[
https://issues.apache.org/jira/browse/BOOKKEEPER-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749627#comment-13749627
]
Rakesh R commented on BOOKKEEPER-677:
-------------------------------------
Thanks [~fpj] for the comment. Please have a look at the latest patch where
I;ve used two independent clients. Also I've used only the exposed apis from
BookKeeper clients.
When I look at the code, bk#delete api is just removing it from the zookeeper
ledger metadata and not actually deleting from the bkservers. Its GC
responsibility to do the actual the cleanups but it takes another gc cycle to
occur, on the other side the creator of the ledger is silently able to add
entries to this ledger. I feel its not the case of security, its similar case
when two clients acting on the same ledger(SingleWriter contract). What do you
feel?
> 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
