[SERVER-21591] Support more than 64 indexes per collection (at least 200) Created: 20/Nov/15  Updated: 08/Mar/18  Resolved: 20/Nov/15

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: 2.6.11, 3.0.7, 3.2.0-rc3
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Chad Kreimendahl Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12250 support arbitrary numbers of indexes Backlog
Participants:

 Description   

We're regularly running into the limitation on 64 indexes per collection. Due to the nature in which we store our customer data, which is highly dynamic, we often run into the need to individually index more than 64 fields.

This is greatly impacting performance capabilities for our use case.

Given the type of metadata we store with each record, the indexes have been a great way for us to ensure absolute performance when the users are filtering their dynamic content.

Due to the above, when we fully index every sortable and filterable field for users, we end up having an index size that is 6-10% of the collection size.

Realizing that we can't do compound indexes past 2, there's still tons of value for us in creating significantly more indexes when needed.

Please up the limit from 64 to at least 256, possibly 512.



 Comments   
Comment by Sheng Hu [ 08/Mar/18 ]

When is possible to remove MMAPV1 and support arbitrary numbers of indexes?

Comment by Scott Hernandez (Inactive) [ 20/Nov/15 ]

Dup of your previously filed issue: SERVER-12250

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