新的HBase安装速度非常慢

新的HBase安装速度非常慢,hbase,apache-zookeeper,Hbase,Apache Zookeeper,我刚刚在iMac上安装了HBase 0.94.2,运行Sun Java 7和Mac OS 10.8.2 我确实有一个开发Hadoop实例,但是目前我正在独立模式下运行HBase 不幸的是,许多基本操作的执行时间超过30秒: magoo:bin mattpainter$ ./hbase shell HBase Shell; enter 'help<RETURN>' for list of supported commands. Type "exit<RETURN>" to

我刚刚在iMac上安装了HBase 0.94.2,运行Sun Java 7和Mac OS 10.8.2

我确实有一个开发Hadoop实例,但是目前我正在独立模式下运行HBase

不幸的是,许多基本操作的执行时间超过30秒:

magoo:bin mattpainter$ ./hbase shell
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 0.94.2, r1395367, Sun Oct  7 19:11:01 UTC 2012

hbase(main):002:0> list 'table'
TABLE                                                                                                                                                                       
2012-10-20 08:26:38.903 java[41217:1703] Unable to load realm info from SCDynamicStore
0 row(s) in 33.6460 seconds

hbase(main):003:0> 
有什么问题会导致零配置的开箱即用安装(除了在
hbase env.sh
中设置
JAVA_HOME
)出现这种行为

非常感谢,,
Matt

看起来您的JVM默认使用IPv6流量。尝试将-Djava.net.preferIPv4Stack=true添加到您的HBASE_OPTS envvar(仅在HBASE env.sh中JAVA_HOME下方几行),然后重新启动HBASE

还有其他强制IPv4的方法(编辑sysctl.conf)

是的,确实是罪魁祸首


我从JDK1.7.0_04升级到JDK1.7.0_09,相应地修改了我的
base env.sh
,现在一切都可以快速工作。

Hrm。答:谢谢-这似乎并没有解决这个问题,但我的JDK升级了几个等级。好奇。
12/10/20 08:24:58 INFO zookeeper.ClientCnxn: Client session timed out, have not heard from server in 26667ms for sessionid 0x13a7a7744270005, closing socket connection and attempting reconnect
12/10/20 08:24:58 WARN zookeeper.RecoverableZooKeeper: Possibly transient ZooKeeper exception: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/master
12/10/20 08:24:58 INFO util.RetryCounter: Sleeping 2000ms before retry #1...
12/10/20 08:24:59 INFO zookeeper.ClientCnxn: Opening socket connection to server /fe80:0:0:0:0:0:0:1%1:2181
12/10/20 08:25:04 INFO client.ZooKeeperSaslClient: Client will not SASL-authenticate because the default JAAS configuration section 'Client' could not be found. If you are not using SASL, you may ignore this. On the other hand, if you expected SASL to work, please fix your JAAS configuration.
12/10/20 08:25:04 INFO zookeeper.ClientCnxn: Socket connection established to fe80:0:0:0:0:0:0:1%1/fe80:0:0:0:0:0:0:1%1:2181, initiating session
12/10/20 08:25:04 INFO zookeeper.ClientCnxn: Session establishment complete on server fe80:0:0:0:0:0:0:1%1/fe80:0:0:0:0:0:0:1%1:2181, sessionid = 0x13a7a7744270005, negotiated timeout = 40000