[jira] [Commented] (HBASE-9892) Add info port to ServerName to support multi instances in a node

["Enis Soztutar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836989#comment-13836989 ] 

Enis Soztutar commented on HBASE-9892:
--------------------------------------

bq. info port is an attribute that does not vary while server is up and running. It does not belong in the cluster status set. Can you not get it from zk Steve Loughran? Or failing that, you want us to write you a script that will read it out of zk for you – this and stuff like current master?
We still need to make the info ports and maybe other static attributes for the cluster to the clients as an API I think. It belongs together with liveServers data, since for each live server, the client may need the info port. 

> Add info port to ServerName to support multi instances in a node
> ----------------------------------------------------------------
>
>                 Key: HBASE-9892
>                 URL: https://issues.apache.org/jira/browse/HBASE-9892
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Minor
>         Attachments: HBASE-9892-0.94-v1.diff, HBASE-9892-0.94-v2.diff, HBASE-9892-0.94-v3.diff, HBASE-9892-0.94-v4.diff
>
>
> The full GC time of  regionserver with big heap(> 30G ) usually  can not be controlled in 30s. At the same time, the servers with 64G memory are normal. So we try to deploy multi rs instances(2-3 ) in a single node and the heap of each rs is about 20G ~ 24G.
> Most of the things works fine, except the hbase web ui. The master get the RS info port from conf, which is suitable for this situation of multi rs  instances in a node. So we add info port to ServerName.
> a. at the startup, rs report it's info port to Hmaster.
> b, For root region, rs write the servername with info port ro the zookeeper root-region-server node.
> c, For meta regions, rs write the servername with info port to root region 
> d. For user regions,  rs write the servername with info port to meta regions 
> So hmaster and client can get info port from the servername.
> To test this feature, I change the rs num from 1 to 3 in standalone mode, so we can test it in standalone mode,
> I think Hoya(hbase on yarn) will encounter the same problem.  Anyone knows how Hoya handle this problem?
> PS: There are  different formats for servername in zk node and meta table, i think we need to unify it and refactor the code.



--
This message was sent by Atlassian JIRA
(v6.1#6144)