Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-29282

BSON Document Size can be exceeded when grouping inserts on SECONDARY nodes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.7, 3.5.11
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v3.4
    • Repl 2017-06-19, Repl 2017-07-31

      During steady state replication, due to the way that SECONDARY nodes group 'insert' oplog entries, the BSON maximum document size of 16MB may be exceeded if we try to group together a batch that include documents at or near the 16MB limit.

      The predicate for how we delimit a group cuts off the group at the first op that exceeds the group size limit, but when we put these ops into a group here, it could put us over a maximum document size when we try to construct a BSON object here. This is due to the incorrect way that we measure the size of a batch. Given a list of ops, we start iterating from the second op, and initialize the batchSize to zero. Thus, we don't actually include the size of the first op in our measurement of the batch size, which is how we could be allowed to exceed document size limits when our ops are very close to 16MB.

      The logic in place to handle insert grouping is somewhat hard to follow as is. This bug can be addressed by limiting batch sizes correctly by including the sizes of all ops, and making sure we delimit the group correctly based on this. Ideally, the grouping logic can be cleaned up at the same time to make it more clear that is correct.

      A JS test reproducing this issue is attached. It reproduced the issue reliably running on MongoDB 3.5.7.

            william.schultz@mongodb.com William Schultz
            william.schultz@mongodb.com William Schultz
            0 Vote for this issue
            8 Start watching this issue