[SERVER-20587] UnrecoverableRollbackError during sync_passive2.js Created: 11/Sep/15  Updated: 07/Oct/15  Resolved: 23/Sep/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Minor - P4
Reporter: Charlie Swanson Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL A (10/09/15)
Participants:

 Description   

Task
Logs

[js_test:sync_passive2] 2015-09-11T02:52:48.392+0000  m20012| 2015-09-11T02:52:48.390+0000 I REPL     [SyncSourceFeedback] setting syncSourceFeedback to ip-10-233-128-208:20013
[js_test:sync_passive2] 2015-09-11T02:52:48.392+0000  m20012| 2015-09-11T02:52:48.391+0000 I REPL     [rsBackgroundSync] starting rollback: RemoteOplogStale we are ahead of the sync source, will try to roll back
[js_test:sync_passive2] 2015-09-11T02:52:48.396+0000  m20012| 2015-09-11T02:52:48.396+0000 F REPL     [rsBackgroundSync] need to rollback, but in inconsistent state
[js_test:sync_passive2] 2015-09-11T02:52:48.396+0000  m20012| 2015-09-11T02:52:48.396+0000 I -        [rsBackgroundSync] Fatal assertion 28723 UnrecoverableRollbackError need to rollback, but in inconsistent state. minvalid: (term: -1, timestamp: Sep 11 02:52:48:2) our last optime: (term: -1, timestamp: Sep 11 02:52:48:1) @ 18750
[js_test:sync_passive2] 2015-09-11T02:52:48.397+0000  m20012| 2015-09-11T02:52:48.396+0000 I -        [rsBackgroundSync]
[js_test:sync_passive2] 2015-09-11T02:52:48.397+0000  m20012|
[js_test:sync_passive2] 2015-09-11T02:52:48.397+0000  m20012| ***aborting after fassert() failure



 Comments   
Comment by Githook User [ 23/Sep/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-20587 prevent UnrecoverableRollbackError in sync_passive2.js
Branch: master
https://github.com/mongodb/mongo/commit/c5d91ef1046d109be65c9365cc86ed478a09476d

Comment by Matt Dannenberg [ 23/Sep/15 ]

Nope. This is a bad syncFrom leading to an unexpected rollback in the test, SERVER-20579 is caused by arbiters attempting to sync from nodes.

Comment by J Rassi [ 23/Sep/15 ]

matt.dannenberg, is SERVER-20579 a dup of this?

Comment by Siyuan Zhou [ 21/Sep/15 ]

An invariant is triggered after forcing a secondary to sync from another secondary that is staler that itself. The node used to sync from the primary.

Comment by Charlie Swanson [ 14/Sep/15 ]

Happened again here

Comment by Siyuan Zhou [ 11/Sep/15 ]

benety.goh, is this one of the known issues about rollback?

Generated at Thu Feb 08 03:54:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.