[SERVER-14967] Migrations are aborted after step2 without a logged reason Created: 20/Aug/14  Updated: 25/Jun/15  Resolved: 13/Nov/14

Status: Closed
Project: Core Server
Component/s: Diagnostics, Logging, Sharding
Affects Version/s: 2.6.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Greg Studer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-14080 Have migration result reported in the... Closed
Related
Operating System: ALL
Steps To Reproduce:
  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
Participants:

 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.



 Comments   
Comment by Greg Studer [ 13/Nov/14 ]

Issue is fixed by SERVER-14080 - follow that ticket for backport progress.

Generated at Thu Feb 08 03:36:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.