[SERVER-22474] rollback.js Created: 03/Feb/16  Updated: 22/Feb/16  Resolved: 04/Feb/16

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

Type: Bug Priority: Critical - P2
Reporter: Jonathan Reams Assignee: Eric Milkie
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
Participants:

 Description   

replicasets_legacy failed on linux-64

rollback.js - Logs | History

BF Ticket Generated by jonathan.reams



 Comments   
Comment by Githook User [ 04/Feb/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-22474 rollback needs to wait longer than the 30 second vote timeout
Branch: master
https://github.com/mongodb/mongo/commit/d24254aa15beeb2a93b696b36e40d4def40d4f3f

Comment by Scott Hernandez (Inactive) [ 04/Feb/16 ]

Talked to Eric and passing back for more investigation.

Comment by Scott Hernandez (Inactive) [ 04/Feb/16 ]

This failure happened before that commit, no?

Comment by Eric Milkie [ 04/Feb/16 ]

Could we try changing the timeout to simply match what it was in 3.0?
Although I'm not sure how rollback.js and friends were reliably passing, since it waits for a new primary for only 30 seconds.

Comment by Eric Milkie [ 04/Feb/16 ]

This appears to be a manifestation of what we feared: raising the first oplogreader find's timeout to 1 minute causes failover to possibly take 1 minute.

Generated at Thu Feb 08 04:00:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.