[
https://issues.apache.org/jira/browse/BOOKKEEPER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506256#comment-13506256
]
Sijie Guo commented on BOOKKEEPER-49:
-------------------------------------
In order to fix this issue, I think we need a TxnId in request similar as
Hedwig PubSubRequest. Along with it, it might be the time to change
bookkeeper's request to use protobuf. So I would suggest to move this ticket to
4.3.0.
> bookkeeper - parallel async read same entry of same ledger will fail
> --------------------------------------------------------------------
>
> Key: BOOKKEEPER-49
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-49
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
>
> all ledgers shared a PerChannelBookieClient.
> PerChannelBookieClient put all the read requests in a
> ConcurrentHashMap<CompletionKey, ReadCompletion> map called readCompletions,
> which is indexed by CompletionKey. If two read requests have same entryId and
> same ledgerId, they have the same CompletionKey, the latter one will
> overwrite the previous one. So a read request's callback will not be invoked.
> we may need to chain the callbacks for same completion keys.
--
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
