[SERVER-77471] Do not log range deletion task registration on shard secondaries Created: 25/May/23 Updated: 29/Oct/23 Resolved: 25/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc3 |
| 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: |
v7.0
|
||||
| Sprint: | Sharding EMEA 2023-05-29 | ||||
| Participants: | |||||
| Description |
|
Since the range deleter observer runs on any node of a shard, also secondaries may try to register tasks on the range deleter service. This is fine because the registration on secondaries will fail and be gracefully handled by the observer. Purpose of this ticket is to move this log line after the acquisition of the mutex (only successful on the primary) in order not to log it on secondaries. |
| Comments |
| Comment by Githook User [ 26/May/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 25/May/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |