couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-326) Occasional {"error":"error","reason":"eacces"} errors deleting a database on Windows
Date Tue, 22 Nov 2011 23:36:42 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155567#comment-13155567
] 

Dave Cottlehuber commented on COUCHDB-326:
------------------------------------------

Resolved since quite a while I believe. I've not seen any errors in the test suite for this
since 1.0, and cannot repro on current 1.1.1.

Running these in parallel shells on CouchDB 1.1.1 produces 0 errors, and leaves behind no
dbs, although a fair bit of laptop heat:

dave@akai /tmp % while (( i++ < 5000 )) { curl --silent -X PUT http://172.16.40.128:5984/db$i
; }                                          
dave@akai /tmp % while (( i++ < 5000 )) { curl --silent -X DELETE http://172.16.40.128:5984/db$i
; }                                          

Anybody reporting this issue I would strongly advise they ensure that they have AV programs
skipping their var/lib/couch/ just in case.
                
> Occasional {"error":"error","reason":"eacces"} errors deleting a database on Windows
> ------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-326
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-326
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.9
>         Environment: Windows, couch 0.9, erlang R12B 5.6.5
>            Reporter: Mark Hammond
>
> On Windows, occasionally you will see errors attempting to delete a database.   This
manifests itself by 10-30% of the test suite failing on Windows.  If you retry the tests that
failed, they will usually pass on subsequent attempts.  Running the tests individually causes
them to fail roughly 10% of the time.
>  The log output shown is:
>   [debug] [<0.18650.6>] httpd 500 error response:
>    {"error":"error","reason":"eacces"}
>   [info] [<0.18650.6>] 127.0.0.1 - - 'DELETE' /test_suite_db/ 500
> A slightly snipped transcript from IRC:
> (2:58:32 PM) markh: I see a number of INFO logs "Shutting down view group server, monitored
db is closing." directly before the error.  I was guessing the file may be unlink'd before
one of those workers actually closes its handle?
> (2:58:54 PM) alisdair: yeah, it's probably a race condition
> (2:59:13 PM) alisdair: where the delete is tried before the fd is let go
> (2:59:26 PM) alisdair: the reader fd that is
> (2:59:32 PM) markh: yeah
> ...
> (3:11:47 PM) alisdair: i can't find an obvious deadlock
> (3:12:18 PM) alisdair: couch_server:delete explicitly waits for the db process to exit
> (3:12:23 PM) alisdair: before deleting it
> (3:15:15 PM) alisdair: i think i found the problem
> (3:15:23 PM) alisdair: but i need a windows machine to confirm
> (3:15:30 PM) alisdair: i'll look into it tomorrow

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message