CouchDB 2 global_changes system table gets insanely large

Question

We have a system that basically writes 250 MB of data to our CouchDB 2 instance, which generates ~ 50 GB / day in the global_changes database.

This makes CouchDB2 consumes the entire disk.

Once you get to this state, CouchDB2 goes and never returns.

We would like to know if there is any way to limit the size of the global_changes table or if there is a way to manage this table, for example, a set of best practices.

Answer 1

TL; DR: just delete it

http://docs.couchdb.org/en/latest/install/setup.html#single-node-setup

Status:

Please note that the last one (link to _global_changes) is not required unless you expect to use the global change feed. Feel free to delete this database, if you created it, it has grown in size, and you do not need this function (and you do not want to spend system resources on its constant compaction).