Hi @nickva @wohali, thank you for answering. @wohali what you ask is in my first post, see `curl localhost:5984/demo`→`full-output.json` and `"doc_del_count": 0`. No documents were deleted.
@nickva thanks a lot for the detailed explanation: it was hard to find technical info on where do these strange files come from. In our servers: - 79% (around 4000000 docs) are like `_local/002b9f5977bdb93052d1134208d7458d`, - 20% (around 1000000 docs) are like `_local/shard-sync-0hbIroIo7GAdeFZTS--0Fw-JTBmB5z2AIBLtN3dFM_ryQ`, - 0.8% (around 40000 docs) are like `_local/Jqbpr4ZvrEGCtSLLtWcpHw==` (these ones come from [PouchDB](https://github.com/pouchdb/pouchdb)). 1. For the `_local/002b9f5977bdb93052d1134208d7458d` type, can we safely delete old ones? Is there a risk of breaking CouchDB by "corrupting" ongoing replications? 2. Is there a way to delete the `_local/shard-sync-0hbIroI...` type? Is it safe? Attempts to `curl -X DELETE` them return `{"error":"not_found","reason":"missing"}`. 3. We don't do live replications. Is it normal that `_local/shard-sync-0hbIroI...` checkpoints stay here for months? Is it a bug? something we're doing wrong? or a misunderstanding from us? [ Full content available at: https://github.com/apache/couchdb/issues/1621 ] This message was relayed via gitbox.apache.org for [email protected]
