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

Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/08/07 13:21:00 UTC

[jira] [Updated] (HBASE-26182) Allow disabling refresh of connection registry endpoint

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

Duo Zhang updated HBASE-26182:
------------------------------
    Description: 
One possible deployment in production is to use something like a lvs in front of all the region servers to act as a LB, so client just need to connect to the lvs IP instead of go to the region server directly to get registry information.

For this scenario we do not need to refresh the endpoints any more.

The simplest way is to set the refresh interval to -1.

  was:
One possible deployment in production is to use something like a lvs in front of all the region servers to act as a LB, so client just need to connect to the lvs IP instead of go to the region server directly to get registry information.

For this scenario we do not need to refresh the endpoints any more.


> Allow disabling refresh of connection registry endpoint
> -------------------------------------------------------
>
>                 Key: HBASE-26182
>                 URL: https://issues.apache.org/jira/browse/HBASE-26182
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Duo Zhang
>            Priority: Major
>
> One possible deployment in production is to use something like a lvs in front of all the region servers to act as a LB, so client just need to connect to the lvs IP instead of go to the region server directly to get registry information.
> For this scenario we do not need to refresh the endpoints any more.
> The simplest way is to set the refresh interval to -1.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)