[SERVER-31500] Create Javascript test to exercise rollback of dropDatabase command Created: 10/Oct/17 Updated: 30/Oct/23 Resolved: 02/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2017-11-13, Repl 2017-12-04, Repl 2017-12-18, Repl 2018-01-01, Repl 2018-01-15 |
| Participants: |
| Description |
|
The dropDatabase command will drop all the collections in a database, wait on the last collection drop to replicate to a majority of nodes, and then log a dropDatabase oplog entry. If the dropDatabase oplog entry was logged and not replicated to a majority of nodes, it could be rolled back. We should add a test that exercises this scenario, to make sure that rollback behavior is not abnormal if it encounters a dropDatabase oplog entry. |
| Comments |
| Comment by Githook User [ 02/Jan/18 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}Message: |
| Comment by Githook User [ 02/Jan/18 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}Message: |