Replies: 1 comment 4 replies
-
After next indexer run, it created new file something |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We found some cases where search on UI doesn't work just after (even after 1 hour) completing the indexing. The index directory doesn't have any dirty file, so that means index is clean but I see some files such as "segment_b" along with other index files. During the next indexing cycle, it creates another file such as "segment_c" ...
Can you please help me understand what does that mean? Also, what could be a reason of search not working after the index? I can browse the files along with History, annotation etc all working fine but search doesn't work.
I see similar issue reported here where deleting the index solved the issue, but before doing that checking if thats only the workaround and what could cause this?
#3590
Some more details:
Opengrok version: 1.7.41 on docker (built from source with following changes in docker/sync.yml file)
Project size: 2.7GB
Beta Was this translation helpful? Give feedback.
All reactions