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

mongod backtrace if shard tag ranges are added before collection is sharded

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.3
    • Component/s: Sharding
    • None
    • ALL
    • Hide

      1. Deploy a 2 shard sharded cluster. Each shard is a PSA replica set.
      2. Add shard tag ranges by upserting directly to config.tags
      3. Shard the collection referred to by the shard tag range

      Show
      1. Deploy a 2 shard sharded cluster. Each shard is a PSA replica set. 2. Add shard tag ranges by upserting directly to config.tags 3. Shard the collection referred to by the shard tag range

      On a 2-shard, PSA sharded cluster, if shard tag ranges are added before a collection is sharded, some shard members will backtrace.

      This appears to be a regression in 4.0.3-rc0. We have not seen this happen in 4.0.2.

      Logs attached.

        1. shard1-2.log
          5 kB
        2. shard1-1.log
          14 kB
        3. shard1-0.log
          2.77 MB
        4. shard0-2.log
          135 kB
        5. shard0-1.log
          10.70 MB
        6. shard0-0.log
          77 kB
        7. mongos.log
          19 kB
        8. csrs2.log
          69 kB
        9. csrs1.log
          73 kB
        10. csrs0.log
          267 kB
        11. config-dump.tar.gz
          2 kB

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            tim.olsen@mongodb.com Timothy Olsen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: