We are migrating Confluence from 2.8 to 4.3. This involves many iterations as we work through the gremlins we uncover.
Some of the most elapsed-time-consuming steps involve waiting for behind the scenes processing to complete.
The techniques for this are a) use TOP on the server to see when the JVM's CPU activity becomes negligible and b) running SQL Trace to see if there is any d/b activity.
Though it is not always content indexing per se, the waits almost always involve something being done that shows on the Content Indexing Queue (eg: when creating an LDAP directory, tens of thousands of Add change document: com.atlassian.confluence.user.PersonalInformation-NNNNNNN items).
To gauge how much time we have before the next migration step we check Content Indexing | Queue Contents.
But, this is very slow and often times out (when the queue is large).
Is there a quick SQL query that can be run to just show the Queue length, please?
I am not sure if I understand the question correctly, but the index queue is stored in the INDEXQUEUEENTRIES table, that may give you an ide what is waiting to be processed. However by this, you will not be able to calculate the exact time it takes for indexing to finish.
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