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

Enis Soztutar commented on HBASE-13453:
---------------------------------------

bq. Hopefully we will get back some of the master configuration properties 
which seem to be lost because master-is-the-rs change
Agreed. At least the ports are coming back in this patch. We can do the bind 
address and DNS in this or a follow up. 
bq. Had an internal chat with Esteban. Attached a patch, which uses reflection. 
This will preserver pre-1.0 behavior.
This should work. I think that patch only binds to one info port for master 
instead of redirection. However, I would still like to see hbase-default to 
contain {{hbase.master.port}} property. 

> Master should not bind to region server ports
> ---------------------------------------------
>
>                 Key: HBASE-13453
>                 URL: https://issues.apache.org/jira/browse/HBASE-13453
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>            Assignee: Devaraj Das
>            Priority: Critical
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: 34111-2.txt, HBASE-13453.patch
>
>
> In 1.0, master by default binds to the region server ports (rpc and info). We 
> have done it so thinking that in the long term, master and meta co-location 
> will be default, and we can merge the master and region server as a single 
> daemon. 
> Over at HBASE-11165, if the conclusion end up being that meta will not be 
> colocated at all, then master hosting a region server will just become an 
> implementation detail. [~saint....@gmail.com] says that we might never allow 
> master to host regions. 
> Now, we are stuck in a state where we have made master bind to RS ports in 
> 1.0, which might create some confusion (and frustration) for small cluster 
> users who traditionally used to host a master and a region server on the same 
> node.
> I think we should undo this in 1.1 and use the previous master ports (16000) 
> and not bind to 16030, so that the user does not need to do anything to bring 
> up a RS on the same host. At least users going from 0.98 -> 1.1 will not take 
> a hit. Users going from 1.0 -> 1.1 will see changed default ports. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to