[SERVER-20177] incoming heartbeats should update liveness table Created: 28/Aug/15 Updated: 25/Jan/17 Resolved: 03/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Siyuan Zhou |
| 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: | RPL 9 (09/18/15) |
| Participants: |
| Description |
|
Because the primary does not have knowledge of which secondaries are currently connected via the spanning tree, it can not tell when secondaries are down, unless we depend on heartbeats. |
| Comments |
| Comment by Githook User [ 03/Sep/15 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: |
| Comment by Githook User [ 02/Sep/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: This is the same as updating the table based on incoming updatePosition commands. |
| Comment by Eric Milkie [ 29/Aug/15 ] |
|
We did! But I think I have a way to avoid such issues this time. |
| Comment by Andy Schwerin [ 29/Aug/15 ] |
|
Didn't we remove similar behavior during the development of 3.0, because it prevented failover during asymmetric network partitions? |