[SERVER-46086] OpObservers to submit ranges for deletion should not run on secondaries Created: 11/Feb/20 Updated: 29/Oct/23 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2020-02-24 | ||||
| Participants: | |||||
| Linked BF Score: | 25 | ||||
| Description |
|
The affected OpObservers are: We have this existing way to check if the node is primary from within the ShardServerOpObserver. |
| Comments |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}Message: |