Glad this worked out. Quick tip then, unless you run this on an 8-core (or more) machine, you might want to look into reducing your q for this database. q=2 or $num_cores is a good rule of thumb. You can use our couch-continuum tool to migrate an existing db: https://npmjs.com/couch-continuum
Cheers Jan — > On 2. May 2019, at 14:17, Frank Röhm <[email protected]> wrote: > > OK, I found it. > In the 8 shards subdirectories (from 00000000-1fffffff to e0000000-ffffffff) > there was still 8 frwiki directories (frwiki.1510609658.couch) with each 5 GB. > I deleted them with: > > find . -name frwiki.1510609658.couch -delete > > from the shards dir and gone they are. > Hopefully it won’t affect my CouchDB, but as I heard this is very robust ;) > > I think I can stick to the v2.x now, no need to downgrade now, ouff. > > frank > >> Am 02.05.2019 um 07:25 schrieb Joan Touzet <[email protected]>: >> >> Look for a .deleted directory under your data/ directory. The files may not >> have been deleted but moved aside due to the enable_database_recovery >> setting, or because the DB was still in use when you restarted CouchDB. >> >> Another useful command is: >> >> $ du -sh /opt/couchdb/data/* >> >> which should tell you where the storage is being used. Does this show >> anything useful to you? >> >> -Joan >> >>> On 2019-05-01 2:22 p.m., Frank Walter wrote: >>> Hello >>> I have CouchDB v2.3.1 (on Ubuntu 14.04) and I use it only for creating >>> Wikipedia databases with mwscrape. >>> My shards folder was too big, over 50 GB big, so I deleted one big db >>> (frwiki) which had 32 GB in Fauxton. That db is gone now. >>> After this, I thought now my shards folder should be about 20 GB but it >>> is still 52 GB. >>> I don't find any documentation about that in the CouchDB Doc. >>> I restarted CouchDB (/etc/init.d/couchdb restart) but nothing changes. >>> How can I reduce the size of shards? How can I get rid of this ghost-db? >>> My next step would be, if I cannot solve this issue, to uninstall >>> CouchDB 2.x and reinstall 1.x, because I dont need that feature of >>> cluster server anyway. I see only inconvenience for my use. >>> Thanks >>> frank >
