Hi Jira gurus,
Do to some plugin issues, our Jira instance won't allow background indexing -- it only allows a locked-down re-index. But this can take 3-5 hours on our environment, and I would very much like to avoid that.
I know script runner has the reindex built in script -- I've used it for small changes before. But is there a way to use this to perform a full background reindex, so the "lock" is removed?
Anyone experiment with this?
BTW -- I've done the DB checks -- there is no discrepancy between jiraaction/jiraissue field and jiraissue/ID field.
So what happens when you try a background re-index?
I'm pretty sure that if you use the script runner to do a back-ground re-index, it's going to fail anyway, as all it will really do is run the same as what goes off when you click the re-index in there. My instinct is that you need to fix the background re-index
It doesn't even give you the option. You can only do the full locked re-index.
However, I am able to run the script runner built-in reindex just fine.
I guess Ideally, I wish there was a way to remove the "lock" (for lack of a better term) preventing me from doing the background re-index.
If I have to bite the bullet, and schedule a 4 hour maintenance for a re-index, that's what I'll do.. but I am so not looking forward to explaining that to management. :)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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