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

Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2017/07/31 21:30:01 UTC

[jira] [Updated] (HBASE-18079) [C++] Optimize ClientBootstrap in ConnectionPool

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

Enis Soztutar updated HBASE-18079:
----------------------------------
    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

Closing this as won't fix. Code around this area is changed now. 

> [C++] Optimize ClientBootstrap in ConnectionPool
> ------------------------------------------------
>
>                 Key: HBASE-18079
>                 URL: https://issues.apache.org/jira/browse/HBASE-18079
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Xiaobing Zhou
>            Assignee: Xiaobing Zhou
>         Attachments: HBASE-18079-HBASE-14850.000.patch
>
>
> ConnectionPool creates an instance of wangle::ClientBootstrap for every new connection (i.e. Wangle pipeline) and cache it hereafter, it is unnecessary. Instead, ConnectionPool can maintain a single ClientBootstrap instance in its members.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)