[GitHub] jjrodrig opened a new issue #1136: Error 500 when deleting a db in a cluster without quorum

[GitBox <gi...@apache.org>]

jjrodrig opened a new issue #1136: Error 500 when deleting a db in a cluster without quorum
URL: https://github.com/apache/couchdb/issues/1136
 
 
   <!--- Provide a general summary of the issue in the Title above -->
   
   ## Expected Behavior
   <!--- If you're describing a bug, tell us what should happen -->
   <!--- If you're suggesting a change/improvement, tell us how it should work -->
   When deleting a database in a cluster where the quorum is not met a 202 - Acepted should be returned if at least one of the active nodes responds ok. 
   
   It is related  to issue #603
   
   ## Current Behavior
   <!--- If describing a bug, tell us what happens instead of the expected behavior -->
   <!--- If suggesting a change/improvement, explain the difference from current behavior -->
    When an existing DB is deleted in a cluster without quorum an error 500 is returned. The deletion is done and replicated once the cluster nodes come back. 
   
   ## Possible Solution
   <!--- Not obligatory, but suggest a fix/reason for the bug, -->
   <!--- or ideas how to implement the addition or change -->
   The problem seems to be here
   https://github.com/apache/couchdb/blob/1c39e0c70f8ac1ac5959ae86c84ba9d3f3f9df9e/src/fabric/src/fabric_db_delete.erl#L73
   
   where accepted is returned only if quorum is met
   
   ## Steps to Reproduce (for bugs)
   <!--- Provide a link to a live example, or an unambiguous set of steps to -->
   <!--- reproduce this bug. Include code to reproduce, if relevant -->
   1. Setup a 3 nodes cluster
   2. Create DB - curl -X PUT "http://.../testdb"
   3. Bring 2 of them down
   4. Delete DB - curl -X DELETE "http://.../testdb"
   5. A 500 error is returned
   6. Get DB - curl "http://.../testdb"
   7. 404 - Not found is returned
   
   ## Context
   <!--- How has this issue affected you? What are you trying to accomplish? -->
   <!--- Providing context helps us come up with a solution that is most useful in the real world -->
   The current situation is not consistent with the fix for issue #603
   
   ## Your Environment
   <!--- Include as many relevant details about the environment you experienced the bug in -->
   * Version used: Compiled from master
   * Browser Name and version:
   * Operating System and version (desktop or mobile): Centos 7
   * Link to your project:
   

----------------------------------------------------------------
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