Incremental Re-Index associated with user that last ran reindex

[Kristin Lyons]

When a user performed either a locked re-index or a background re-index, and then an incremental re-index is performed on it's own - is the user who last ran the re-index the user account associated with the incremental re-indexes?  I am specifically talking about when we are reading the logs.  Is there any documentation surround thing? It's more to ensure that everything is running smoothly in our environment.

[Nic Brough -Adaptavist- · Accepted solution]

No, the account that kicks off the index process has nothing to do with it, other than being the person that triggers it.

[Kristin Lyons]

Thanks for the update - are incremental indexes ever run in the background without a user triggering it?

[Nic Brough -Adaptavist-]

Yes and no.

Yes - the index is updated on every change of issue, which may be made by things other than a human.

No - neither of the full re-indexes, foreground (locking) or background are run automatically, humans have to trigger them (although you can script it of course). 

The foreground one is also done during upgrades unless you set a flag to turn it off (makes it faster if you've got more than one version to go through on upgrade, like 6.4 -> 7.0 -> 7.13 -> 8.20 - you don't need the index for upgrades, you only need it when you're letting people into the 8.20 system)

By the way, the background indexing is not "incremental", it just reads each issue and rebuilds the index records for it.  The locking index does exactly the same thing, but it deletes the index before building anything (that's why it locks Jira - most of Jira's functions rely on reading the index first)