調整原因：

1.原有分片是兩個SECONDARY，查詢時開發人員也很少設置成
const string RP_SECONDARY = "secondary" ;
const string RP_SECONDARY_PREFERRED = "secondaryPreferred" ;
此類讀優化

2.昨天出現誤操作，把一個表的部分數據刪除了。

3.正好手頭上多了一臺用來備份的服務器，但測試使用文件備份mongodump
的方法，發現備份時性能不理想。
數量量大，半天也還沒全部備份完成，跑shell，出現錯誤：
Failed: error running `listIndexes`. Collection: `dp.tb_bid` Err: read tcp 127.0.0.1:28011: i/o timeout

這個錯誤好幾臺服務器都同出現。


計劃達到目的：

1.增加備份節點，以保證數據安全（誤操作：比如刪除數據，修改數據）
2.兩個次節點的，減少集群同步消耗，優化插入性能，同時 slaveDelay 節點不建立索引。
3.slaveDelay 節點設置成前臺不可見（不可查詢數據）

具體性能，還得后面跟進，看看效果。



原架構

set?? ??? ?host：port?? ??? ??? ?stateStr?? ??? ??? ??? ??? ??? ??? ??? ??? ?
----------------------------------------------------------
shard1?? ??? ?192.168.0.11:27011?? ??? ?PRIMARY?? ??? ??? ??? ??? ?
shard1?? ??? ?192.168.0.13:27011?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ?
shard1?? ??? ?192.168.0.17:27011?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ??? ??? ?

shard2?? ??? ?192.168.0.11:27012?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ?
shard2?? ??? ?192.168.0.15:27012?? ??? ?PRIMARY?? ??? ??? ??? ??? ?
shard2?? ??? ?192.168.0.19:27012?? ??? ?SECONDARY?? ??? ??? ??? ?

shard3?? ??? ?192.168.0.13:27013?? ??? ?PRIMARY?? ??? ??? ??? ??? ?
shard3?? ??? ?192.168.0.15:27013?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ?
shard3?? ??? ?192.168.0.19:27013?? ??? ?ARBITER?? ??? ??? ??? ??? ?

shard4?? ??? ?192.168.0.15:27011?? ??? ?ARBITER?? ??? ??? ??? ??? ?
shard4?? ??? ?192.168.0.17:27012?? ??? ?PRIMARY?? ??? ??? ??? ??? ??? ??? ??? ??? ?
shard4?? ??? ?192.168.0.19:27011?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ??? ??? ?


調整后：

set?? ??? ?host：port?? ??? ??? ?stateStr?? ??? ??? ??? ??? ??? ??? ??? ??? ?
-------------------------------------------------------------
shard1?? ??? ?192.168.0.11:27011?? ??? ?PRIMARY?? ??? ??? ??? ??? ?
shard1?? ??? ?192.168.0.13:27011?? ??? ?slaveDelay?? ??? ??? ??? ??? ??? ??? ??? ?
shard1?? ??? ?192.168.0.17:27011?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ??? ??? ?

shard2?? ??? ?192.168.0.11:27012?? ??? ?slaveDelay?? ??? ??? ??? ??? ??? ??? ??? ?
shard2?? ??? ?192.168.0.15:27012?? ??? ?PRIMARY?? ??? ??? ??? ??? ?
shard2?? ??? ?192.168.0.19:27012?? ??? ?SECONDARY?? ??? ??? ??? ?

shard3?? ??? ?192.168.0.13:27013?? ??? ?PRIMARY?? ??? ??? ??? ??? ?
shard3?? ??? ?192.168.0.15:27013?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ?
shard3?? ??? ?192.168.0.21:27011?? ??? ?slaveDelay?? ??? ??? ??? ??? ?

shard4?? ??? ?192.168.0.21:27012?? ??? ?slaveDelay?? ??? ??? ??? ??? ?
shard4?? ??? ?192.168.0.17:27012?? ??? ?PRIMARY?? ??? ??? ??? ??? ??? ??? ??? ??? ?
shard4?? ??? ?192.168.0.19:27011?? ??? ?SECONDARY?? ??? ??? ??? ??? ??? ??? ??? ??? ??? ?


刪除 ARBITER 節點，另外增加slaveDelay 節點：
[mongo@ms3 bin]$ ./mongo -port 27011
rs.remove("192.168.0.19:27013");
rs.add({_id: 2, host:'192.168.0.21:27012',"slaveDelay":36000,"priority":0,"hidden":true,"buildIndexes":true});

總結

以上是生活随笔為你收集整理的MONGODB 集群架构 调整，增加延迟备份节点服务器，删除仲裁节点的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。