[SERVER-6638] Replica set members create/hold first connection to themselves Created: 29/Jul/12  Updated: 20/Feb/15  Resolved: 20/Feb/15

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

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

When you start a replica set member it creates a connection to itself. Not sure if this is an active connection, and/or intentional.

db.currentOp(true) entry:

		{
			"opid" : 8,
			"active" : false,
			"op" : "query",
			"ns" : "local.system.replset",
			"query" : {
				"count" : "system.replset",
				"query" : {
					
				}
			},
			"client" : "192.168.1.100:57714",
			"desc" : "conn1",
			"threadId" : "0x1056c9000",
			"connectionId" : 1,
			"waitingForLock" : false,
			"numYields" : 0
		},

Before 2.1+ it seems to connect from localhost, but now a public address. Not sure if this is intentional either.



 Comments   
Comment by Eric Milkie [ 05/Mar/14 ]

I think it's just using a DBDirectClient to read some data from an internal table. There are easier ways to do this now.

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