[SERVER-12811] hidden nodes don't always display syncingTo field Created: 20/Feb/14  Updated: 10/Dec/14  Resolved: 14/Aug/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.9
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Roy Smith Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-14702 ReplSetGetStatus show syncingTo for s... Closed
Operating System: ALL
Participants:

 Description   

We're in the process of upgrading all our servers from 2.2.2 to 2.4.9. I noticed after one of the upgrades that some of our secondaries are not showing syncingTo data. It appears to only affect hidden members. See, for example, the output below. db1f is hidden.

On another replica set, I had two hidden nodes. Neither was showing syncingTo data. When I unhid one of them, the field showed up in the rs.status() output.

I know the non-syncingTo-data members are indeed replicating because I can do queries and observe new data appearing.

SECONDARY> rs.status()
{
	"set" : "songza-new",
	"date" : ISODate("2014-02-20T23:25:30Z"),
	"myState" : 2,
	"syncingTo" : "db1e.songza.com:27017",
	"members" : [
		{
			"_id" : 4,
			"name" : "db1b.songza.com:27017",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 28048,
			"optime" : {
				"t" : 1392938730000,
				"i" : 70
			},
			"optimeDate" : ISODate("2014-02-20T23:25:30Z"),
			"lastHeartbeat" : ISODate("2014-02-20T23:25:30Z"),
			"lastHeartbeatRecv" : ISODate("2014-02-20T23:25:30Z"),
			"pingMs" : 1,
			"syncingTo" : "db1e.songza.com:27017"
		},
		{
			"_id" : 6,
			"name" : "db1e.songza.com:27017",
			"health" : 1,
			"state" : 1,
			"stateStr" : "PRIMARY",
			"uptime" : 28048,
			"optime" : {
				"t" : 1392938729000,
				"i" : 20
			},
			"optimeDate" : ISODate("2014-02-20T23:25:29Z"),
			"lastHeartbeat" : ISODate("2014-02-20T23:25:29Z"),
			"lastHeartbeatRecv" : ISODate("2014-02-20T23:25:30Z"),
			"pingMs" : 0
		},
		{
			"_id" : 7,
			"name" : "db1c.songza.com:27017",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 28048,
			"optime" : {
				"t" : 1392938728000,
				"i" : 131
			},
			"optimeDate" : ISODate("2014-02-20T23:25:28Z"),
			"lastHeartbeat" : ISODate("2014-02-20T23:25:28Z"),
			"lastHeartbeatRecv" : ISODate("2014-02-20T23:25:29Z"),
			"pingMs" : 0,
			"syncingTo" : "db1e.songza.com:27017"
		},
		{
			"_id" : 8,
			"name" : "db1d.songza.com:27017",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 28048,
			"optime" : {
				"t" : 1392938728000,
				"i" : 176
			},
			"optimeDate" : ISODate("2014-02-20T23:25:28Z"),
			"lastHeartbeat" : ISODate("2014-02-20T23:25:28Z"),
			"lastHeartbeatRecv" : ISODate("2014-02-20T23:25:30Z"),
			"pingMs" : 1,
			"syncingTo" : "db1e.songza.com:27017"
		},
		{
			"_id" : 9,
			"name" : "db1f.songza.com:27017",
			"health" : 1,
			"state" : 2,
			"stateStr" : "SECONDARY",
			"uptime" : 38524,
			"optime" : {
				"t" : 1392938730000,
				"i" : 123
			},
			"optimeDate" : ISODate("2014-02-20T23:25:30Z"),
			"self" : true
		}
	],
	"ok" : 1
}



 Comments   
Comment by Roy Smith [ 20/Feb/14 ]

FWIW, we're running on Ubuntu Precise.

Generated at Thu Feb 08 03:29:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.