You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2014/02/22 17:31:19 UTC

[jira] [Updated] (BOOKKEEPER-734) Improve the HashedWheelTimer usage in PerChannelBookieClient

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rakesh R updated BOOKKEEPER-734:
--------------------------------

    Attachment: 0001-BOOKKEEPER-734_br_4_2.patch

> 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
>             Fix For: 4.2.3
>
>         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.1.5#6160)