[SERVER-36132] Invariant that chunk migration is actually reflected in the metadata after successful commit Created: 13/Jul/18 Updated: 29/Oct/23 Resolved: 17/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.17, 3.6.7, 4.0.1, 4.1.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.0, v3.6, v3.4
|
||||||||||||||||
| Sprint: | Sharding 2018-07-30 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 15 | ||||||||||||||||
| Description |
|
Currently, if for some reason the successfully committed chunk migration is not visible after refresh, the code will silently return a succeeded status. Such situation would be a data corruption and instead we should invariant and output diagnostic information. |
| Comments |
| Comment by Githook User [ 26/Jul/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 4858e05ee6bb59ec728d74802766c05b122aeced) |
| Comment by Githook User [ 25/Jul/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 1c0bce5f9792f0f6d4f26cd041a0c60c0398bd5e) |
| Comment by Githook User [ 23/Jul/18 ] |
|
Author: {'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}Message: (cherry picked from commit 1c0bce5f9792f0f6d4f26cd041a0c60c0398bd5e) |
| Comment by Githook User [ 17/Jul/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: |