[SERVER-25744] Don't log about distlock ping failures due to NotMaster on secondaries Created: 22/Aug/16 Updated: 19/Nov/16 Resolved: 19/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Nathan Myers |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2016-09-19, Sharding 2016-10-10 |
| Participants: |
| Description |
|
When a config server process starts up it starts the distlock pinger. The distlock pinger, however, doesn't check if the node is primary before trying to ping the distributed lock. This is fine from a correctness perspective, but it fills the logs on config server secondaries with unnecessary messages like
|
| Comments |
| Comment by Githook User [ 19/Sep/16 ] |
|
Author: {u'name': u'Nathan Myers', u'email': u'ncm@asperasoft.com'}Message: |