[SERVER-26840] ChunkManager reload may return successfully if the chunk metadata is corrupted Created: 31/Oct/16 Updated: 19/Nov/16 Resolved: 31/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.0-rc2 |
| Fix Version/s: | 3.4.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2016-11-21 |
| Participants: |
| Description |
|
The chunk manager may return early if the chunk metadata is corrupted (i.e., contains holes or mismatched keys). It is not certain whether any corruptions will not already have been discovered by the incremental reload's logic in the _load method, but for the sake of not introducing a regression the early return should be removed. The bug was introduced by this commit and is only present in 3.4.0-RC2. |
| Comments |
| Comment by Githook User [ 31/Oct/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 31/Oct/16 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Revert " This reverts commit b55d380b4a38345ac7a52d508cf905fc8e789dd2. |
| Comment by Githook User [ 31/Oct/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |