[SERVER-63334] Fix logic in chunk info comparator object Created: 07/Feb/22 Updated: 29/Oct/23 Resolved: 15/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Paolo Polato | 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 | ||||
| Participants: | |||||
| Linked BF Score: | 184 | ||||
| Description |
|
It has been detected that the comparison functor used in the "MoveAndMergeChunks" phase of the defragmentation algorithm to sort the list of chunk infos doesn't comply with the Compare named requirement (in particular, with the restriction about Strict weak orderings). |
| Comments |
| Comment by Githook User [ 15/Feb/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |
| Comment by Githook User [ 14/Feb/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |
| Comment by Githook User [ 08/Feb/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |