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

Patch for SERVER-4333 for 2.0.x

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 2.1.1
    • Affects Version/s: 2.0.3, 2.0.4
    • Component/s: Replication
    • None
    • Environment:
      Amazon Linux
    • Fully Compatible

      I'm critically blocked on getting our sharded system live until I can differentiate between true user-initiated INSERTs and balancer-driven inserts.

      Fortunately, Milkie is "the man", and has fixed this. Unfortunately, it won't be in stable until 2.2.
      https://github.com/mongodb/mongo/commit/abc3e0cb35c4ab0e837936e04f378c1d963c849b

      I've created a patch, attached here that should apply these changes to 2.0.3. But when I compiled the patch, built my own RPM, and ran it, I didn't see the change. It definitely is running the new 2.0.3 version (I had 2.0.2 on the machine before).

      Milkie, or someone else, is there any other "trick" to getting this behavior to trigger? Would be a huge win for me, this is literally the last blocker on a major rollout. Mongo is ready, but without this, I can't drive our analytics DB properly, so can't go live.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            wkoffel Will Koffel
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: