You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/02/21 16:19:24 UTC
[GitHub] jjrodrig commented on issue #1139: Fix for issue #1136 - Error 500 deleting DB without quorum
jjrodrig commented on issue #1139: Fix for issue #1136 - Error 500 deleting DB without quorum
URL: https://github.com/apache/couchdb/pull/1139#issuecomment-367381444
@rnewson I've done some more testing on the deletion with different cluster conditions. It seems that some .couch files keep orphaned if a database is deleted with one of the nodes of the cluster stopped.
- Start 3-node cluster and create test db:
```
./dev/run -n 3 --with-admin-party-please
curl -X PUT http://127.0.0.1:15984/test?q=1
```
*One .couch file is created per node*
- Stop 1 node in the cluster and delete the database
```
./dev/run -n 3 --with-admin-party-please --degrade-cluster 1
curl -X DELETE http://127.0.0.1:15984/test
```
*The .couch is removed and persist in the stopped node as expected*
- Start the complete cluster and check if the database is deleted
```
./dev/run -n 3 --with-admin-party-please
curl -X HEAD http://127.0.0.1:15984/test -v
```
*The database is not found but the .couch file is propagated from the restarted node to the rest*
It seems that .couch file keeps orphaned in the system after a deletion with at least a node stopped. This PR does not modify this behavior. Do you think, this is an issue?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services