hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13479) [branch-1.0] Master should not bind to region server ports
Date Thu, 16 Apr 2015 04:48:59 GMT

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

stack commented on HBASE-13479:


I tried it.

I added these configs:

diff --git a/conf/hbase-env.sh b/conf/hbase-env.sh
index 2bbde1a..87745d7 100644
--- a/conf/hbase-env.sh
+++ b/conf/hbase-env.sh
@@ -124,6 +124,7 @@ export HBASE_OPTS="-XX:+UseConcMarkSweepGC"

 # Tell HBase whether it should manage it's own instance of Zookeeper or not.
 # export HBASE_MANAGES_ZK=true
+export HBASE_MANAGES_ZK=false

 # The default log rolling policy is RFA, where the log file is rolled as per the size defined
for the
 # RFA appender. Please refer to the log4j.properties file to see more details on this appender.
diff --git a/conf/hbase-site.xml b/conf/hbase-site.xml
index c516ac7..c88ad7e 100644
--- a/conf/hbase-site.xml
+++ b/conf/hbase-site.xml
@@ -21,4 +21,20 @@
+  <property >
+    <name>hbase.cluster.distributed</name>
+    <value>true</value>
+    <description>The mode the cluster will be in. Possible values are
+      false for standalone mode and true for distributed mode.  If
+      false, startup will run all HBase and ZooKeeper daemons together
+      in the one JVM.</description>
+  </property>
+  <property >
+    <name>hbase.master.port</name>
+    <value>16010</value>
+  </property>
+  <property >
+    <name>hbase.master.info.port</name>
+    <value>16011</value>
+  </property>

I started zk, then master.  I could not start regionserver because ports were occupied (the
hbase.master.port configs were ignored in hbase-site.xml).

I applied the patch and I was able to start master and then regionserver successfully.

I think it a good call sinking the RC to get this one in. Its still bad but at least there
is an out now. Thanks [~enis]

> [branch-1.0] Master should not bind to region server ports
> ----------------------------------------------------------
>                 Key: HBASE-13479
>                 URL: https://issues.apache.org/jira/browse/HBASE-13479
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>            Priority: Blocker
>             Fix For: 1.0.1
>         Attachments: hbase-13479_v1.patch
> In parent jira, we have brought back old config value {{hbase.master.port}} and made
it so that if it is configured (which is by default), master does not bind to the region servers's
RPC and info ports now. We have realized that master binding to RS ports turns out to be a
pain point and unnecessary frustration for users (although we were expecting the opposite).

> Let's use this jira to see what we can do in 1.0.x series. In 1.0.0, master binds to
> {{hbase.regionserver.port}}
> {{hbase.master.info.port}}
> {{hbase.regionserver.info.port}}
> In 1.0.x, we have a couple of options I think:
> (a) don't do anything. 
> (b) Commit patch from master as it is. All upgrades from 1.0.0 will observe changed ports.

> (c) Commit the patch, disabled by default. If user has {{hbase.master.port}} set, bind
to the port. Only users who set the conf value will observe changed ports. 
> (d) Commit the patch with an extra config option {{hbase.master.compat.mode}}. The users
have to explicitly enable this in 1.0. 

This message was sent by Atlassian JIRA

View raw message