[SERVER-29273] Two Phase Drops: add list of drop-pending collections to ReplicationCoordinator Created: 18/May/17 Updated: 30/Oct/23 Resolved: 24/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.8 |
| Type: | Task | 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 | ||||||||||||||||
| Sprint: | Repl 2017-05-29 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
With 2-phase drops, collections are not physically dropped (on all nodes) until the commit point advances past the optime when the collection drop was first requested on the primary. Since the ReplicationCoordinator maintains the commit point, it is a logical choice for a location to hold this list of drop-pending collections. This list is updated when:
|
| Comments |
| Comment by Githook User [ 25/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: Revert " This reverts commit a339d8d6167aae163bdf7cda71c81e3165385ff4. |
| Comment by Githook User [ 25/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: The drop-pending collection will be removed by DropPendingCollectionReaper |
| Comment by Githook User [ 24/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 23/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 19/May/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |