[SERVER-18511] Report upstream progress when initial sync completes Created: 18/May/15  Updated: 07/Jan/20  Resolved: 08/Jun/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.0.3
Fix Version/s: 3.0.4

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-17934 Do not report upstream progress while... Closed
related to SERVER-19244 Secondary position information can be... Closed
related to SERVER-18110 Add Reporter to Data Replicator Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL 5 06/26/16
Participants:

 Description   

Currently, write concern can fail to be satisfied even when sufficient nodes receive the write, if one of the nodes received it while initial syncing. Consider the following:

  • 2 nodes started as a replicaset
  • replSetInitiate is ran and the set is then hammered with w:2 writes
  • one node becomes primary and accepts a write
  • the other node receives the write through initial sync and does not report this progress


 Comments   
Comment by Githook User [ 08/Jun/15 ]

Author:

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

Message: SERVER-18511 report replication progress upstream after initial sync completes
Branch: v3.0
https://github.com/mongodb/mongo/commit/43f94f503d7be84aab9417a81fd5abef537bdcb4

Comment by Githook User [ 08/Jun/15 ]

Author:

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

Message: Revert "SERVER-18511 report upstream progress when initial sync completes"

This reverts commit 2d52cff7ee8fbff257698c334da85fa9115d35c0.
Branch: v3.0
https://github.com/mongodb/mongo/commit/6cff58bea0dd2bda391d84a8d7bc1f604d4a4607

Comment by Matt Dannenberg [ 21/May/15 ]

After research and repros, it was concluded that this problem is only present in the 3.0 branch of mongodb. The fix has been pushed and will be included in the next release of 3.0 series.

Comment by Githook User [ 21/May/15 ]

Author:

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

Message: SERVER-18511 report upstream progress when initial sync completes
Branch: v3.0
https://github.com/mongodb/mongo/commit/2d52cff7ee8fbff257698c334da85fa9115d35c0

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