You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2014/11/01 01:03:34 UTC
[jira] [Commented] (HBASE-12399) Master startup race between
metrics and RpcServer
[ https://issues.apache.org/jira/browse/HBASE-12399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192787#comment-14192787 ]
Enis Soztutar commented on HBASE-12399:
---------------------------------------
+1.
> Master startup race between metrics and RpcServer
> -------------------------------------------------
>
> Key: HBASE-12399
> URL: https://issues.apache.org/jira/browse/HBASE-12399
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: Nick Dimiduk
> Priority: Minor
> Fix For: 2.0.0, 0.98.8, 0.99.2
>
> Attachments: 12399.patch
>
>
> Seeing this on CM tests with frequent master thrashing
> {noformat}
> 2014-10-31 12:01:59,196 ERROR [Timer for 'HBase' metrics system] impl.MetricsSourceAdapter: Error getting metrics from source IPC,sub=IPC
> java.lang.NullPointerException
> at org.apache.hadoop.hbase.ipc.FifoRpcScheduler.getGeneralQueueLength(FifoRpcScheduler.java:81)
> at org.apache.hadoop.hbase.ipc.MetricsHBaseServerWrapperImpl.getGeneralQueueLength(MetricsHBaseServerWrapperImpl.java:43)
> at org.apache.hadoop.hbase.ipc.MetricsHBaseServerSourceImpl.getMetrics(MetricsHBaseServerSourceImpl.java:117)
> at org.apache.hadoop.metrics2.impl.MetricsSourceAdapter.getMetrics(MetricsSourceAdapter.java:195)
> at org.apache.hadoop.metrics2.impl.MetricsSystemImpl.snapshotMetrics(MetricsSystemImpl.java:419)
> at org.apache.hadoop.metrics2.impl.MetricsSystemImpl.sampleMetrics(MetricsSystemImpl.java:406)
> at org.apache.hadoop.metrics2.impl.MetricsSystemImpl.onTimerEvent(MetricsSystemImpl.java:382)
> at org.apache.hadoop.metrics2.impl.MetricsSystemImpl$4.run(MetricsSystemImpl.java:369)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)