Anybody know if it is ok to restart the Confluence service before the index rebuild completes? We are wanting to give the virtual server and jvm more memory but the re-index is going very slowly. We want to do this irrespective of the re-index ... the machine just needs more but I'd rather not wait a day or two more to add it if possible.
The reindex will begin all over again after the restart, because it was not completed properly.
A good thing do to - after is to perform your changes - is to perform a Rebuild from Scratch:
https://confluence.atlassian.com/display/CONFKB/Rebuild+the+Content+Indices+from+Scratch, so you next rebuilds (using the UI) should run more quickly.
It's actually doing a rebuild from scratch right now ... SLOWLY. I started it last night and it went from 0%-66% in about 10 minutes and has spend the last 9 hours getting to 67%. The server needs more RAM anyway, so hopefully adding more will help with the index rebuild faster.
In the worst case the index will not be completed which means that some content might not be searchable for a while (until you rebuild the indexes again).
I figured that was the worst case, but should it in the best case just continue on with the rest if it hasn't been indexed yet? Or will it always require a re-index?
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events