MongoDB Version 3.2.17 Sharded Cluster Stop Balancer messages, is it normal or issues

3 Shards , Each Shard has 3 nodes ( 1 Primary and 2 Replica Sets)
Config Server is 3 node replica set.

These messages are cause of concern since ping shows old date and message migration may be in progress…

Waiting for active host node-mongo2-3:27017 to recognize new settings… (ping : Mon Oct 18 2021 09:05:00 GMT+0000 (GMT))
Waiting for active host node-mongo1-3:27017 to recognize new settings… (ping : Tue Aug 31 2021 15:28:27 GMT+0000 (GMT))
Waited for active ping to change for host node-mongo1-3:27017, a migration may be in progress or the host may be down.

Stopping Balancer ....
Waiting for active hosts...
Waiting for active host node-mongo3-3:27017 to recognize new settings... (ping : Sat Sep 04 2021 15:53:14 GMT+0000 (GMT))
Waited for active ping to change for host node-mongo3-3:27017, a migration may be in progress or the host may be down.
Waiting for active host node-mongo2-3:27017 to recognize new settings... (ping : Mon Oct 18 2021 09:05:00 GMT+0000 (GMT))
Waiting for active host node-mongo1-3:27017 to recognize new settings... (ping : Tue Aug 31 2021 15:28:27 GMT+0000 (GMT))
Waited for active ping to change for host node-mongo1-3:27017, a migration may be in progress or the host may be down.
Waiting for the balancer lock...
Waiting again for active hosts after balancer is off...
Waiting for active host node-mongo3-3:27017 to recognize new settings... (ping : Sat Sep 04 2021 15:53:14 GMT+0000 (GMT))
Waited for active ping to change for host node-mongo3-3:27017, a migration may be in progress or the host may be down.
Waiting for active host node-mongo1-3:27017 to recognize new settings... (ping : Tue Aug 31 2021 15:28:27 GMT+0000 (GMT))
Waited for active ping to change for host node-mongo1-3:27017, a migration may be in progress or the host may be down.
Warning : host node-mongo3-3:27017 seems to have been offline since Sat Sep 04 2021 15:53:14 GMT+0000 (GMT)
Warning : host node-mongo1-3:27017 seems to have been offline since Tue Aug 31 2021 15:28:27 GMT+0000 (GMT)
WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 })
Checking if the balancer is stopped
Balancer is not running now.
---------

    In config mongos setting ( I can see old ping date too)
    
    db.mongos.find()
    { "_id" : "node-mongo3-3:27017", "mongoVersion" : "3.2.17", "ping" : ISODate("2021-09-04T15:53:14.436Z"), "up" : NumberLong(17679988), "waiting" : false }
    { "_id" : "node-mongo2-3:27017", "mongoVersion" : "3.2.17", "ping" : ISODate("2021-10-25T19:15:04.779Z"), "up" : NumberLong(22098498), "waiting" : true }
    { "_id" : "node-mongo1-3:27017", "mongoVersion" : "3.2.17", "ping" : ISODate("2021-08-31T15:28:27.695Z"), "up" : NumberLong(17330247), "waiting" : false }

rs.printReplicationInfo()  
configured oplog size:   9775.30859375MB
log length start to end: 15014162secs (4170.6hrs)
oplog first event time:  Wed May 05 2021 23:42:53 GMT+0000 (GMT)
oplog last event time:   Tue Oct 26 2021 18:18:55 GMT+0000 (GMT)
now:                     Tue Oct 26 2021 18:18:55 GMT+0000 (GMT)
CR2ConfigRepSet_Prod:SECONDARY> rs.printSlaveReplicationInfo()  
source: node-mongo3-3.mydomain.com:27019
    syncedTo: Tue Oct 26 2021 18:19:11 GMT+0000 (GMT)
    0 secs (0 hrs) behind the primary 
source: node-mongo1-3.mydomain.com:27019
    syncedTo: Tue Oct 26 2021 18:19:11 GMT+0000 (GMT)
    0 secs (0 hrs) behind the primary 
source: node-mongo3-504.mydomain.com:27019
    syncedTo: Tue Oct 26 2021 18:19:11 GMT+0000 (GMT)
    0 secs (0 hrs) behind the primary 


Thanks for looking.

Issue was resolved after I bounced router service of all 3 nodes. So all is well.

Hi @Sanjay_Gupta,

Great to hear you were able to resolve your issue!

However, I would note that MongoDB 3.2 was first released in Dec 2015 and reached end of life in September 2018.

I suggest upgrading to a supported version of MongoDB (currently 4.0 or later) as there have been a lot of improvements in the six years since the 3.2 series was released.

Regards,
Stennie