[jira] [Resolved] (BOOKKEEPER-49) bookkeeper - parallel async read same entry of same ledger will fail

["Sijie Guo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo resolved BOOKKEEPER-49.
---------------------------------

    Resolution: Won't Fix

after moving to protobuf in BOOKKEEPER-582, we used txn id to track requests. this issue will not exist anymore. so close it as 'Won't Fix'

> 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
>
>         Attachments: 0001-BOOKKEEPER-49-bookkeeper-parallel-async-read-same-en.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)