[SERVER-6173] Indexes in capped collection and it size Created: 22/Jun/12  Updated: 15/Aug/12  Resolved: 22/Jun/12

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

Type: Question Priority: Critical - P2
Reporter: Azat Khuzhin Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Is index in capped collection increase it size?
If so, is it doing once (for summary size of index)?
Or when capped collection rotated (already full, and starting from first offset), index size will be increased too?



 Comments   
Comment by Azat Khuzhin [ 25/Jun/12 ]

Thanks, but to clarify, the size of index "on disk" also have an upper bound?

Comment by Eliot Horowitz (Inactive) [ 22/Jun/12 ]

It will follow normal btree patterns.
So will be at worst 50% full, and then sized based on the contents of the collection.
So there will be an upper bound on the size, not infinite.

Comment by Azat Khuzhin [ 22/Jun/12 ]

So, the size of index, will grow?

Comment by Scott Hernandez (Inactive) [ 22/Jun/12 ]

The data for the documents is capped only. The indceexes are stored separately, not in the preallocated space during the capped colllection creation.

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