简体   繁体   English

HBase .META。 表-readRequestsCount太高

[英]HBase .META. table - readRequestsCount too high

My HBase RegionServers are well balanced except the readRequestsCount to the .META. 除了对.META的readRequestsCount之外,我的HBase RegionServers都平衡良好。 table. 表。

Looking at the log files of my MapReduce jobs I found that there are many calls to ZooKeeper which established and closed immediately: 查看我的MapReduce作业的日志文件,我发现有很多对ZooKeeper的调用,它们立即建立并关闭:

2:04,958 INFO org.apache.zookeeper.ZooKeeper: Initiating client connection, connectString=nam-1:2181,nam-2:2181,dat-4:2181 sessionTimeout=180000 watcher=catalogtracker-on-org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@76477647 2014-02-04 20:32:04,958 INFO org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: The identifier of this process is 16972@dat-2 2014-02-04 20:32:04,958 INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server /1.10.230.132:2181 2014-02-04 20:32:04,958 WARN org.apache.zookeeper.client.ZooKeeperSaslClient: SecurityException: java.lang.SecurityException: Unable to locate a login configuration occurred when trying to find JAAS configuration. 2:04,958 INFO org.apache.zookeeper.ZooKeeper:启动客户端连接,connectString = nam-1:2181,nam-2:2181,dat-4:2181 sessionTimeout = 180000 watcher = catalogtracker-on-org.apache.hadoop。 hbase.client.HConnectionManager$HConnectionImplementation@76477647 2014-02-04 20:32:04,958 INFO org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper:此过程的标识符为16972 @ dat-2 2014-02-04 20: 32:04,958 INFO org.apache.zookeeper.ClientCnxn:打开与服务器/1.10.230.132:2181 2014-02-04 20:32:04,958 WARN org.apache.zookeeper.client.ZooKeeperSaslClient的套接字连接:SecurityException:java.lang。 SecurityException:尝试查找JAAS配置时无法找到登录配置。 2014-02-04 20:32:04,958 INFO org.apache.zookeeper.client.ZooKeeperSaslClient: Client will not SASL-authenticate because the default JAAS configuration section 'Client' could not be found. 2014-02-04 20:32:04,958信息org.apache.zookeeper.client.ZooKeeperSaslClient:客户端将不会进行SASL身份验证,因为找不到默认的JAAS配置节“客户端”。 If you are not using SASL, you may ignore this. 如果您不使用SASL,则可以忽略它。 On the other hand, if you expected SASL to work, please fix your JAAS configuration. 另一方面,如果您希望SASL可以运行,请修复您的JAAS配置。 2014-02-04 20:32:04,958 INFO org.apache.zookeeper.ClientCnxn: Socket connection established to nam-1:2181, initiating session 2014-02-04 20:32:04,960 INFO org.apache.zookeeper.ClientCnxn: Session establishment complete on server nam-1:2181, sessionid = 0x243fd975d060d09, negotiated timeout = 60000 2014-02-04 20:32:05,430 INFO org.apache.zookeeper.ZooKeeper: Session: 0x243fd975d060d09 closed 2014-02-04 20:32:04,958 INFO org.apache.zookeeper.ClientCnxn:建立与nam-1:2181的套接字连接,启动会话2014-02-04 20:32:04,960 INFO org.apache.zookeeper.ClientCnxn:服务器nam-1:2181上的会话建立完成,sessionid = 0x243fd975d060d09,协商的超时= 60000 2014-02-04 20:32:05,430 INFO org.apache.zookeeper.ZooKeeper:会话:0x243fd975d060d09关闭

I cant find any reason for that. 我找不到任何原因。 Anyone can help? 有人可以帮忙吗?

Can you try setting hbase.zookeeper.property.maxClientCnxns in hbase-site.xml. 您可以尝试在hbase-site.xml中设置hbase.zookeeper.property.maxClientCnxns吗? I set this to 150 it works for me. 我将此设置为150它对我有用。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM