CODEWITHSUNDEEP
arangodb
Deepak Agarwal
Deepak Agarwal

Reputation: 905

Strange disk space utilization by collections in arangodb

I have 2 collections (edge collection) and both have similar type of data. Each have around 400k documents. But one of the collection occupies more than double of the disk space. I am wondering why it is like that. I do a lot of update/replace. Could it be because arangodb keeps all the revisions? 90% space is occupied by datafiles. If it's because of the revisions how can I disable persisting the revisions.

Upvotes: 1

Views: 480

Answers (1)

dothebart
dothebart

Reputation: 6077

Usually the compactor thread is intended to clean up unused WAL-files. This was already done by ArangoDB. Thus the files using the space weren't shown in ls anymore.

The situation was caused by disabling the compactor thread to save system performance, thus many files were released at once.

However, for some reason arangod didn't close the file handles, which resulted in the file system not releasing the space of the deleted files.

This could be resolved by restarting the ArangoDB daemon - on shut down the held file handles were closed and the space released.

Meanwhile the issue of non-closing WAL-files has been fixed and is available as of ArangoDB 2.8.6

Upvotes: 3

Related Questions