[SERVER-23663] New primary syncs from chosen node to catch up with timeout Created: 12/Apr/16 Updated: 25/Jan/17 Resolved: 05/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Crystal Horn | Assignee: | Siyuan Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 15 (06/03/16), Repl 16 (06/24/16), Repl 17 (07/15/16), Repl 18 (08/05/16) | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||
| Description |
|
To avoid unnecessary rollback after a PV1 election, the new primary finds the node with the highest lastOpTime, then tries to sync all the oplog from that node to catch up its opTime. This ticket is for the catch-up phase. If the catch-up timeout expires before we exhaust all the sync source’s oplog entries, the new primary ends the catch-up phase and proceeds to exit drain mode like normal. |
| Comments |
| Comment by Githook User [ 05/Aug/16 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Githook User [ 04/Aug/16 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message:
|
| Comment by Githook User [ 02/Aug/16 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: |