[BOOKKEEPER-602] we should have request timeouts rather than channel timeout in PerChannelBookieClient

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.0, 4.2.1
• Fix Version/s: 4.3.0, 4.2.3
• Component/s: bookkeeper-client
• Assignee: Aniruddha
• Reporter: Sijie Guo
• Created: 05/Apr/13 19:03
• Updated: 10/Mar/14 02:00
• Resolved: 10/Mar/14 02:00

Description

currently we only have readTimeout in netty channel, it timeouts only when there is no activities in that channel, but it can't track timeouts of individual requests. if a channel continues having read entry activities, it might shadow a slow add entry response, which is bad impacting add latency.