-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
8.10.0, 8.11.0, 8.12.0, 8.10.1, 8.11.1, 8.10.2, 8.12.1, 8.12.2, 8.13.0, 8.12.3, 8.13.1
-
8.1
-
13
-
Severity 2 - Major
-
11
-
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
- Create an issue with comments in Jira not supporting versioning (< 8.10.0)
- 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)
- this will trigger re-indexing of all comments and produce an index replicated operation for those comments created before upgrading with version 0
- 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
- relates to
-
-
- Closed
-
- is related to
-
GHS-202458 You do not have permission to view this issue
-
-
DBR-259 You do not have permission to view this issue
-
(3 mentioned in)
[JRASERVER-71759] WARN: Unexpected un-versioned operation added for processing ... for comments&worklogs
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 512393 ] |
| Link |
New:
This issue relates to |
| Remote Link | New: This issue links to "Page (Confluence)" [ 517093 ] |
| Description |
Original:
h3. 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. h3. Steps to Reproduce # Create an issue with comments in Jira not supporting versioning (< 8.10.0) # 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) ## this will trigger re-indexing of all comments and produce an index replicated operation for those comments created before upgrading with version 0 ## when other nodes replay this indexing operation the following WARN should be logged: {noformat} 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=''}{noformat} h3. Expected Results Do not log WARNs for legal flows. h3. Actual Results The below message is logged in {{atlassian-jira.log}} file: {noformat} WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation {noformat} h3. Related [https://confluence.atlassian.com/display/JIRAKB/WARN%3A+Unexpected+un-versioned+operation+added+for+processing] |
New:
h3. 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). (i) 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. h3. Steps to Reproduce # Create an issue with comments in Jira not supporting versioning (< 8.10.0) # 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) ## this will trigger re-indexing of all comments and produce an index replicated operation for those comments created before upgrading with version 0 ## when other nodes replay this indexing operation the following WARN should be logged: {noformat} 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=''}{noformat} h3. Expected Results Do not log WARNs for legal flows. h3. Actual Results The below message is logged in {{atlassian-jira.log}} file: {noformat} WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation {noformat} h3. Related [https://confluence.atlassian.com/display/JIRAKB/WARN%3A+Unexpected+un-versioned+operation+added+for+processing] |
| Description |
Original:
h3. 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. h3. Steps to Reproduce # Create an issue with comments in Jira not supporting versioning (< 8.10.0) # 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) ## this will trigger re-indexing of all comments and produce an index replicated operation for those comments created before upgrading with version 0 ## when other nodes replay this indexing operation the following WARN should be logged: {noformat} 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=''}{noformat} h3. Expected Results Do not log WARNs for legal flows. h3. Actual Results The below message is logged in {{atlassian-jira.log}} file: {noformat} WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation {noformat} h3. Workaround [https://confluence.atlassian.com/display/JIRAKB/WARN%3A+Unexpected+un-versioned+operation+added+for+processing] |
New:
h3. 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. h3. Steps to Reproduce # Create an issue with comments in Jira not supporting versioning (< 8.10.0) # 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) ## this will trigger re-indexing of all comments and produce an index replicated operation for those comments created before upgrading with version 0 ## when other nodes replay this indexing operation the following WARN should be logged: {noformat} 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=''}{noformat} h3. Expected Results Do not log WARNs for legal flows. h3. Actual Results The below message is logged in {{atlassian-jira.log}} file: {noformat} WARN [INDEX-REPLAY] Unexpected un-versioned operation added for processing: ReplicatedIndexOperation {noformat} h3. Related [https://confluence.atlassian.com/display/JIRAKB/WARN%3A+Unexpected+un-versioned+operation+added+for+processing] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| UIS | Original: 10 | New: 11 |
| Support reference count | Original: 12 | New: 13 |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Waiting for Release [ 12075 ] | New: In Progress [ 3 ] |