Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.1.1
-
None
-
6.01
-
Description
One of the customers reported that for large instances it's not possible to cancel re-indexing after project key was changed. Either the process checks for cancellation rarely or it doesn't check for it at the project re-index level at all.
I imagine problem is caused by jira.index.background.batch.size (advanced property) set to some large value - issues are processed in batches and when batch is processed it's not possible to cancel (the flag is set but cancellation happens only between batches).
Attachments
Issue Links
- is cloned from
-
JDEV-25436 Loading...
- mentioned in
-
Page Loading...