[BOOKKEEPER-620] PerChannelBookieClient race during channel disconnect

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.2.2, 4.3.0
• Component/s: bookkeeper-client
• Assignee: Ivan Kelly
• Reporter: Sijie Guo
• Created: 07/Jun/13 00:58
• Updated: 06/Aug/13 17:25
• Resolved: 28/Jun/13 16:00

Description

channel & state are not synchronized in PerChannelBookieClient#closeInternal. so it might cause state is set to CONNECTED but the netty channel is closed by mistake in closeInternal.

Issue Links

• breaks: BOOKKEEPER-668 Race between PerChannelBookieClient#channelDisconnected() and disconnect() calls can make clients hang while add/reading entries in case of multiple bookie failures