[SERVER-10539] Missed index for sharding key Created: 16/Aug/13 Updated: 06/Dec/22 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Sharding |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nazar Volynets | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: Ubuntu 12.04 |
||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | MongoDB sharded cluster. Please use Mongo shell to reproduce this issue:
As you can see there is index for sharding key of sharding_test.test1 collection and no index for sharding key of sharding_test.test2. Moreover there is no any exception observed. Expected result (any one is acceptible):
|
||||||||||||||||||||||||||||||||||||||||||||
| Participants: |
| Description |
|
Mongo doesn't create an index for sharding key if index name (constructed by mongo in background) exceeds 128 characters. As result such case of sharded collection without index for sharding key will cause performance degradation. Additionally reproduced this issue by using Mongo Java Driver 2.9.3 with write concern 2 (REPLICAS_SAFE) - the same situation, no any exception observed. |
| Comments |
| Comment by Kaloian Manassiev [ 06/Sep/18 ] |
|
This is a very old report and given that we have continuous integration tests which exercise this logic, we believe it is no longer a problem. |
| Comment by Asya Kamsky [ 25/Sep/13 ] |
|
Possibly related issue - |