[SERVER-349] support more than 10 indexes Created: 09/Oct/09  Updated: 12/Jul/16  Resolved: 22/Oct/09

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 1.1.3

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Dwight Merriman
Resolution: Done Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by auto [ 29/Sep/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-349 merge
http://github.com/mongodb/mongo/commit/eb8927dd5b1cb51d70f94b5d1de67f0da8c36863

Comment by Dwight Merriman [ 22/Oct/09 ]

up to 40 now

Comment by Dwight Merriman [ 19/Oct/09 ]

this may already be fixed in the latest code.

was this happening with 1.0?

can someone try it with latest code?

Comment by David Wolf [ 19/Oct/09 ]

An issue which is likely related occurs when adding a combined index with more than 10 keys. It seems to kill the mongod process and leave an index which is unusable but also impossible to remove.

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