WARN: Unexpected un-versioned operation added for processing
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
TLDR
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.
In Jira 8.10.0 we added versioning of Jira entities: issues, comments, worklogs.
From now 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).
| 8.10.x | 8.11.x | 8.12.x | 8.13.0 | 8.13.1 |
|---|
In Jira 8.10.x, 8.11.x, 8.12.x, 8.13.0, 8.13.1 every time a node re-indexes such entity the following warning is 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=''}
This does not cause any Jira index corruption. Such an entity is unconditionally re-indexed (vs versioned entities which are re-index only if the local index does not contain an entity with version greater or equal). This message may be logged very frequently thus affect the Jira instance: frequent log file rotation, logging performance affected.
There are a few scenarios where such a situation happens in a valid flow and should not cause any concern:
- after upgrading, when there is any action which triggers a full issue re-index (issue & comments & worklogs) the comments & worklogs which were created/updated in a version of Jira not supporting versioning, those comments&worklogs will have version 0
- when adding a comment which triggers a full issue re-index (before this comment is indexed & versioned), this new comment is first replicated with version = 0 (because of the full issue re-index) and then replicated with version 1
| 8.14.0 | 8.13.2 |
|---|
Because of this we have slightly changed this log message in Jira >=8.14.0 and 8.13.2.
There is still a warning when processing an un-versioned issue entity. It should only happen just after ZDU (when a node may still process an index operation created by a node with no versioning). In any case this requires investigation:
WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation {indexTime=... affectedIndex=ISSUE...}
When processing unversioned comments & worklogs entities, the log level and message changed to:
DEBUG [INDEX-REPLAY] Un-versioned COMMENT/WORKLOG operation added for processing: ReplicatedIndexOperation {indexTime=... affectedIndex=COMMENT...}Note that there is still the aggregated (every 5 min) log [INDEX-REPLAY] which contains the number of un-versioned entities:
[INDEX-REPLAY] [STATS] Node replay index operations stats (total): ... compactUnVersionedCounter
[INDEX-REPLAY] [STATS] Node replay index operations stats (snapshot): ... compactUnVersionedCounterCompare compactUnVersionedCounter vs compactVersionedCounter:
- for comments&worklogs expect
compactUnVersionedCounter << compactVersionedCounter - for issues expect
compactUnVersionedCounter ~ 0, can be > 0 only just after ZDU