[SERVER-30937] Migration failed because of `already exists with different options` Created: 04/Sep/17 Updated: 15/Nov/21 Resolved: 01/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Zhang Youdong | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Create a shared cluster Step1: enable sharding for test database
Step2: create index for some colletion
Shard1 (primary shard for test database)
Shard2
Step3: shardCollection for test.coll
Step4: create index again with different option
Shard1 (primary shard)
Shard2
Now two shards have the same index with different IndexOption, the migration will never success. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The migration in shared cluster stopped because of "transfer data error", after dive into the log and source code, I found that the migration dest failed when create index.
I have the three questions about this problem? 1. why invalid IndexOption can be specified when createIndex? f |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 01/Nov/19 ] |
This is addressed in
As of I'm going to close this ticket as a duplicate. |
| Comment by conan [ 09/Nov/17 ] |
|
this bug causes a online problem, looking forward |
| Comment by Zhang Youdong [ 08/Sep/17 ] |
|
What's the progress of this issue? I noticed it's not assigned for few dayes. |
| Comment by Zhang Youdong [ 04/Sep/17 ] |
|
Affect version: MongoDB 3.2.13 |