[SERVER-51679] Fix race condition in Free Monitoring when free monitoring document is deleted Created: 15/Oct/20 Updated: 29/Oct/23 Resolved: 09/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2020-11-02, Security 2020-11-16 | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Description |
|
In a replica set, when the config document for free monitoring in admin.system.version is deleted, the deletion is replicated to the secondary. If the secondary sees the deletion between sending metrics to monitoring service and waiting for the reply, the secondary gets into the wrong state. The metrics completion message should be ignored in this situation. Currently, it is processed as if the deletion did not occur. |
| Comments |
| Comment by Githook User [ 09/Nov/20 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |