[SERVER-9283] lastHeartbeatRecv flaps between invalid and valid dates Created: 08/Apr/13 Updated: 11/Jul/16 Resolved: 23/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.1, 2.5.0 |
| Fix Version/s: | 2.4.5, 2.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Hannes Magnusson | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
build info: Darwin anden.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49 |
||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Every once in a while the lastHeartbeatRecv date stamp gets screwed up while initialising a replicaset. Note: This is completely fresh replicaset with no data inserted yet
|
| Comments |
| Comment by auto [ 19/Jun/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Do not overwrite lastHeartbeatRecv with 0 value everytime HeartbeatInfo gets updated. |
| Comment by auto [ 23/May/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Do not overwrite lastHeartbeatRecv with 0 value everytime HeartbeatInfo gets updated. |
| Comment by Jenny Duckett [ 07/May/13 ] |
|
I'm also seeing this very frequently on our replica set, which contains data and is in use. Nearly every time I run rs.status() on any member of the set, for at least one of the other two members it will show "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"). I haven't been able to find any pattern to the flapping between valid and invalid dates. Our replica set is now running version 2.4.3. We started seeing this issue after upgrading from 2.2.3 to 2.4.1. At the same time we also started to be affected by SERVER-9085, which is now resolved. I'd hoped that the fix for that introduced in 2.4.2 might also fix the lastHeartbeatRecv issue, but it hasn't. |
| Comment by Matt Campbell [ 11/Apr/13 ] |
|
I'm also seeing this on a replica set when just running rs.status() repeatedly. The lastHeartbeatRecv bounces from ISODate("1970-01-01T00:00:00Z") to ISODate("2013-04-11T01:26:11Z"). Note: this is happening WITHOUT data in the rs - as it was mentioned below it occurred after adding data. |
| Comment by Hannes Magnusson [ 08/Apr/13 ] |
|
Hmh. I am seeing this on a running replicaset too, after inserting some data |