-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Write Ops
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Here is an error that was returned to application - a multi update with giant array of $in values to update:
com.mongodb.WriteConcernException: {
"serverUsed" : "big-cache-1.Socialite-Stage.6519.mongodbdns.com:27017" ,
"ok" : 1 ,
"n" : 0 ,
"updatedExisting" : true ,
"err" : "multiple errors for op : BSONObj size: 17599963 (0x10C8DDB) is invalid. Size must be between 0 and 16793600(16MB) :: and :: BSONObj size: 17599963 (0x10C8DDB) is invalid. Size must be between 0 and 16793600(16MB) :: and :: BSONObj size: 17599963 (0x10C8DDB) is invalid. Size must be between 0 and 16793600(16MB)" , "code" : 65 ,
"causedBy" : [
{ "index" : 0 , "code" : 10334 , "errmsg" : "BSONObj size: 17599963 (0x10C8DDB) is invalid. Size must be between 0 and 16793600(16MB)"} , { "index" : 0 , "code" : 10334 , "errmsg" : "BSONObj size: 17599963 (0x10C8DDB) is invalid. Size must be between 0 and 16793600(16MB)"} ,
{ "index" : 0 , "code" : 10334 , "errmsg" : "BSONObj size: 17599963 (0x10C8DDB) is invalid. Size must be between 0 and 16793600(16MB)"}
]
}
It might just be mongos aggregating together shard results and the shards were impacted by SERVER-14123?
- duplicates
-
-
- Closed
-