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

Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2021/08/10 20:54:00 UTC

[jira] [Updated] (HBASE-26180) Introduce a initial refresh interval for RpcConnectionRegistry

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

Michael Stack updated HBASE-26180:
----------------------------------
    Description: 
So we can get the new list soon once we connect to the cluster.

As end users could configure any nodes in a cluster as the initial bootstrap nodes, it is possible that different end users will configure the same machine which makes the machine over load. So we should have a shorter delay for the initial refresh, to let users quickly switch to the bootstrap nodes we want them to connect to.

  was:So we can get the new list soon once we connect to the cluster.


> Introduce a initial refresh interval for RpcConnectionRegistry
> --------------------------------------------------------------
>
>                 Key: HBASE-26180
>                 URL: https://issues.apache.org/jira/browse/HBASE-26180
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Duo Zhang
>            Priority: Major
>
> So we can get the new list soon once we connect to the cluster.
> As end users could configure any nodes in a cluster as the initial bootstrap nodes, it is possible that different end users will configure the same machine which makes the machine over load. So we should have a shorter delay for the initial refresh, to let users quickly switch to the bootstrap nodes we want them to connect to.



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