StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14520577
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-25T11:09:59.877
FavoriteCount
0
LastActivityDate
2013-01-25T11:15:09.377
LastEditDate
2013-01-25T11:15:09.377
LastEditorUserId
1235551
OwnerUserId
1235551
ParentId
14495544
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<ol> <li>Upgrade to 2.2.2 - 2.2.0 has an idempotency bug in replication and no longer recommended for production.</li> <li>See here for general info <a href="http://docs.mongodb.org/manual/faq/storage/#faq-disk-size" rel="nofollow">http://docs.mongodb.org/manual/faq/storage/#faq-disk-size</a></li> <li>The only way to recover space back from mongodb is to either sync a new node over the network - in which case the documents are copied over the the new file system and stored anew without fragmentation. Or to use the repair command - but for that you need double the disk space that you are using on disk. The data files are copied, defragged and compacted and copied back over the original. The compact command is badly named and only defrags - it doesn't recover disk space back from mongo. </li> <li>Going forward, use usePowerOf2Sizes command (new in 2.2.x) <a href="http://docs.mongodb.org/manual/reference/command/collMod/" rel="nofollow">http://docs.mongodb.org/manual/reference/command/collMod/</a> If you use that command and allocate say an 800 byte document, 1024 bytes will be allocated on disk. If you then delete that doc and insert a new one - say 900 bytes, that doc can fit in the 1024 byte space. Without this option enabled, the 800 byte doc might only have 850 bytes on disk - so when it's deleted and the 900 byte doc inserted, new space has to be allocated. And if that is then deleted you will end up with two free space - 850 bytes and 950 bytes which are never joined (unless compact or repair is used) - so then insert a 1000 byte doc and you need to allocate <em>another</em> chunk of disk. usePowerOf2Sizes helps this situation a lot by using standard bucket sizes. </li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy is MongoDB storage constantly increasing?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGregor
UserOwnerUserId
1. USGregor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
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.