Mongodb compact

Ops and Admin Sharding
1

Hello team,

we have a 3 node sharded cluster and we are trying to delete the unused data from the collections, but after the delete the disk space was not released back to the OS.

can anyone provide me the details on running the compact command from a mongod instance? looks like running compact from mongos is not supported in 3.0.4

2

Its going to block the database.
You need to run it on each member.

The collection will reuse the space so if you’re adding data to it still, you may just want to leave it.

And obigatory: 3.0.4 is old, really old.

1 Like
3

Hi @personal_java and welcome in the MongoDB Community :muscle: !

MongoDB is currently in version 6.0.3.

V3.0.4 was born in March 2015 and reached end of life support in Feb 2018 according to MongoDB Legacy Support Policy.

So my first suggestion would be to update this cluster to 6.0.3 ASAP and there are good chances that your problem could just go away with the upgrade.

Are you still running on MMAPv1 or are you using WiredTiger?

Cheers,
Maxime.

4

reg 3.0.4 yea, we just have this one cluster and others are migrated to Atlas. we are in process of moving this one too… soon!

Do you have any specific commands that I need toexecute the compact command from mongod?

Thanks

1 Like
5

Thank you so much for the reply
we are on wiredtiger

1 Like
6

I would go with db.runCommand ( { compact: 'mydb.mycollection', force: true } ). But yeah if you can move to Atlas, just forget about it and migrate. Problem solved.

2 Likes
7

The command is as @MaBeuLux88 replied.

But per the link in my previous reply MMAPv1 or wiredTiger will tield different results.

MMAPv1 wont’t release storage back. You’ll need to perform an initial sync in that case.

8

I tried running that from the mongos instance. but looks like it is not supported. How can we run it from a mongod instance ?

9

Direct connect on each mongod, and each secondary too, its not replicated.

Its on the page too: compact — MongoDB Manual

10

Thank you for the link. this is what I get when I try to connect to mongo shell from the instance where mongod is running.

MongoDB shell version: 3.0.4
connecting to: test
2022-12-01T15:55:08.719+0000 W NETWORK  Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
2022-12-01T15:55:08.720+0000 E QUERY    Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed
    at connect (src/mongo/shell/mongo.js:179:14)
    at (connect):1:6 at src/mongo/shell/mongo.js:179
exception: connect failed.


Here is our set uo : 
1. mongos server
 /opt/mongo/bin/mongos --configdb m1.qa..com:27019,m2.qa..com:27019,m3.qa..com:27019

2. 3 mongod servers 
 /opt/mongo/bin/mongod --dbpath /mongodb/configdb --port 27019 --storageEngine wiredTiger
 /opt/mongo/bin/mongod --dbpath /mongodb/sharddb --port 27018 --storageEngine wiredTiger
11

As per your commands(and standard for shard replset members) the port is 27018

1 Like
12

that is it. i’m able to connect. Thank you so much for your help.

2 Likes