[
https://issues.apache.org/jira/browse/BOOKKEEPER-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749578#comment-13749578
]
Flavio Junqueira commented on BOOKKEEPER-677:
---------------------------------------------
hi rakesh, the api is not going to allow two clients to write to the same
ledger, so as I understand the problem here, you're bypassing the api and
writing directly through BookieClient. if this is the case, then this is not a
bk client from one of our distributions, it is a rogue client built on top of
BookieClient. if we are to avoid such scenarios, we need to enforce that only
the ledger creator is able to add to the ledger. since security is part of
4.3.0, I wonder if this is not a scenario already cover in other jiras.
> 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
>
>
> 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
