We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When we update the index with a cron job. Is the https://github.com/ufal/lindat_piwik_reports/blob/master/scripts/search_application.py#L9 searcher updated right away, or do the values returned depend on the workers lifecycle (it would then be possible that each worker returns a different count)?
We've observed some sort of value skipping on production. The above might be a pointer to the cause.
The text was updated successfully, but these errors were encountered:
Maybe we should do some isCurrent (https://lucene.apache.org/core/6_5_0/core/org/apache/lucene/index/DirectoryReader.html#isCurrent--) check. Or use the Makefile to restart the workers
isCurrent
Sorry, something went wrong.
vidiecan
Successfully merging a pull request may close this issue.
When we update the index with a cron job. Is the https://github.com/ufal/lindat_piwik_reports/blob/master/scripts/search_application.py#L9 searcher updated right away, or do the values returned depend on the workers lifecycle (it would then be possible that each worker returns a different count)?
We've observed some sort of value skipping on production. The above might be a pointer to the cause.
The text was updated successfully, but these errors were encountered: