From reading this article on how Jira indexing works in a data center environment; each node has its own copy of the index.
Reading the Elastic Search documentation on how it functions in a cluster; there is only one instance of an index which may be split across each node.
My question is why does each Jira node have its own copy of the index? It isnt efficient and could mean getting different results dependent on which node you are on.
Thanks for the reply Nic,
In our multi node data center environment we have a cron job that triggers an overnight background re-index on an admin node. Once the index is built this gets copied across to the other nodes. As events are generated these are broadcast to the other Jira nodes.
Every night we trigger the background re-index on the admin node to avoid the risk of indexes becoming out of date.
Does this setup sound correct?
We are suffering with ongoing issues with our Jira data centre nodes having corrupted indexes.
Atlassian havent got this right at all. For data centre environments using netapp or other shared storage I dont agree with you about the speed issue and it being faster having indexes locally.
A more scaleable robust solution would be where each node contributes towards building an index in ElasticSearch (which can itself be multi node and resilient).
Splitting the reindex task across nodes would also reduce the reindex time from the several hours it takes currently.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot