MONGODB 回滾失敗
MONGODB 回滾失敗:
{
"_id" : 5,
"name" : "192.168.190.7:27018",
"health" : 1,
"state" : 4,
"stateStr" : "FATAL",
"uptime" : 63,
"optime" : Timestamp(1414132121, 1),
"optimeDate" : ISODate("2014-10-24T06:28:41Z"),
"lastHeartbeat" : ISODate("2014-06-08T12:10:55Z"),
"lastHeartbeatRecv" : ISODate("2014-06-08T12:10:56Z"),
"pingMs" : 0,
"lastHeartbeatMessage" : "rollback error: not willing to roll back more than 30 minutes of data"
}
],
檢視資料:
In some cases, MongoDB decides that the rollback is too large to undertake. Rollback
can fail if there are more than 300 MB of data or about 30 minutes of operations to roll
back. In these cases, you must resync the node that is stuck in rollback
如下進行重新配置:
首先刪除出錯的節點
rs.remove("192.168.190.7:27018")
然後停止原出錯節點,刪除所有的資料檔案。並且按照配置重啟
[root@testora1 db]# rm -rf *
./mongod ~/.mongodb.conf
加入節點
rs.add({"_id":5,"host":"192.168.190.7:27018","priority":1})
這樣及可以進行重新配置
檢視狀態
{
"_id" : 5,
"name" : "192.168.190.7:27018",
"health" : 1,
"state" : 5,
"stateStr" : "STARTUP2",
"uptime" : 602,
"optime" : Timestamp(1413699079, 2838693),
"optimeDate" : ISODate("2014-10-19T06:11:19Z"),
"self" : true
}
],
{
"_id" : 5,
"name" : "192.168.190.7:27018",
"health" : 1,
"state" : 4,
"stateStr" : "FATAL",
"uptime" : 63,
"optime" : Timestamp(1414132121, 1),
"optimeDate" : ISODate("2014-10-24T06:28:41Z"),
"lastHeartbeat" : ISODate("2014-06-08T12:10:55Z"),
"lastHeartbeatRecv" : ISODate("2014-06-08T12:10:56Z"),
"pingMs" : 0,
"lastHeartbeatMessage" : "rollback error: not willing to roll back more than 30 minutes of data"
}
],
檢視資料:
In some cases, MongoDB decides that the rollback is too large to undertake. Rollback
can fail if there are more than 300 MB of data or about 30 minutes of operations to roll
back. In these cases, you must resync the node that is stuck in rollback
如下進行重新配置:
首先刪除出錯的節點
rs.remove("192.168.190.7:27018")
然後停止原出錯節點,刪除所有的資料檔案。並且按照配置重啟
[root@testora1 db]# rm -rf *
./mongod ~/.mongodb.conf
加入節點
rs.add({"_id":5,"host":"192.168.190.7:27018","priority":1})
這樣及可以進行重新配置
檢視狀態
{
"_id" : 5,
"name" : "192.168.190.7:27018",
"health" : 1,
"state" : 5,
"stateStr" : "STARTUP2",
"uptime" : 602,
"optime" : Timestamp(1413699079, 2838693),
"optimeDate" : ISODate("2014-10-19T06:11:19Z"),
"self" : true
}
],
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7728585/viewspace-1346197/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- win10系統itunes安裝失敗正在回滾怎麼解決Win10
- mongodb啟動失敗問題解決MongoDB
- 失敗的十年,回顧反思
- mongodb安裝失敗如何徹底刪除MongoDB
- 回滾操作、回滾段的理解
- mongodb資料庫連結失敗如何解決MongoDB資料庫
- yum安裝mongodb啟動失敗怎麼解決MongoDB
- oracle前滾和回滾Oracle
- ORACLE 前滾和回滾Oracle
- 回顧自己三次失敗的面試經歷面試
- MongoDB例項重啟失敗探究(大事務Redo導致)MongoDB
- Java的快速失敗和安全失敗Java
- oracle回滾溯源Oracle
- ORACLE回滾段Oracle
- 誤操作經歷,truncate導致閃回查詢失敗
- 快速失敗機制&失敗安全機制
- git push程式碼失敗,鑑權失敗Git
- Oracle 資料回滾Oracle
- Mac回滾iTunes版本Mac
- ORACLE回滾段(1)Oracle
- ORACLE回滾段(2)Oracle
- ORACLE回滾段(轉)Oracle
- ORACLE回滾段管理Oracle
- win10退回win7失敗怎麼解決_win10換回win7失敗處理方法Win10Win7
- Begin end程式碼段裡面有DDL和DML,如果DDL成功了而DML失敗了,則DDL的程式碼也會回滾
- Win7 Nginx啟動失敗 cmd命令失敗Win7Nginx
- SQL code----檢視回滾段名稱及大小 回滾段的管理SQL
- 介面,失敗品
- 安裝失敗????
- 求職失敗求助!!求職
- 以失敗為機制:奇異人生中的真實失敗與虛構性失敗
- Spring Boot 事物回滾Spring Boot
- java 事務提交/回滾Java
- ORACLE 回滾段詳解Oracle
- dota2啟動失敗 初始化vulkan失敗
- 入門Kubernetes - 滾動升級/回滾
- 關於前滾(roll forward)和回滾(roll back)Forward
- 鎖表時KILL SESSION及回滾段監控(回滾時間評估)Session