[SERVER-31825] replset6.js should await replication before checking that renameCollection replicated properly Created: 03/Nov/17 Updated: 30/Oct/23 Resolved: 03/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
replset6.js tests the replication of renameCollection commands across databases i.e.
renameCollection commands across databases are not atomic, and are comprised of several, individual oplog entries. The last oplog entry that gets logged is the drop of the source collection, and before that we rename the temp collection into its final destination. If there is a delay between the application of these ops, we might see the rename but not wait for the source collection to be dropped on secondary. |
| Comments |
| Comment by Githook User [ 03/Nov/17 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |