[
https://issues.apache.org/jira/browse/BOOKKEEPER-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-734:
----------------------------------
Fix Version/s: (was: 4.2.3)
> Improve the HashedWheelTimer usage in PerChannelBookieClient
> ------------------------------------------------------------
>
> Key: BOOKKEEPER-734
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-734
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.2.2
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: 0001-BOOKKEEPER-734_br_4_2.patch
>
>
> Observed two potential cases about the HashedWheelTimer usage:
> # Unnecessary creation of HashedWheelTimer for each channel connection
> establishment. Instead of creating for each channel connection, we could
> create one timer per bookie client and close it during permanent closure.
> # Handle IllegalStateException of HashedWheelTimer.releaseExternalResources()
--
This message was sent by Atlassian JIRA
(v6.2#6252)
