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

Migrations are aborted after step2 without a logged reason

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.6.3
    • Component/s: Diagnostics, Logging, Sharding
    • None
    • ALL
    • Hide
      1. create a sharded collection on 2 shards with the key {x:"hashed"}
      2. populate the collection with some dummy data
      3. connect directly to the shard 2 and drop the shard key index
      4. try moving chunks from shard 2 to shard 1
      5. observe migrations failing without a specific error
      Show
      create a sharded collection on 2 shards with the key {x:"hashed"} populate the collection with some dummy data connect directly to the shard 2 and drop the shard key index try moving chunks from shard 2 to shard 1 observe migrations failing without a specific error

      If a particular shard misses the shard key index, any migrations from it will fail, which is expected.

      What is unexpected, is that no explicit error is logged even with loglevel 1, basically leaving the operator guessing what's wrong.

            Assignee:
            greg_10gen Greg Studer
            Reporter:
            alex.komyagin@mongodb.com Alexander Komyagin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: