[SERVER-81372] Collection defragmentation phases sporadically jump backward Created: 22/Sep/23 Updated: 16/Nov/23 Resolved: 02/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.1, 7.1.0-rc1 |
| Fix Version/s: | 7.2.0-rc0, 7.0.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Paolo Polato |
| 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: |
v7.1
|
||||||||||||||||
| Sprint: | Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 15 | ||||||||||||||||
| Description |
|
In On the other hand we use majority read to start/resume defragmentation, so it could happen that we miss the last phase update since it was not majority committed yet. |