[
https://issues.apache.org/jira/browse/HBASE-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-11066.
------------------------------------
Resolution: Invalid
HBaseConfiguration loads hbase-site.xml from the expected location already.
This issue seems to describe a local configuration problem not a bug. Please
mail u...@hbase.apache.org for assistane.
> HBase client could not add resource from hbase-site.xml
> -------------------------------------------------------
>
> Key: HBASE-11066
> URL: https://issues.apache.org/jira/browse/HBASE-11066
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.1
> Environment: Suse linux 11 64-bit and jdk1.7.0_05
> Reporter: ZhangYong
>
> Configuration conf = HBaseConfiguration.create();
> conf.addResource("hbase-site.xml");
> this code could not work find, all configuration in hbase-site.xml could not
> be loaded, and log will show as below:
> 14/04/24 12:06:13 INFO zookeeper.ZooKeeper: Initiating client connection,
> connectString=localhost:2181 sessionTimeout=90000
> watcher=hconnection-0x26f997aa, quorum=localhost:2181, baseZNode=/hbase
> 14/04/24 12:06:13 INFO zookeeper.RecoverableZooKeeper: Process
> identifier=hconnection-0x26f997aa connecting to ZooKeeper
> ensemble=localhost:2181
> 14/04/24 12:06:13 INFO zookeeper.ClientCnxn: Opening socket connection to
> server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL
> (unknown error)
> 14/04/24 12:06:13 INFO zookeeper.ClientCnxn: Socket connection established to
> localhost/127.0.0.1:2181, initiating session
> 14/04/24 12:06:13 INFO zookeeper.ClientCnxn: Session establishment complete
> on server localhost/127.0.0.1:2181, sessionid = 0x14572d37f6a00c1, negotiated
> timeout = 40000
> 14/04/24 12:06:13 INFO client.ZooKeeperRegistry: ClusterId read in ZooKeeper
> is null
> but if I set properties like this:
> conf.set("hbase.zookeeper.quorum", "mater");
> conf.set("hbase.zookeeper.property.clientPort", "8181");
> conf.set("hbase.master.port", "60000");
> it will work fine.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
