Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reindex all jobs take too long to start #3075

Open
CGillen opened this issue Mar 7, 2024 · 0 comments
Open

Reindex all jobs take too long to start #3075

CGillen opened this issue Mar 7, 2024 · 0 comments
Labels
Features Issues related to building and enhancing features Priority - Medium Issues that should be prioritized ahead of low but not immediately critical - bulk of work cycles Ready for Development The issue has passed review from teams and is ready to be worked on

Comments

@CGillen
Copy link
Contributor

CGillen commented Mar 7, 2024

Descriptive summary

Currently a reindex is starting and it has taken an unacceptably long time to spool up. It claims 5675709.1ms to query the head of Fedora (though it took closer to several days) and has now been running for 21272:51min, or just under 15 days, without finishing partitioning the URIs. Before any jobs can be submitted to SideKiq, this partitioning has to be completed, so no real work has begin and we're 15 days behind content that would need to be reindexed.

We need to find a way to reindex as we find URIs to reindexable assets.

Expected behavior

Reindexing jobs are queued as URIs are found, not after all URIs are found and partitioned.
Alternatively, reindexing is just generally sped up.

Related work

#2760
#2651

@CGillen CGillen added Features Issues related to building and enhancing features Ready for Development The issue has passed review from teams and is ready to be worked on Priority - Medium Issues that should be prioritized ahead of low but not immediately critical - bulk of work cycles labels Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Features Issues related to building and enhancing features Priority - Medium Issues that should be prioritized ahead of low but not immediately critical - bulk of work cycles Ready for Development The issue has passed review from teams and is ready to be worked on
Projects
None yet
Development

No branches or pull requests

1 participant