[SERVER-71479] Merging chunks must not set `validAfter` to the current wall time Created: 18/Nov/22 Updated: 29/Oct/23 Resolved: 05/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.4, 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Silvia Surroca |
| 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 | ||||
| Backport Requested: |
v6.2, v6.1, v6.0, v5.0
|
||||
| Sprint: | Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12 | ||||
| Participants: | |||||
| Description |
|
When two or more contiguous chunks belonging to the same shards are being merged, the shard is sending to the config server a validAfter field set to the current time. This is wrong because merging is not implying any ownership change. Setting an unnecessary value for validAfter has the side effect of potentially breaking snapshot reads. Example assuming history window of 300 seconds:
Purpose of this ticket is to set the validAfter field to the higher validAfter belonging to one of the chunks to merge or - in case of empty history on all of them - not setting it. |
| Comments |
| Comment by Githook User [ 03/Jan/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |
| Comment by Githook User [ 05/Dec/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |