-
Notifications
You must be signed in to change notification settings - Fork 746
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
Opengrok web application isn't accessible during reindex #4527
Comments
Sounds like a bug. There is probably something in the One way to avoid this is to use the per project workflow which avoids uploading the configuration to the webapp. |
@vladak looks like with Is it expected for My indexing command is: I also couldn't get per project setup to work without the same issue either, could you elaborate on how the setup would look? |
The configuration processing in the webapp might be held by invalidating repositories. Could you take a look at the webapp logs while the configuration upload is in progress to see if that is the case ? Ideally also capture the thread stacks at that point using The point of per project workflow is that per project reindex does not send the complete configuration at the end of the reindex: opengrok/opengrok-indexer/src/main/java/org/opengrok/indexer/index/Indexer.java Lines 421 to 424 in 500e28c
It merely pokes the webapp to bump the index reader for given project. |
I continuously get the same log across multiple threads almost exactly 1 second apart When searching a query I see EDIT: Disabling suggester works fine, sending config finishes in sub second time. Looks like suggester should be temporarily turned off during it's rebuilding to avoid this denial of service. |
It may be, and this is purely a speculation at this point, that at the time the configuration is sent to the webapp, there is already a sequence of suggester rebuild jobs waiting in the queue and it somehow blocks the request. The |
I see, I can reproduce it 100% of the time, so this waiting for rebuild thread is either triggering all the time or indexing somehow spawns it and takes a very very long time to do so as well. Probably interesting to look into how we can optimize suggester rebuilds especially when we have history information and we can granularly build it. Or maybe disable the feature entirely when rebuild is on. EDIT: |
Could you take the stack trace snapshot using |
Hello,
I'm running an opengrok server which is set to run
opengrok-indexer
periodically using cron. I notice that when the indexer is running and the output isSending configuration to: http://localhost:8080/source
the web application is non responsive until this configuration reindex is done. This takes about 5mins as my codebase is big. Is there another way to reindex while still keeping the webapp without degradation?The text was updated successfully, but these errors were encountered: