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

Dev Lakhani commented on HBASE-13449:
-------------------------------------

Fine, but how to I set region server specific properties for JMX/JVM for 
example? As mentioned in my comment, the convention has been to set 
HBASE_REGIONSERVER_OPTS in hbase-env.sh and similarly for related hadoop 
properties to be in hadoop-env.sh. 

We then need another env variable to append to HBASE_REGIONSERVER_ARGS to 
ensure that the local region server has it's own set of runtime args. 

> HBASE_REGIONSERVER_OPTS in local-regionservers.sh is masked and silently 
> reset.
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-13449
>                 URL: https://issues.apache.org/jira/browse/HBASE-13449
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Dev Lakhani
>
> In local-regionserver.sh there is a line which masks the current 
> HBASE_REGIONSERVER_OPTS
> https://github.com/apache/hbase/blob/master/bin/local-regionservers.sh#L38
> # sanity check: make sure your regionserver opts don't use ports [i.e. 
> JMX/DBG]
> export HBASE_REGIONSERVER_OPTS=" "
> We are having trouble with this because:
> 1) As per normal Hadoop convention env variables should be in hbase-env.sh, 
> as with other daemons this is where we set jmx/jvm properties.
> 2) Whatever we set in hbase-env.sh gets masked by this line.
> Is there any reason this line is included in the runner and can it be moved 
> to the env.sh file?



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

Reply via email to