[SERVER-13253] Local database 150G on new installation . Created: 18/Mar/14  Updated: 15/Nov/21  Resolved: 18/Mar/14

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

Type: Question Priority: Major - P3
Reporter: Alex Furman Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I am new to mongoDB. We have new installation with 2 sharded clusters. What I noticed that local db is 150G in size and all tables are empty. Repair database does not seems to me helped. I am sure something went wrong and I need to get a root cause of that.

autotrader 0.203125GB
local 156.001953125GB
rs0:PRIMARY> use local
switched to db local
rs0:PRIMARY> show tables
me
oplog.rs
replset.minvalid
slaves
startup_log
system.indexes
system.replset
rs0:PRIMARY> db.me.count()
1
rs0:PRIMARY> db.oplog.rs.count()
6
rs0:PRIMARY> db.replset.minvalid.count()
1
rs0:PRIMARY> db.slaves.count()
2
rs0:PRIMARY> db.startup_log.count()
6
rs0:PRIMARY> db.system.indexes.count()
4
rs0:PRIMARY> db.system.replset.count()
1
rs0:PRIMARY>



 Comments   
Comment by Scott Hernandez (Inactive) [ 18/Mar/14 ]

Please see the docs on the oplog size, and it has a default size: http://docs.mongodb.org/manual/core/replica-set-oplog/#replica-set-oplog-sizing

Also, questions like this are best asked on mongodb-user (https://groups.google.com/group/mongodb-user) and not here in the SERVER project in jira which is to track bugs, feature requests and the like.

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