Replies: 1 comment
-
These is an excerpt from the webapp log. What might have happened is that the request to the webapp for the file arrived just after the file was updated on disk and before the indexer ran. You can raise log level for the indexer to see how it handled the file and when. There is a way how to make reindexing almost atomic however it requires sort of elaborate workflow and possibly a file-system capable of creating snapshots/clones. Otherwise it would be a bug however much more information would be needed in such case. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
Opengrok notices newer files but does not rebuild the xref .gz files
If you provide the exact version of OpenGrok, JDK used, OS(and its version) used and Tomcat(or your webapp server) used it can help figuring out an environment issue.
Opengrok Docker 1.13.7
To Reproduce
Steps to reproduce the behavior:
Let
opengrok-sync
update the source.Expected behavior
Opengrok checkFileInner updates the
.gz
files when it notces a updated code-fileScreenshots
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions