[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: |
|
||||||||||||||||||||
| 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:
|
| 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: |
| 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 " This reverts commit 2d52cff7ee8fbff257698c334da85fa9115d35c0. |
| 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: |