How to Check Jira indexing is Background or Lock Jira Indexing?

[Vishal Srivastava]

Hi,

How can we check whether the indexing running on Jira is background or Lock Jira, with the help of atlassian-jira.log ? 

Please note, we are using Jira Data Center. 

Regards,

Vishal

[Sushil Ranjan · Accepted solution]

If you have set
com.atlassian.jira.issue.index.DefaultIndexManager &
com.atlassian.jira.issue.index to 'Info'.

I think you can also check indexing status on log file like:

less atlassian.log | grep ReindexAll

You should get result as:
JiraTaskExectionThread-1370 INFO sushil 183x10834283x4 1xesk2a 169.10.31.218 /secure/admin/IndexReIndex.jspa [c.a.j.issue.index.DefaultIndexManager] ReindexAll in foreground: {indexIssues=true, indexChangeHistory=true, indexComments=true, indexWorklogs=true, forceReloadFromDatabase=false}

[Nic Brough -Adaptavist-]

You can just try visting a Jira page.  If a locking index run is in progress, it will say you can't log in.

[Craig Castle-Mead]

In Server, this would definitely work, but the poster mentioned they're running DC, and if they've configured the load balancer using /status as documented, the node running the locking cluster changes to 503 response with {"state":"MAINTENANCE"} body, so that node would drop off the LB. You could look for a node returning 503 on the LB/status URL.

As for the application log itself, I've just done a locking and non-locking index and looked at the logs and can't see any specific marker to determine which is which...

CCM

[Nic Brough -Adaptavist-]

I think I answered before the DC install was added to the question.

So, @Vishal Srivastava , @Craig Castle-Mead is absolutely right about the DC config. 

You can try visiting a Jira page, but you will only get an error if you have landed on a node that is being indexed (and if you set your DC up to be nice to your users, your load-balancers will never land them on a node that is being indexed!)

As for the logs - @Craig Castle-Mead  is spot on again, the defaults for server and DC do not log "I'm indexing", but I want to add that you can go to Admin -> logging and profiling and change the log-level of the indexing classes to something that is more talkative, then you'll be able to capture it in the log for that node.   (Just to be really sad, my memory is yelling "com.atlassian.jira.issue.index" at me as the class to increase the logging on.  Do not trust my memory, please look for yourself and bear in mind most of my work has been with "server", not DC or Cloud)