[jira] [Created] (HBASE-7153) print gc option in hbase-env.sh affects hbase zkcli

[wonderyl (JIRA)]

wonderyl created HBASE-7153:
---

 Summary: print gc option in hbase-env.sh affects hbase zkcli
 Key: HBASE-7153
 URL: https://issues.apache.org/jira/browse/HBASE-7153
 Project: HBase
  Issue Type: Bug
  Components: scripts
Affects Versions: 0.94.0
Reporter: wonderyl


I un-commented the -verbose:gc option in hbase-env.sh, which print out the gc 
info.
but when I use hbase zkcli to check zk, it can not connect to the server.
the problem is zkcli uses hbase 
org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg to get the server_arg 
in the script hbase. when gc verbose option is open, the output of 
ZooKeeperMainServerArg is with gc info, which masses up with server_arg. and 
this is the reason stop zkcli working.
I think the easiest way to fix this is to trim the gc info out of server_arg in 
the hbase script.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HBASE-7044) verifyRegionLocation in CatalogTracker.java didn't check if regionserver is in the cluster

[wonderyl (JIRA)]

wonderyl created HBASE-7044:
---

 Summary: verifyRegionLocation in CatalogTracker.java didn't check 
if  regionserver is in the cluster
 Key: HBASE-7044
 URL: https://issues.apache.org/jira/browse/HBASE-7044
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.94.0
Reporter: wonderyl


at the beginning there is 1 whole hbase cluster, then I decide to split is into 
2 cluster, one is for offline mining, one is for online service, and the online 
one is striped, the offline one contains the original master.
unfortunately, the META of the original cluster is assigned to the machine 
stripped, and as there is a cache policy for META, the offline cluster is still 
access the META of the stripped one.
after inspected the code, I found that in verifyRegionLocation of 
CatalogTracker.java, although it checks if the region server still contains the 
region, but it didn't check if the regions erver is still in the cluster which 
is very easy, just inspect if it is registered int zk.
all in all, I have to shutdown the online cluster and restart the offline one, 
then the META is re-assgined. then everything is back to normal.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira