[SERVER-18680] Mongos should continue to support netstat command when using config servers as replica sets Created: 27/May/15  Updated: 23/Sep/15  Resolved: 23/Sep/15

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

Type: Task Priority: Major - P3
Reporter: John Morales Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-19547 Shard and mongos nodes should report ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding A (10/09/15)
Participants:

 Description   

In MongoDB 3.0 and earlier, the {netstat:1} command provides a comma separated list of config servers.

For example:

mongos> db.adminCommand({netstat:1})
{
	"configserver" : "config1.example.com:27019,config2.example.com:27019,config3.example.com:27019",
	"isdbgrid" : 1,
	"ok" : 1
}

For backward compatibility with applications that parse this output, it would be great if MongoDB 3.2 clusters continued to support and expose the current list of config servers with this format.



 Comments   
Comment by Andy Schwerin [ 23/Sep/15 ]

Re-opening to fix resolution.

Comment by Andy Schwerin [ 23/Sep/15 ]

The netstat command continues to behave as expected on the 3.1 development branch. It reports the "connection string" for the config servers as it knows them. For SCCC config servers, this is a comma separated list with the host-and-port elements. For CSRS config servers, this is the replica set name, followed by a forward slash followed by a comma-separated list of one or more replica set members. E.g., csrsSet/csrs-0.mydomain[,csrs-1.mydomain[, ...]]

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