[
https://issues.apache.org/jira/browse/COUCHDB-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976458#action_12976458
]
Robert Newson commented on COUCHDB-1003:
----------------------------------------
I mean that any rename operation takes the same time as any other (the amount
of work required is the same).
It's trivial to verify that deleting a large file takes time (as every block
needs to be marked as free), just make a large file and then delete it.
It's true that other tests have sleeps and waits in them but since
replication.js was working for you until very recently without the sleep I
would rather find and treat the cause than the symptom.
> deleting db file is asynchronous & file rename in couch_file:delete
> -------------------------------------------------------------------
>
> Key: COUCHDB-1003
> URL: https://issues.apache.org/jira/browse/COUCHDB-1003
> Project: CouchDB
> Issue Type: Question
> Components: Database Core
> Reporter: Benoit Chesneau
>
> I wonder why we spawn the file deletion when we delete a database. On slow io
> machine it introduces latency. I don't see any reason we make this deletion
> asynchronous ?
> About couch_file:delete, we first rename the file before deleting it. Why are
> we doing that ? Is this for windows ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
