MongoDB副本集集群從節(jié)點(diǎn)控制臺(tái)報(bào)錯(cuò)10061怎么辦

這篇文章主要介紹MongoDB副本集集群從節(jié)點(diǎn)控制臺(tái)報(bào)錯(cuò)10061怎么辦，文中介紹的非常詳細(xì)，具有一定的參考價(jià)值，感興趣的小伙伴們一定要看完！

--------------------------------------------------------------------------------------------------------------------------------------------
    首先查看集群3個(gè)節(jié)點(diǎn)的控制臺(tái)日志

1、集群三臺(tái)服務(wù)器控制臺(tái)日志

192.168.72.33

2018-01-05T09:46:24.281+0800 I STORAGE [initandlisten] Placing a marker at optime Jan 05 05:16:28:3e9 
2018-01-05T09:46:24.432+0800 I NETWORK [HostnameCanonicalizationWorker] Starting hostname canonicalization worker 
2018-01-05T09:46:24.432+0800 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory 'd:/mongodata/rs0-2/diagnostic.data' 
2018-01-05T09:46:24.443+0800 I NETWORK [initandlisten] waiting for connections on port 27013 
2018-01-05T09:46:25.485+0800 W NETWORK [ReplicationExecutor] Failed to connect 
to 192.168.72.31:27011, reason: errno:10061 由于目標(biāo)計(jì)算機(jī)積極拒絕，無(wú)法連接。 
2018-01-05T09:46:25.533+0800 I REPL [ReplicationExecutor] New replica set co 
nfig in use: { _id: "rs0", version: 8, protocolVersion: 1, members: [ { _id: 0, 
host: "mongodb-rs0-0:27011", arbiterOnly: false, buildIndexes: true, hidden: fal 
se, priority: 100.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 1, host: "mongo 
db-rs0-1:27012", arbiterOnly: false, buildIndexes: true, hidden: false, priority 
: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "mongodb-rs0-2:27013 
", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: { 
}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatInte 
rvalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, getLas 
tErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: Obje 
ctId('59365592734d0747ee26e2a6') } } 
2018-01-05T09:46:25.534+0800 I REPL [ReplicationExecutor] This node is mongo db-rs0-2:27013 in the config

192.168.72.32

2018-01-05T09:46:17.064+0800 I NETWORK [HostnameCanonicalizationWorker] Starting hostname canonicalization worker 
2018-01-05T09:46:17.064+0800 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory 'd:/mongodata/rs0-1/diagnostic.data' 
2018-01-05T09:46:17.076+0800 I NETWORK [initandlisten] waiting for connections on port 27012 
2018-01-05T09:46:18.102+0800 W NETWORK [ReplicationExecutor] Failed to connect 
to 192.168.72.31:27011, reason: errno:10061 由于目標(biāo)計(jì)算機(jī)積極拒絕，無(wú)法連接。 
2018-01-05T09:46:19.149+0800 W NETWORK [ReplicationExecutor] Failed to connect 
to 192.168.72.33:27013, reason: errno:10061 由于目標(biāo)計(jì)算機(jī)積極拒絕，無(wú)法連接。 
2018-01-05T09:46:19.150+0800 I REPL [ReplicationExecutor] New replica set co 
nfig in use: { _id: "rs0", version: 8, protocolVersion: 1, members: [ { _id: 0, 
host: "mongodb-rs0-0:27011", arbiterOnly: false, buildIndexes: true, hidden: fal 
se, priority: 100.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 1, host: "mongo 
db-rs0-1:27012", arbiterOnly: false, buildIndexes: true, hidden: false, priority 
: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "mongodb-rs0-2:27013 
", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: { 
}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatInte 
rvalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, getLas 
tErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: Obje 
ctId('59365592734d0747ee26e2a6') } } 
2018-01-05T09:46:19.150+0800 I REPL [ReplicationExecutor] This node is mongo db-rs0-1:27012 in the config

192.168.72.31

2018-01-05T15:56:42.999+0800 I STORAGE [initandlisten] Placing a marker at optime Jan 05 05:12:59:b4a 
2018-01-05T15:56:43.000+0800 I STORAGE [initandlisten] Placing a marker at optime Jan 05 05:13:08:8df 
2018-01-05T15:56:43.000+0800 I STORAGE [initandlisten] Placing a marker at optime Jan 05 05:14:05:329 
2018-01-05T15:56:43.001+0800 I STORAGE [initandlisten] Placing a marker at optime Jan 05 05:15:30:25f 
2018-01-05T15:56:43.002+0800 I STORAGE [initandlisten] Placing a marker at optime Jan 05 05:15:39:4b1

    根據(jù)以上日志信息推測(cè)：由于集群主節(jié)點(diǎn)192.168.72.31發(fā)生存儲(chǔ)類型的等待事件，導(dǎo)致主節(jié)點(diǎn)192.168.72.31拒絕2個(gè)從節(jié)點(diǎn)192.168.72.32/33的TCP連接

2、根據(jù)步驟1中的提示，查看mongo服務(wù)在操作系統(tǒng)層次的日志，操作系統(tǒng)日志從2018-1-5 4:59:25秒就已經(jīng)告警提示D盤已經(jīng)滿載

3、查看192.168.72.31存儲(chǔ)情況，果然如操作系統(tǒng)日志提示，D盤只剩余58MB的可用空間

4、由以上信息可以斷定：由于Mongo集群主節(jié)點(diǎn)192.168.72.31存儲(chǔ)空間滿，導(dǎo)致主節(jié)點(diǎn)192.168.72.31的Mongo進(jìn)程無(wú)法完成寫操作從而拒絕2個(gè)從節(jié)點(diǎn)的連接導(dǎo)致整個(gè)mongo集群服務(wù)中斷。經(jīng)溝通得知，地市技術(shù)對(duì)當(dāng)前Mongo主節(jié)點(diǎn)192.168.72.31數(shù)據(jù)做了備份，沒有注意到D盤存儲(chǔ)情況。
事后，地市技術(shù)立即刪除節(jié)點(diǎn)192.168.72.31的冗余數(shù)據(jù)備份釋放D盤空間，由于調(diào)度程序處于僵死狀態(tài)，地市技術(shù)決定重啟整個(gè)mongo集群服務(wù)器192.168.72.31/32/33。

5、重啟完成后，mongo集群恢復(fù)正常，主節(jié)點(diǎn)192.168.72.31的mongo控制臺(tái)提示調(diào)度程序bmi被接受連接到mongo集群的admin庫(kù)

以上是“MongoDB副本集集群從節(jié)點(diǎn)控制臺(tái)報(bào)錯(cuò)10061怎么辦”這篇文章的所有內(nèi)容，感謝各位的閱讀！希望分享的內(nèi)容對(duì)大家有幫助，更多相關(guān)知識(shí)，歡迎關(guān)注億速云行業(yè)資訊頻道！