[SERVER-71436] Range deleter must not aggressively spam the log when shard key index not found Created: 17/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: | 4.4.19, 5.0.15, 6.0.4, 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v6.2, v6.1, v6.0, v5.0, v4.4
|
||||||||
| Sprint: | Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12 | ||||||||
| Participants: | |||||||||
| Description |
|
The range-deleter is deleting orphaned documents by scanning an index compatible with the shard key. When no index on the shard key is found on a shard trying to perform orphans deletion, the range-deleter starts to spam the logs aggressively and indefinitely with the "Unable to find shard key index" error; this results in a relevant increase on the log file size up to some GBs per hour. Purpose of this ticket is to:
|
| Comments |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 05/Dec/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |