-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.0.6
-
Component/s: Replication
-
Labels:
-
Environment:three Mongo config server
one Mongos
i have create one shard
> cfg = {
_id : "webex11_shard1",
members : [
{_id : 0, host : "10.224.88.109:27018", tags : {"DC": "SJ"}, priority:2},
{_id : 1, host : "10.224.88.110:27018", tags : {"DC": "SJ"}, priority:1},
{_id : 2, host : "10.224.88.160:27018", tags : {"DC": "TX"}, priority:1},
{_id : 3, host : "10.224.88.161:27018", tags : {"DC": "TX"}, priority:1},
{_id : 4, host : "10.224.88.163:27018", tags : {"DC": "LONDON"}, priority:0}
]
}three Mongo config server one Mongos i have create one shard > cfg = { _id : "webex11_shard1", members : [ {_id : 0, host : "10.224.88.109:27018", tags : {"DC": "SJ"}, priority:2}, {_id : 1, host : "10.224.88.110:27018", tags : {"DC": "SJ"}, priority:1}, {_id : 2, host : "10.224.88.160:27018", tags : {"DC": "TX"}, priority:1}, {_id : 3, host : "10.224.88.161:27018", tags : {"DC": "TX"}, priority:1}, {_id : 4, host : "10.224.88.163:27018", tags : {"DC": "LONDON"}, priority:0} ] }
-
Linux
when I use multhiThread to call insert , it cause tow secondaryNode Disk fully, but check the rs.status() I have confuse why the 10.224.88.160 not sync the right optlog with 10.224.88.109(PRI) 10.224.88.110(normally Secondary), seems it only keep in touch with other two nodes which have disk fully\
detail pls check the two attachments
EDIT: in this replica set, 10.224.88.160 is syncing from either 10.224.88.161 or 10.224.88.163 - both have the same error (out of disk space) and have stopped syncing from the PRIMARY. This means that 10.224.88.60 is now also falling behind the primary even though it is not in error. This issue to be fixed here is that a node should check the error status of the node it is syncing from and switch to sync from another node if there is an error status.
https://groups.google.com/forum/?fromgroups=#!topic/mongodb-user/k0XaKb0vH3s
