[SERVER-29752] Two Phase Drops: support dropping of system collections when applying operations Created: 20/Jun/17 Updated: 30/Oct/23 Resolved: 21/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | 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: | Repl 2017-07-10 | ||||||||
| Participants: | |||||||||
| Description |
|
When dropping databases under the two phase design, collection drop oplog entries will be generated for system collections. We need to be able to apply these operations on secondary nodes in order to complete the two phase drop instead of silently failing due to a check in DatabaseImpl::dropCollection(). Additionally, this will add support to the applyOps command for dropping system collections. |
| Comments |
| Comment by Githook User [ 21/Jun/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 21/Jun/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |