[SERVER-24927] Ignore NamespaceNotFound errors during initial sync apply ops, because they are transient Created: 06/Jul/16 Updated: 24/Mar/17 Resolved: 07/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.12, 3.2.7, 3.3.9 |
| Fix Version/s: | 3.2.12, 3.3.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| 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 | ||||||||||||||||
| Backport Requested: |
v3.2
|
||||||||||||||||
| Sprint: | Repl 17 (07/15/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
During initial sync, there is a race between when we get the first op to apply and when we call list collections and create them all. Consider the following operation order: 1. Primary creates collection, foo into foo 4. Primary drops foo and gets NamespaceNotFound error. During initial sync, we should just ignore NamespaceNotFound errors since that means that a drop collection has occurred later on in the oplog. |
| Comments |
| Comment by Githook User [ 19/Jan/17 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'visualzhou@gmail.com'}Message: |
| Comment by Githook User [ 07/Jul/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |