Site reindex should reset journal entry pointer upon successful completion to prevent the reindex run after each restart when the journal entry queue is empty

Issue Summary

As documented in How to Rebuild the Content Indexes From Scratch on Confluence Data Center, journal directory must be deleted before reindexing. This however may cause that node to run full site reindexing at every restart afterward if there is no new index journal (content updates that require an index update e.g. new page, page update, etc...) during that reindexing. The reason is Confluence expects there must always be some entries in journal directory.

Steps to Reproduce

Just follow the instructions described in How to Rebuild the Content Indexes From Scratch on Confluence Data Center

Expected Results

<confluence-home>/journal/main_index is created when the index is rebuilt.

Actual Results

<confluence-home>/journal/main_index is not created.

Notes

When you do some page operation (e.g. new page, page update, etc...) after rebuilding index, you can see that the file is created for the first time.

Workaround

When you do How to Rebuild the Content Indexes From Scratch on Confluence Data Center, add a step to make page operation on Confluence as

Start Node 1 and make any page operation on Confluence (this will recreate journal/main_index directory) . This node will rebuild its index from the database automatically on startup. Log files will print lines like the below to signify the reindex has been kicked off: