[SERVER-43094] Problem to set up a Cluster with MongoDB 4.2 Created: 30/Aug/19  Updated: 30/Aug/19  Resolved: 30/Aug/19

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: 4.2.0
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Rui Ribeiro 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-43093 Concurrent calls to ShardingReplicaSe... Closed
Operating System: ALL
Participants:

 Description   

Hi

I setup the cluster with MongoDB 4.0 without problems, but  I am struggling to setup a cluster with MongoDB 4.2.

As soon as I add more than 3 shards  to the cluster (I would like to have up to 24), I am not able to run a mongos anymore. It looks fine until the first restart of the mongos process. When I remove all shards and only keep 3 of them, everything is fine again. It does not matter which shard I keep, it seems something with the number of > 3. 

I tried a lot of things, removed auth, removed encryption, removed compression: no luck.

I cannot believe that this is a bug in 4.2.0 because even in the highest loglevel with exception tracing I cannot see any errors, the mongos is just not starting up until the point when it should start listening on all interfaces (with net.bindIpAll true) or on localhost (started with no special interface binding).

Can you give me some help regarding this problem I am facing.

Thank you

 



 Comments   
Comment by Kaloian Manassiev [ 30/Aug/19 ]

Closing this ticket in place of SERVER-43093.

Generated at Thu Feb 08 05:02:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.