Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Data Centre Search Problems Edited

Recently we have had a number of indexing failures on our 4 node Jira data centre installation. Indexes were corrupt and restoring from backup indexes was also failing. Our system administrator is currently holding his head in his hands wondering how to fix it.

Compared to Bitbucket where ElasticSearch was added to the product it looks like Jira Data Centre still has the old single node Search architecture and it doesnt work well in Jira Data Centre.

Each Jira node looks to have its own embedded lucene instance with indexes being built on a node and copied across to the other nodes. Each node has its own copy of the indexes. Our recent problems with corrupted indexes has prompted me to write this post and suggest an alternate approach.

Where Jira is

ElasticSearch is embedded in Jira, each node has it's own copy of the complete index. This doesn't scale, isnt efficent or performant and from recent experience isn't reliable.

Where Jira should be

ElasticSearch should be a separate install preferably on a separate server or servers. Each node contributes to generating indexes that are used by all nodes (a single source of truth). Indexing times are reduced as the task can be split across all nodes. Indexing is only ever a background task.

 

 

0 comments

Comment

Log in or Sign up to comment
TAGS

Community Events

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

Events near you