Batch reindex queues every dataset at once since #12712
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start at IndexServiceBean.indexDatasetInNewTransaction and compare the change from #12712 with the 6.12 behavior described in the issue. Restore direct dataset indexing there so full and recursive reindexes do not queue every dataset at once; verify that progress, duration, and index-time recording reflect the indexing work.
Written by the indexing model from the issue text.
Description
Since #12712, IndexServiceBean.indexDatasetInNewTransaction fires an indexing request instead of indexing the dataset itself. In 6.12 it indexed the dataset right away, one at a time. Now a full reindex, and a recursive collection reindex (also used when moving a collection), queue every dataset as an @Asynchronous call at once.
Effects:
- The shared async pool is flooded: indexing after an edit, exports and index time updates wait behind the whole backlog.
- The progress and duration log lines of the reindex no longer reflect the indexing.
- Index times are only recorded when the backlog drains.
Fix: index the dataset directly in indexDatasetInNewTransaction again.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 569
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 36
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IQSS/dataverse
-
Release Size: 30
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
docs: remove obsolete edit in domain.xmlPossibly taken @donsizemore claimed this 8 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
IQSS/dataverse#12768 · 3 comments ·
Maintainers usually reply within 1 day
-
docs: remove obsolete chown command and follow-up notePossibly taken @donsizemore claimed this 8 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
IQSS/dataverse#12764 · 1 reaction ·
Maintainers usually reply within 1 day
-
S3SubmitToArchiveCommand: temporary bag files not deleted after upload, causing disk space leakOpenType: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
IQSS/dataverse#12736 · 1 comment ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IQSS/dataverse#12735 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day
-
[BUG] S3 CORS responses omit Access-Control-Allow-Credentials for matched originsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
floci-io/floci#5369 · 1 comment ·
Maintainers usually reply within 1 day
-
securityHeaders replaces a route's own Content-Security-Policy (0.9.9; weakens embedders' pages)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sqlcipher/sqlcipher-android#97 · 1 comment ·
-
area-integrations
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day