[
https://issues.apache.org/jira/browse/BOOKKEEPER-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144185#comment-13144185
]
Sijie Guo commented on BOOKKEEPER-105:
--------------------------------------
I just found BOOKKEEPER-49 during testing performance of bookkeeper.
I didn't work on that issue yet. since in Hub server, there is only one ledger
handle opened for a specific ledger, it is not critical for pub/sub :)
if you have idea on this issue, you could fix it in this jira and marked
BOOKKEEPER-49 as duplicated.
> A Bookkeeper can only open one LedgerHandle to a specific ledger at a time,
> if it expects them to work
> ------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-105
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-105
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
>
> If you open two ledger handles pointing to the same ledger, using the same
> client, you will not be able to read from both. This is due to them sharing
> PerChannelBookieClient instances. PerChannelBookieClient has a member
> {code}
> ConcurrentHashMap<CompletionKey, ReadCompletion> readCompletions = new
> ConcurrentHashMap<CompletionKey, ReadCompletion>();
> {code}
> where CompletionKey is the ledgerId and entryId. If both LedgerHandles try to
> read the same entryId, they'll override each other on this hashmap.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
