StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16058860
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-17T11:30:00.513
FavoriteCount
0
LastActivityDate
2013-04-17T11:52:13.560
LastEditDate
2013-04-17T11:52:13.560
LastEditorUserId
383478
OwnerUserId
383478
ParentId
16058575
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
MongoDB has, at most, an oplog and journal. The oplog is a capped collection of a fixed size as such it will never just grow out of control and the journal has a contained amount of space (normally 3GB). If the document requires to be moved on disk due to growth then yes, the DB can grow in size causing fragmentation within your deleted and free lists. This presentation is good at explaining this concept: <a href="http://www.10gen.com/presentations/storage-engine-internals" rel="nofollow">http://www.10gen.com/presentations/storage-engine-internals</a> As for avoiding that situation, it all depends on what queries you are performing and what updates you are committing. There is no single way to fix the problem and without knowing more about your problem I can only direct you to places. One consideration, if you are making continous, regular, updates which require document movement would be to use power of 2 sizes allocation: <a href="http://docs.mongodb.org/manual/reference/command/collMod/#usePowerOf2Sizes" rel="nofollow">http://docs.mongodb.org/manual/reference/command/collMod/#usePowerOf2Sizes</a> However, most of the time it is a case of tweaking the schema and queries to be more performant, i.e. not creating so much redundancy within subdocuments etc. There is one other place you could see a problem which is within the <code>mongod</code> logs. If you create excessive logging of queries that touch your <code>mongod</code> servers then you could be seeing your logs using up all your space, however, you can solve this problem by limiting just how much log is written or <a href="http://docs.mongodb.org/manual/tutorial/rotate-log-files/" rel="nofollow">http://docs.mongodb.org/manual/tutorial/rotate-log-files/</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODo updates in MongoDB in the same record make the db grow?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSammaye
UserOwnerUserId
1. USSammaye
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODo updates in MongoDB in the same record make the db grow?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.