@Leigh,
Mark has commented on the implementation details in a separate Jira here:
https://jira.atlassian.com/browse/JRA-25788?focusedCommentId=323761&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-323761
Hope this helps.

I've not had a chance to try out 5.2 EAP as yet, but can anyone confirm if this has been implemented in that release and provide some details as to the mechanism that's been adopted?

Thanks

This will be implemented in 5.2 - the first milestone will be available for testing and feedback in ~ 2 weeks.

This is a feature I would expect from any application advertising itself as "Enterprise". You simply cannot have operations that lock users out, especially routine maintenance operations.

JIRA should re-index in the background, but, if that's not possible, it should at a minimum re-index atomically by project to lessen the global impact.

Hi, I implemented Michael's Jelly script below and works a treat, does background re-indexing and still allows users to access JIRA issues at the same time, however it does not remove the blue banner in Admin mode saying the a re-index is needed?

Chris Kent made configuration changes in section 'Custom Fields' at 03/May/12 11:31 AM. It is recommended that you perform a re-index. For more information, please click the Help icon.

To perform the re-index now, please go to the 'Indexing' section.

Note: So that you only have to re-index once, you may wish to complete any other configuration changes before performing the re-index.

My question is, what command can I add to the Jelly script to remove this warning banner after the background re-index is finished?

Thanks

The jelly script is iterating over a set of issues, calling reIndex on wach one. The usual reindex operation does the iteration from within Java so I'd expect it to be (a bit) faster.

@Michael, we have not shared this implementation. Do not hesitate to contact me per e-mail for more information. It is a custom Java solution that has its own db and runs separate from Jira, hence keeps Jira running smooth. I prefer to archive projects as separate time-boxed projects in Jira but in some cases this is not possible.

@Matt: The jelly-script shouldn't be faster or slower. It just starts the normal reindex process with the issues provided by the given filter.

@Ivar: how do you implemented your archiving solution? Is it available as plugin?

With 500k+ issues and hardware designed to run Jira smoothly but without exaggerating the server specs it took us over 5 hours to do the reindexing in Jira 3.13. After this, we implemented a custom archiving solution to cut down on the number of old rarely needed issues.

Reindex on a server with enough memory shouldn't take hours. I see 10 mins to 180K issues at one client. I'd be interested to know how much longer than the ordinary reindex using Jelly takes?