-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
ALL
The following has been observed on v4.4 in a case of large number of namespaces/indexes:
{"t":{"$date":"2022-04-30T02:32:19.131+00:00"},"s":"E", "c":"-", "id":23077, "ctx":"conn48184","msg":"Assertion","attr":{"error":"BSONObjectTooLarge: BSONObj size: 17342353 (0x1089F91) is invalid. Size must be between 0 and 16793600(16MB) First element: failedInitialSyncAttempts: 0","file":"src/mongo/bson/bsonobj.cpp","line":101}}
{"t":{"$date":"2022-04-30T02:32:19.131+00:00"},"s":"I", "c":"INITSYNC", "id":21161, "ctx":"conn48184","msg":"Error creating initial sync progress object","attr":{"error":"BSONObjectTooLarge: BSONObj size: 17342353 (0x1089F91) is invalid. Size must be between 0 and 16793600(16MB) First element: failedInitialSyncAttempts: 0"}}
While this appears to be a non-fatal event, it would be nice to have this code to work regardless of the how many objects needed to be cloned.