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

elemMatchProjection.js incorrectly assumes that shell generates monotonically increasing _id values

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.14, 3.6.3, 3.7.2
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
    • Fully Compatible
    • ALL
    • v3.6, v3.4
    • Query 2018-02-12
    • 0

      The elemMatchProjection.js integration test has various assertions which sort by _id, and depend on this sort enforcing a particular ordering. The test, however, does not supply explicit _id values. It instead relies on the shell generating ObjectIds, and it assumes that these ObjectIds are monotically increasing.

      This is not a sound assumption. As documented here, the least significant three bytes of an ObjectId consist of an incrementing counter which is seeded with a random value. If the uint32_t seed is close to 0xffffffff, then during the execution of the test, the counter will roll over to zero. If this occurs, the sort order of the _id values will not match the shell's insertion order, causing the test to fail.

      The test fails consistently after building the server with the following patch:

      diff --git a/src/mongo/bson/oid.cpp b/src/mongo/bson/oid.cpp
      index 26d90d97ba..00f0159f1d 100644
      --- a/src/mongo/bson/oid.cpp
      +++ b/src/mongo/bson/oid.cpp
      @@ -54,7 +54,7 @@ OID::InstanceUnique _instanceUnique;
       (InitializerContext* context) {
           std::unique_ptr<SecureRandom> entropy(SecureRandom::create());
      -    counter.reset(new AtomicUInt32(uint32_t(entropy->nextInt64())));
      +    counter.reset(new AtomicUInt32(uint32_t(0xffffff35)));
           _instanceUnique = OID::InstanceUnique::generate(*entropy);
           return Status::OK();

      This replaces random seeding of the ObjectId counter with a hardcoded value of 0xffffff35, designed to demonstrate the problem.

            david.storch@mongodb.com David Storch
            david.storch@mongodb.com David Storch
            0 Vote for this issue
            2 Start watching this issue