This is not a good answer. Some JIRA instances, including ours, serve 10k users or more and experience hundreds of changes a week across hundreds of projects. Many of these changes call for a reindex.
One challenge is that background reindexing can take double or triple the time of a hard (locking) reindex, and is less efficient. When Background reindexing takes more than twelve hours, creeping into daytime hours on a system already struggling for resources, it's time to more regularly do a hard reindex - e.g. weekly - and this is why I am up right now, on a Saturday night.
Before you suggest moving to Data Center, we know. Cash and politics can delay such an upgrade for years in some cases. We work with what we have, which is large VMs for production, failover, and nonprod.
It would really help me to automate this otherwise manual weekly experience.
I agree with Kay - my reindex takes over 1 hour due to the sheer size of our platform. I have to say i get a little tired of the Atlassian Point of View that says i must do this manually, in my own time out of hours on a platform with a number of homeworkers and international staff who want a lot of access hours.
This forces me to sit up at 10pm at night and hang around. That's a little ridiculous. I should be able to set something on the working day that will trigger it at Xhours and just leave a system banner to communicate that it will be coming down later.
Atlassian have said they want to be considered *an enterprise scale tool*, but these residual "small system" mentality failings that are becoming a blocker for us.
I accept your answer.
However, the reason we need to do it as we have on-going problems with the Epic link being populated into subtasks on auto create of subtasks. We are on an older version so hopefully this problem is resolved in the newer version when we upgrade shortly.
Also, re-indexing is not actually that long a job on our system.
Under normal circumstances having to automate a re-index is usually indicative of a deeper problem.
For us this is not the case....we are already on data center, but we have over 300,000 issues in flight at any given time. When we import data into our eazyBI reporting platform we are finding random anomalies with the issue counts, statuses, etc. For this specific use case an automated re-index prior to an eazyBI import seems to resolve these anomalies.
Don't automate the problem away if you are seeing red indexing toaster messages.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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