[
https://issues.apache.org/jira/browse/HBASE-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wuchengzhi updated HBASE-18868:
-------------------------------
Attachment: jmx-iffy.json
the jmx show so little info as the attachment
> metrics error and the jmx loss many metrics like
> 'Hadoop:service=HBase,name=RegionServer,sub=IPC'
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-18868
> URL: https://issues.apache.org/jira/browse/HBASE-18868
> Project: HBase
> Issue Type: Bug
> Components: metrics
> Affects Versions: 1.2.1, 1.2.4, 1.2.6
> Environment: 2*6 cores process,E5-2620v3 , 128G memory , 1*600G
> SAS，12*6T SATA
> Linux version 2.6.32-504.el6.x86_64 (mockbu...@c6b9.bsys.dev.centos.org) (gcc
> version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Wed Oct 15 04:27:16
> UTC 2014
> Reporter: wuchengzhi
> Priority: Critical
> Labels: jmx, metrics
> Attachments: jmx-iffy.json
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> so many metrics error log printed in the regionserver log all the time, then
> the web-gui http://hbase-master1:16010/jmx loss some metrics like
> 'Hadoop:service=HBase,name=RegionServer,sub=Regions' ,
> 'Hadoop:service=HBase,name=RegionServer,sub=IPC' .......
> is there something wrong i configured at my hbase-site.xml or hbase-env.sh?
> ver.thread.wakefrequency</name>
> <value>1000</value>
> </property>
> <property>
> <name>hbase.rpc.timeout</name>
> <value>54000000</value>
> </property>
> <property>
> <name>hbase.hstore.blockingStoreFiles</name>
> <value>500</value>
> </property>
> <property>
> <name>hbase.client.scanner.timeout.period</name>
> <value>600000</value>
> </property>
> <property>
> <name>zookeeper.session.timeout</name>
> <value>180000</value>
> </property>
> <property>
> <name>hbase.regionserver.optionallogflushinterval</name>
> <value>5000</value>
> </property>
> <property>
> <name>hbase.client.write.buffer</name>
> <value>5242880</value>
> </property>
> <property>
> <name>hbase.hstore.compactionThreshold</name>
> <value>5</value>
> </property>
> <property>
> <name>hbase.hstore.compaction.max</name>
> <value>12</value>
> </property>
> <!-- disable to auto split -->
> <property>
> <name>hbase.regionserver.regionSplitLimit</name>
> <value>1</value>
> </property>
> <property>
> <name>hbase.regionserver.thread.compaction.large</name>
> <value>3</value>
> </property>
> <property>
> <name>hbase.regionserver.thread.compaction.small </name>
> <value>8</value>
> </property>
> <property>
> <name>hbase.master.logcleaner.ttl</name>
> <value>3600000</value>
> </property>
> <property>
> <name>hbase.bucketcache.ioengine</name>
> <value>offheap></value>
> </property>
> <property>
> <name>hbase.bucketcache.percentage.in.combinedcache</name>
> <value>0.9</value>
> </property>
> <property>
> <name>hbase.bucketcache.size</name>
> <value>26214</value>
> </property>
> <property>
> <name>hbase.master.maxclockskew</name>
> <value>150000</value>
> </property>
> <!-- hbase1 -->
> <property>
> <name>hbase.regionserver.port</name>
> <value>16021</value>
> </property>
> <property>
> <name>hbase.regionserver.info.port</name>
> <value>16011</value>
> </property>
> <!-- end of hbase1 -->
> <!-- start of replication -->
> <property>
> <name>hbase.replication</name>
> <value>true</value>
> </property>
> <property>
> <name>replication.source.nb.capacity</name>
> <value>6000</value>
> </property>
> <property>
> <name>replication.source.size.capacity</name>
> <value>67108864</value>
> </property>
> <property>
> <name>replication.source.ratio</name>
> <value>1</value>
> </property>
> <property>
> <name>hbase.regionserver.wal.enablecompression</name>
> <value>false</value>
> </property>
> <property>
> <name> replication.sleep.before.failover</name>
> <value>5000</value>
> </property>
> <property>
> <name>replication.executor.workers</name>
> <value>5</value>
> </property>
> <!-- end of replication -->
> </configuration>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
