Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CouchDB data folder is getting bigger and bigger #464

Closed
larryaubstore opened this issue Mar 30, 2017 · 3 comments
Closed

CouchDB data folder is getting bigger and bigger #464

larryaubstore opened this issue Mar 30, 2017 · 3 comments

Comments

@larryaubstore
Copy link

Hi, I just noticed that CouchDB data folder is getting big very quickly. I use this docker image: https://github.com/klaemo/docker-couchdb (Tag 2.0.0)

The fix I found for the moment is to call manually 'http:https://couchdbserver/{dbname}/_view_cleanup' on each database.

Before cleanup, the database took 5GB and after cleanup the database take 86M.

It there a way to configure automatically the 'clean_up' task ?

@janl
Copy link
Member

janl commented Mar 30, 2017

@janl janl closed this as completed Mar 30, 2017
@larryaubstore
Copy link
Author

Thank you for the quick response. Do you have an example somewhere ?

I added this config in local.ini but it does not seem to work:

_default = [{db_fragmentation, "70%"}, {view_fragmentation, "60%"}, {from, "07:00"}, {to, "11:00"}]

Do I have to specify the databases somewhere ?

@larryaubstore
Copy link
Author

larryaubstore commented Mar 31, 2017

The automatic compaction does not seem to work. I tried with 5%, it is never triggered:

_default = [{db_fragmentation, "5%"}, {view_fragmentation, "5%"}, {from, "07:00"}, {to, "11:00"}]

There is an other thing that it is not clear to me. Does '_clean_up' operation included in compaction ?

nickva pushed a commit to nickva/couchdb that referenced this issue Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants