[SERVER-24018] Balancing Server's sharding metadata manager failed asking for instance is manually reset Created: 03/May/16  Updated: 03/May/16  Resolved: 03/May/16

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

Type: Question Priority: Major - P3
Reporter: virendra agarwal Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

My MongoS servers are not staring they are sending this error in logs.

SHARDING [Balancer] caught exception while doing balance: Server's sharding metadata manager failed to initialize and will remain in this state until the instance is manually reset :: caused by :: HostNotFound: unable to resolve DNS for host confserv_1.xyz.com

2016-05-02T17:57:06.612+0530 I SHARDING [Balancer] about to log metadata event into actionlog: { _id: "DB2255-2016-05-02T17:57:06.611+0530-5727479aa1051c5fb04fcc49", server: "mongoS1", clientAddr: "", time: new Date(1462192026611), what: "balancer.round", ns: "", details:

{ executionTimeMillis: 35, errorOccured: true, errmsg: "Server's sharding metadata manager failed to initialize and will remain in this state until the instance is manually reset :: caused by :: HostNotFoun..." }

}

When I connect config server using host name it is working fine.
I tried to restart MongoS server it is not coming up.

Thanks
Virendra Agarwal



 Comments   
Comment by Ramon Fernandez Marina [ 03/May/16 ]

Thanks for your report agarwal.viren@gmail.com. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Comment by virendra agarwal [ 03/May/16 ]

I checked Mongo code and found this error mentioned in
https://github.com/mongodb/mongo/blob/master/src/mongo/db/s/sharding_state.cpp

    / TODO: remove after v3.4.
    // This is for backwards compatibility with old style initialization through metadata
    // commands/setShardVersion. As well as all assignments to _initializationStatus and
    // _setInitializationState_inlock in this method.
    if (_getInitializationState() == InitializationState::kInitializing) {
        auto waitStatus = _waitForInitialization_inlock(deadline, lk);
        if (!waitStatus.isOK()) {
            return waitStatus;
        }
    }
 
    if (_getInitializationState() == InitializationState::kError) {
        return {ErrorCodes::ManualInterventionRequired,
                str::stream() << "Server's sharding metadata manager failed to initialize and will "
                                 "remain in this state until the instance is manually reset"
                              << causedBy(_initializationStatus)};
    }  

But it does not mention anything what manual intervention is required.

Thanks
Viren

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