[SERVER-15424] Check compatibilty of connection behavior in new heartbeats Created: 26/Sep/14 Updated: 03/Mar/15 Resolved: 22/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc3 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We have changed how heartbeats work via the executor and the underlying connections are different than how 2.6 worked. We should investigate how this compares and affects monitoring wrt how 2.6 worked. Plan:
|
| Comments |
| Comment by Githook User [ 09/Dec/14 ] | ||||
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: | ||||
| Comment by Githook User [ 09/Dec/14 ] | ||||
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: | ||||
| Comment by Githook User [ 08/Dec/14 ] | ||||
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: | ||||
| Comment by Githook User [ 08/Dec/14 ] | ||||
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: | ||||
| Comment by Githook User [ 08/Dec/14 ] | ||||
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: By capping the lifetime of connections used for heartbeats at 30 seconds, we | ||||
| Comment by Amalia Hawkins [ 25/Nov/14 ] | ||||
|
No, a new primary is not elected. The "No address associated with hostname" message appears multiple times, and the replSet attempts to sync for 10 seconds repeatedly. | ||||
| Comment by Andy Schwerin [ 24/Nov/14 ] | ||||
|
amalia.hawkins@10gen.com, the question is, do the remaining nodes ever elect another primary? | ||||
| Comment by Amalia Hawkins [ 24/Nov/14 ] | ||||
|
Under case (1), the replica set realizes DNS issues when the primary's hostname changes.
| ||||
| Comment by Andy Schwerin [ 24/Nov/14 ] | ||||
|
There are two major divergences from 2.6 behavior here, at least one of which might need to be remedied for 2.8.0
|