jjrodrig commented on issue #1139: Fix for issue #1136 - Error 500 deleting DB 
without quorum
URL: https://github.com/apache/couchdb/pull/1139#issuecomment-370928857
   Thanks @kocolosk  for your comments.
   I see that the orphaned files question is a different issue. We are facing 
it as part of a cleanup process that we have implemented in our system. 
Databases are periodically transferred to a temporary database and then moved 
back to the work database. It is like a purging procedure that allows us to 
keep the databases small. During this process we are removing and creating 
databases and orphaned files are produced. **+1 for the orphaned files cleanup 
process enhancement.**
   Respect to the main issue of this PR, I think that the main problem is to 
respond with a `500 Error` when the operation has been accepted and the 
database is deleted on the nodes that have received the request. It is 
responding with an error but the database is deleted in the active nodes, and 
later on propagated to the rest of nodes once they are accessible. It seem to 
me that this behaviour is more akin to a `202 Accepted` result.
   The idea of responding `200 Ok` in the case that the quorum is met is mainly 
to keep the API consistent with other operations where the quorum is considered 
but I see that this can have some drawbacks.

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:

With regards,
Apache Git Services

Reply via email to