[BOOKKEEPER-49] bookkeeper - parallel async read same entry of same ledger will fail

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 4.0.0, 4.1.0
• Component/s: bookkeeper-client
• Assignee: Sijie Guo
• Reporter: Sijie Guo
• Created: 16/Aug/11 11:21
• Updated: 07/Oct/14 09:49
• Resolved: 26/Jul/14 06:53

Description

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.

Issue Links

• depends upon: BOOKKEEPER-587 Make BK use protobufs on the wire
• depends upon: BOOKKEEPER-558 change bookkeeper request/response protocol to use protobuf
• is depended upon by: BOOKKEEPER-516 TestSpeculativeRead failed in Jenkins
• is duplicated by: BOOKKEEPER-105 A Bookkeeper can only open one LedgerHandle to a specific ledger at a time, if it expects them to work
• is related to: BOOKKEEPER-302 No more messages delivered when hub server scans messages over two ledgers.
• relates to: BOOKKEEPER-582 Make bookie and client use protobuf for requests (non-wire part)