[SERVER-21188] schedule only one outstanding liveness item of work Created: 28/Oct/15 Updated: 04/Nov/15 Resolved: 29/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl B (10/30/15) |
| Participants: |
| Description |
|
When we schedule a liveness update in replication, we need to make sure there aren't any outstanding updates already scheduled – otherwise, they will leak and continue to reschedule themselves forever. |
| Comments |
| Comment by Githook User [ 29/Oct/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |