-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.2.0
-
Component/s: None
-
None
-
Environment:Mix CentOS 5.8,6.2, and 6.3. All Mongo upgraded from 2.0.6 to 2.2.0 via RPM(YUM).
There are 2 sharded replication sets with 3 configd servers. Each replication set has 3 servers. Mongos run in each client (web server). All client connect to localhost to use MongoDB.
(NOTE: When upgraded from 2.0.6, We didn't run mongod --upgrade since it's not instructed in Changelog)Mix CentOS 5.8,6.2, and 6.3. All Mongo upgraded from 2.0.6 to 2.2.0 via RPM(YUM). There are 2 sharded replication sets with 3 configd servers. Each replication set has 3 servers. Mongos run in each client (web server). All client connect to localhost to use MongoDB. (NOTE: When upgraded from 2.0.6, We didn't run mongod --upgrade since it's not instructed in Changelog)
-
Linux
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We encountered the following errors a couple of times on PRIMARY master of each of our replication set.
Mon Sep 3 11:02:17 [conn38] Assertion: 10334:Invalid BSONObj size: -286331391 (0x01EEEEEE) first element: ^A: ?type=108
When this happened, the SECONDARY take over. Starting PRIMARY again will yield the same error. We have to remove all data files and have former PRIMARY re-replicate from current PRIMARY.
Note that, this problem never occured before.
Attach are log files from 2 of our PRIMARY servers.
- duplicates
-
-
- Closed
-