[SERVER-11266] Error on capped collection TTL deletes blocks other collection deletes (in same db) Created: 18/Oct/13 Updated: 20/Jan/16 Resolved: 21/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | ttl, ttlmonitor | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If you create a TTL index on a capped collection, which should not be allowed, then when documents are found to delete a user assertion is generated, exception thrown, and all unprocessed collections in db are skipped.
|
| Comments |
| Comment by Scott Hernandez (Inactive) [ 21/Jan/15 ] |
|
fixed with |