-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.2.5
-
Component/s: Sharding
-
Labels:None
-
ALL
-
On a sharded cluster running MongoDb 3.2.5 with WT, multiple mongos processes are created when the CSRS nodes are not up and ready at that time.
During starting the cluster, if the CSRS nodes are not available, I see multiple mongos processes being created which just hang around without serving any client.
[oasprod@chi-ppe-oas001 ~]$ ps -aef | grep mongos oasprod 8728 1 0 13:41 ? 00:00:00 /oas_alias/mongodb/mongodb/bin/mongos --fork --port 29101 --logpath /data_mount/mongodata/mongos/mongos.log --pidfilepath /data_mount/mongodata/mongos/mongos.pid --configdb csReplSet/bxb-ppe-oas002:29102,chi-ppe-oas019:29102,bxb-ppe-oas012:29102 --quiet oasprod 8729 8728 0 13:41 ? 00:00:01 /oas_alias/mongodb/mongodb/bin/mongos --fork --port 29101 --logpath /data_mount/mongodata/mongos/mongos.log --pidfilepath /data_mount/mongodata/mongos/mongos.pid --configdb csReplSet/bxb-ppe-oas002:29102,chi-ppe-oas019:29102,bxb-ppe-oas012:29102 --quiet oasprod 22278 16931 0 13:57 pts/2 00:00:00 grep --color=auto mongos [oasprod@chi-ppe-oas001 ~]$
My expectation is that the mongos process should simply fail instead of exhibiting this behavior.
Attaching the log file from the hanging mongos process.
I had created an issue for the same on the google user forums as well:
https://groups.google.com/forum/#!searchin/mongodb-user/mongos%7Csort:relevance/mongodb-user/b5K9enNl0Cs/PuNszaSQBgAJ