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

stack updated HBASE-4457:
-------------------------

    Priority: Major  (was: Critical)

Marking this down to major since it looks like we do read from the 
configuration in current trunk and branch:

{code}
...
200 <table>
201 <tr><th rowspan="<% servers.size() + 
1%>"></th><th>ServerName</th><th>Load</th></tr>
202 <%java>
203    ServerName [] serverNames = servers.toArray(new 
ServerName[servers.size()]);
204      Arrays.sort(serverNames);
205      for (ServerName serverName: serverNames) {
206        // TODO: this is incorrect since this conf might differ from RS to RS
207        // or be set to 0 to get ephemeral ports
208        int infoPort = 
master.getConfiguration().getInt("hbase.regionserver.info.port", 60030);
209        String url = "http://"; + serverName.getHostname() + ":" + infoPort + 
"/";
210        HServerLoad hsl = master.getServerManager().getLoad(serverName);
211        String loadStr = hsl == null? "-": hsl.toString();
212        if (hsl != null) {
213          totalRegions += hsl.getNumberOfRegions();
214          totalRequests += hsl.getNumberOfRequests();
215        }
216 </%java>
{code}
                
> Starting region server on non-default info port is resulting in broken URL's 
> in master UI
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-4457
>                 URL: https://issues.apache.org/jira/browse/HBASE-4457
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.92.0
>            Reporter: Praveen Patibandla
>              Labels: newbie
>             Fix For: 0.92.0
>
>         Attachments: 4457-V1.patch, 4457.patch
>
>
> When  "hbase.regionserver.info.port" is set to non-default port, Master UI 
> has broken URL's in the region server table because it's hard coded to 
> default port.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to