[
https://issues.apache.org/jira/browse/BOOKKEEPER-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010035#comment-14010035
]
Ivan Kelly commented on BOOKKEEPER-756:
---------------------------------------
I think we should skip it for 4.2. I think 4.2 should be in critical fix only
mode after 4.2.3, and we should concentrate on 4.3.0.
> Use HashedwheelTimer for request timeouts for PCBC
> --------------------------------------------------
>
> Key: BOOKKEEPER-756
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-756
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-client
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0, 4.2.3
>
> Attachments: BOOKKEEPER-756.diff, BOOKKEEPER-756.v2.diff
>
>
> Current scheduler based timeout mechanism is per batch, which isn't
> efficient. HashedWheelTimer is much better for timeouts. So change the PCBC
> to use HashedWheelTimer for timeouts.
> Besides that HashedWheelTimer change, it also provides multiple channel per
> bookie support for latency consideration.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
