Skip to content

_global_changes is growing fast and others questions #3822

Discussion options

You must be logged in to vote

We see that the _global_changes is the one responsible of the size. Can we delete it?

Yes, if you don't use the _db_updates endpoint you can delete this database.

Other question, we clone the VMs in a test env and we did delete the db directories of the 2 nodes of 200gb so they start resync and now they are 20gb each. Is this the correct procedure? We lost anything?

The individual shard replicas are only eventually consistent with one another; in an environment where you are regularly writing to a given database deleting 2 out of 3 copies does run the risk of losing updates that were reported as committed. It's a low risk, though, as CouchDB does eagerly try to write to all 3 copies o…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by nickva
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants