Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-43094

Problem to set up a Cluster with MongoDB 4.2

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 4.2.0
    • Component/s: Upgrade/Downgrade
    • Labels:
    • ALL


      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


            Unassigned Unassigned
            rui.ribeiro@comfone.com Rui Ribeiro
            0 Vote for this issue
            4 Start watching this issue