[
https://issues.apache.org/jira/browse/BOOKKEEPER-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750187#comment-13750187
]
Sijie Guo commented on BOOKKEEPER-677:
--------------------------------------
this ticket is duplicated of BOOKKEEPER-443. we raised the deletion semantic
discussion when introducing improved gc algorithm. as previous discussion, we
preferred similar filesystem semantic, when a concurrent deletion happened, the
writer could still write data to it but those entries will be garbage collected
eventually. so it is the application responsibilities for concurrent deletion.
otherwise, we mess up bookkeeper to handle too complex problem.
> BookieClient is successfully adding entries to a deleted ledger
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-677
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-677
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.0.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments:
> 0001-BOOKKEEPER-677-testcase-to-simulate-the-problem.java,
> 0002-BOOKKEEPER-677-testcase-to-simulate-the-problem.patch
>
>
> Multiple bkclients are allowed to perform operation on same ledger, this
> violates the SingleWriter contract.
> BookieClient is successfully adding entries to the ledger without knowing
> that another bkclient has come and deleted the ledger itself. Causing serious
> dataloss to the applications which might be thinking the data would be
> successfully written to the ledger.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
