Issue Summary

Note that this bug affects Jira DC only.

In Jira 8.10.0 we added versioning of Jira entities: issues, comments, worklogs.

From now on every index operation replayed by other nodes contains also the version of entity which is requested to be re-indexed by other nodes.

It is possible that comments/worklogs re-index request may be added without version (i.e. version = 0).

If you see this WARNING in Jira 8.10.x, 8.11.x, 8.12.x, 8.13.0, 8.13.1 in the context of comments or worklogs (affectedIndex=COMMENT or affectedIndex=WORKLOG), you can safely ignore it.

Steps to Reproduce

1. Create an issue with comments in Jira not supporting versioning (< 8.10.0)
2. After upgrading to Jira supporting versioning (>= 8.10) trigger an action which re-indexes the whole issue with related entities (example: in 8.11 - 8.13.2 link this issue with another issue)
   1. this will trigger re-indexing of all comments and produce an index replicated operation for those comments created before upgrading with version 0
   2. when other nodes replay this indexing operation the following WARN should be logged:

WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation {indexTime=2020-09-18 09:01:34.136, id=3813938, nodeId='node1', affectedIdToVersion={85040=0, 90614=0, 86326=0, 85894=0, 90377=0, 85258=0}, operation=UPDATE, affectedIndex=COMMENT, entityType=NONE, backupFilename=''}

Expected Results

Do not log WARNs for legal flows. 

Actual Results

The below message is logged in atlassian-jira.log file:

WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation

Related

https://confluence.atlassian.com/display/JIRAKB/WARN%3A+Unexpected+un-versioned+operation+added+for+processing