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

Migrations are aborted after step2 without a logged reason

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 2.6.3
    • Fix Version/s: None
    • Component/s: Diagnostics, Logging, Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      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

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              greg_10gen Greg Studer
              Reporter:
              alex.komyagin Alexander Komyagin
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: