[
https://issues.apache.org/jira/browse/COUCHDB-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976462#action_12976462
]
Benoit Chesneau commented on COUCHDB-1003:
------------------------------------------
what I say is that we should wait for complrtr deletion in my opinion. Whatever
the time it take. Delete isn't a common operation and it should be handeld like
it. On a more general view spawning an operztion without checking it doesn't
finish isn't so good...
I'm not sure it is recent. Already had such error. Also please reopen the bug
if you think it's needed. This one wasn't related.
> 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.
