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

Umesh Agashe commented on HBASE-20130:
--------------------------------------

Ref guide documents the port number changes here: 
[https://hbase.apache.org/book.html#_changes_of_note.]

The documented default ports are 160XX (e.g. 16010, 16020, 16030).

To find an answer to question "why ports 16201, 16301 are used when region 
server binds to localhost?", the only references to these ports in hbase code 
can be found in following two files:
{code:java}
bin/local-regionservers.sh
bin/regionservers.sh{code}
I have left the comment on Jira HBASE-15924 to know reasons why those ports are 
used and not the default once (16020, 16030). From the code/ patch reasons are 
not clear. After going through the history of commits for those files, the 
original intent was: to be able to spawn 100 instances in pseudo distributed 
mode. For this, port numbers should not overlap.

I think leaving the hard coded non-default ports as is, will make it necessary 
to document this exception and may cause more confusion. We need to use default 
ports which allows up to 10 instances of region servers and if somebody wants 
to have more, it can be done by changing the ports as needed in these files. 
This can be documented in ref guide.

[~chia7712], [~stack]: let me know your thoughts. I will upload the patch with 
suggested changes as above.

> Document the ports used by RS are changed to 16201/16301 when the RS is bound 
> to localhost
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20130
>                 URL: https://issues.apache.org/jira/browse/HBASE-20130
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Chia-Ping Tsai
>            Assignee: Umesh Agashe
>            Priority: Minor
>             Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to