我的MongoS服务器没有开始运行,而是在日志中发送此错误。
分片均衡器在执行平衡时捕获异常:服务器的切分元数据管理器初始化失败,并将保持在此状态,直到实例被手动重置: HostNotFound:无法解析主机confserv_1.xyz.com的DNS
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..." } } 当我用主机名连接配置服务器时,它正常工作。
我试着重新启动MongoS服务器,但没有启动。
我检查了Mongo代码,发现了在
/ 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)};
} 但它没有提到任何需要人工干预的地方。目前的Mongo版本是3.2.6
发布于 2016-06-28 16:13:25
我只是在尝试强化安全配置时遇到了这个问题。与您的情况一样,我能够从所有mongos实例连接到配置服务器。
在我的例子中,我还测试了一个案例,复制集的成员位于不同的数据中心,只有在steppingDown进行了一些初级测试之后,我才遇到了这个问题。
最后,我注意到,不是因为错误消息是假装的,这个问题发生在一个数据中心的一些主服务器上,他们无法路由回配置服务器。在修复路由问题(/etc/host最终)之后,芒果一侧不再出现问题。
https://stackoverflow.com/questions/36982869
复制相似问题