[SERVER-33956] A sequence of rename and create collections that do not arrive at the correct end state Created: 16/Mar/18 Updated: 29/Oct/23 Resolved: 29/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.5, 3.7.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | 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 | ||||||||||||||||||||||||||||||||
| Steps To Reproduce: |
|
||||||||||||||||||||||||||||||||
| Sprint: | Repl 2018-04-09 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Linked BF Score: | 4 | ||||||||||||||||||||||||||||||||
| Description |
|
Consider a node initial syncing from a primary. The initial syncing node, before the oplog application phase has the following collection -> UUID mappings:
It also happens to be that this is the correct goal state. Now consider the sequence of oplog entries that are played as part of the oplog application step of initial sync:
Those operations result in the initial syncing node to only have test.shardedColl -> UUID("16ce21b8-320c-4bfc-af8c-05cae93bdadb") while missing the expected test.bar collection. I can make statements about behavior change that fix this specific sequence, but I can't speak to their correctness globally. I do have two observations that might illuminate what's going wrong.
One clarification about the reproduction script. The first two "oplog entries" are simply to recreate the state of the initial syncing node before it began oplog application. Had a primary produced that sequence of oplog entries, including the initial creates would be a very different problem. |
| Comments |
| Comment by Githook User [ 24/Apr/18 ] |
|
Author: {'email': 'benety@mongodb.com', 'username': 'benety', 'name': 'Benety Goh'}Message: (cherry picked from commit 0d02b8352e3f44385276fb2bbc6f5c09736afa04) |
| Comment by Githook User [ 24/Apr/18 ] |
|
Author: {'email': 'benety@mongodb.com', 'username': 'benety', 'name': 'Benety Goh'}Message: This test case demonstrates the current behavior when the target collection does (cherry picked from commit c2d54f70ad7b23bba86776f60504dc4916dead27) |
| Comment by Githook User [ 29/Mar/18 ] |
|
Author: {'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}Message: |
| Comment by Githook User [ 29/Mar/18 ] |
|
Author: {'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}Message: This test case demonstrates the current behavior when the target collection does |