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?
Hi Peter,
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.
Kind regards,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For anyone finding this old thread: the index queue is no longer stored in INDEXQUEUEENTRIES, but I have no idea where they've moved it now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Index queue moved to journalentry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.