[SERVER-37046] "Unable to auto-split" message in ChunkSplitter when top chunk fails is misleading Created: 07/Sep/18 Updated: 29/Oct/23 Resolved: 28/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2019-01-28, Sharding 2019-02-11 |
| Participants: |
| Description |
|
This log line says "Unable to auto-split chunk" for any exception that is thrown, even if it was from the moveChunk command after the split already succeeded. This line is misleading since the autosplit may have worked but the moveChunk may have failed. The logging should be more granular. |
| Comments |
| Comment by Githook User [ 28/Jan/19 ] |
|
Author: {'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz'}Message: |