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

acquiring balancer lock may fail and get stuck with concurrent write traffic

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.0.0-rc6
    • Affects Version/s: 2.4.12, 2.6.5, 2.7.8
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • Hide
      • setup a shard with 3 shards/3 config server/1 mongos
      • start concurrent insert traffic (more than 10 connections)
      • check chunk distribution regularly, there are around 50% chance that chunks are not balanced,
      Show
      setup a shard with 3 shards/3 config server/1 mongos start concurrent insert traffic (more than 10 connections) check chunk distribution regularly, there are around 50% chance that chunks are not balanced,

      during concurrent insert testing, saw chunk stay with the primary shard without being balanced. assertion error in log file.

        1. config-db-dump-1.tar.gz
          67 kB
        2. config-db-dump-2.tar.gz
          67 kB
        3. config-db-dump-3.tar.gz
          67 kB
        4. config-dump.tar.gz
          64 kB
        5. imbalanced_chunks.png
          imbalanced_chunks.png
          25 kB
        6. mongod-primary-shard.log.gz
          1.02 MB

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            rui.zhang Rui Zhang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: