[SERVER-42783] Migrations don't wait for majority replication of cloned documents if there are no transfer mods Created: 12/Aug/19 Updated: 29/Oct/23 Resolved: 22/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.15, 3.6.4, 4.0.0, 4.2.0 |
| Fix Version/s: | 3.6.15, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.2, v4.0, v3.6, v3.4
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Run the following test that shows majority committed documents may not be in the recipient shard's majority committed snapshot after a migration:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding 2019-08-26 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 23 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Before a chunk migration can commit, the shard receiving the chunk is supposed to wait for every document in the chunk to be majority committed to ensure no data can be lost if there's a failover. Currently, the recipient shard will wait for the maximum of the last opTime on the client of the thread driving the migration on the recipient at the end of the cloning phase and the opTime of the latest transfer mod write to be majority committed.
This has at least the following implications for migrations that involve no transfer mods:
|
| Comments |
| Comment by Githook User [ 08/Oct/19 ] |
|
Author: {'name': 'Janna Golden', 'username': 'jannaerin', 'email': 'janna.golden@mongodb.com'}Message: (cherry picked from commit 2fb73bcd2515cd8d566fecc5b23ee9f6970b1716) |
| Comment by Githook User [ 07/Oct/19 ] |
|
Author: {'username': 'jannaerin', 'email': 'janna.golden@mongodb.com', 'name': 'Janna Golden'}Message: (cherry picked from commit 2fb73bcd2515cd8d566fecc5b23ee9f6970b1716) |
| Comment by Githook User [ 07/Oct/19 ] |
|
Author: {'username': 'jannaerin', 'email': 'janna.golden@mongodb.com', 'name': 'Janna Golden'}Message: (cherry picked from commit 2fb73bcd2515cd8d566fecc5b23ee9f6970b1716) |
| Comment by Githook User [ 22/Aug/19 ] |
|
Author: {'username': 'jannaerin', 'email': 'golden.janna@gmail.com', 'name': 'jannaerin'}Message: |