[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14707668#comment-14707668 ] Nick Dimiduk commented on HBASE-14166: -- looks like this was committed to branch-1 so added fixVersion 1.3. Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0, 1.3.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705604#comment-14705604 ] Andrew Purtell commented on HBASE-14166: Might be a deadlock associated with this: HBASE-14274 Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704057#comment-14704057 ] Nick Dimiduk commented on HBASE-14166: -- Yeah, looks like we should have it back. This cache-buster stuff is nasty business. I'm not so deep into it yet -- is this a JMX cache bug or a hadoop metrics2 sink bug, or something else? Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14701965#comment-14701965 ] Andrew Purtell commented on HBASE-14166: It's wanted back to 0.98 looks like. If you don't mind backporting, that's great. Otherwise ping me and I'll gladly do it. Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700496#comment-14700496 ] Hudson commented on HBASE-14166: FAILURE: Integrated in HBase-TRUNK #6732 (See [https://builds.apache.org/job/HBase-TRUNK/6732/]) HBASE-14166 Per-Region metrics can be stale (eclark: rev ad2c7c6336d157d2372eebbf73c3dc0977939b8a) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperStub.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DynamicMetricsRegistry.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSource.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionSourceImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/MetricsExecutorImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java * hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/regionserver/TestMetricsRegionSourceImpl.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/impl/JmxCacheBuster.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapper.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegion.java Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700559#comment-14700559 ] Elliott Clark commented on HBASE-14166: --- Yes this could be applied to other branches. I only did non-released branches as it was larger change that didn't affect dat correctness or reliability. If it's wanted I can back port it. Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700692#comment-14700692 ] Hudson commented on HBASE-14166: FAILURE: Integrated in HBase-1.2 #114 (See [https://builds.apache.org/job/HBase-1.2/114/]) HBASE-14166 Per-Region metrics can be stale -- ADDENDUM (eclark: rev 13d7250ec9996b5f6e76931177a3f3e825eb754f) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700472#comment-14700472 ] Enis Soztutar commented on HBASE-14166: --- bq. This looks like a bug that should be picked back to other active release branches. However this is an interesting change that adds a background task for cleaning the JMX cache and locks for said cleaning. I plan to pick it back in a couple of days but won't if there are concerns or objections. Agreed. [~eclark] is this applicable to earlier versions? Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700557#comment-14700557 ] Hudson commented on HBASE-14166: FAILURE: Integrated in HBase-1.3 #112 (See [https://builds.apache.org/job/HBase-1.3/112/]) HBASE-14166 Per-Region metrics can be stale (eclark: rev d6c2beb4bff557976c4d6f7cb122b4e69705ff79) * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSource.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/impl/JmxCacheBuster.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/MetricsExecutorImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DynamicMetricsRegistry.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperStub.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapper.java * hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/regionserver/TestMetricsRegionSourceImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegion.java HBASE-14166 Per-Region metrics can be stale -- ADDENDUM (eclark: rev 81f3afa5da4652830f5f42696ed289268c4f42c9) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700558#comment-14700558 ] Hudson commented on HBASE-14166: SUCCESS: Integrated in HBase-1.3-IT #94 (See [https://builds.apache.org/job/HBase-1.3-IT/94/]) HBASE-14166 Per-Region metrics can be stale (eclark: rev d6c2beb4bff557976c4d6f7cb122b4e69705ff79) * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapper.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperStub.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSource.java * hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/regionserver/TestMetricsRegionSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/impl/JmxCacheBuster.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DynamicMetricsRegistry.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/MetricsExecutorImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java HBASE-14166 Per-Region metrics can be stale -- ADDENDUM (eclark: rev 81f3afa5da4652830f5f42696ed289268c4f42c9) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700552#comment-14700552 ] Hudson commented on HBASE-14166: SUCCESS: Integrated in HBase-1.2-IT #94 (See [https://builds.apache.org/job/HBase-1.2-IT/94/]) HBASE-14166 Per-Region metrics can be stale (eclark: rev fb91012b096a217e844200e24bed92b8ba867b1a) * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/impl/JmxCacheBuster.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapper.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/MetricsExecutorImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionSourceImpl.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java * hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/regionserver/TestMetricsRegionSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperStub.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DynamicMetricsRegistry.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSource.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegion.java HBASE-14166 Per-Region metrics can be stale -- ADDENDUM (eclark: rev 13d7250ec9996b5f6e76931177a3f3e825eb754f) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700106#comment-14700106 ] Hudson commented on HBASE-14166: FAILURE: Integrated in HBase-1.2 #113 (See [https://builds.apache.org/job/HBase-1.2/113/]) HBASE-14166 Per-Region metrics can be stale (eclark: rev fb91012b096a217e844200e24bed92b8ba867b1a) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegion.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionSourceImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/impl/JmxCacheBuster.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSource.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperStub.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionAggregateSourceImpl.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapper.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/MetricsExecutorImpl.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DynamicMetricsRegistry.java * hbase-hadoop2-compat/src/test/java/org/apache/hadoop/hbase/regionserver/TestMetricsRegionSourceImpl.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRemoveRegionMetrics.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MetricsRegionWrapperImpl.java Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.2.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697880#comment-14697880 ] Elliott Clark commented on HBASE-14166: --- k, I'll check this in later today unless there are any other comments. Thanks Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695540#comment-14695540 ] Elliott Clark commented on HBASE-14166: --- Any further thoughts on this one? I'm not 100% sure this will fix everything but it sure seems to make them better. Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[
https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693906#comment-14693906
]
Hadoop QA commented on HBASE-14166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750111/HBASE-14166-v5.patch
against master branch at commit 72a48a1333f6c01c46cd244439198ccce3f941ac.
ATTACHMENT ID: 12750111
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 11 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15069//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15069//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15069//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15069//console
This message is automatically generated.
Per-Region metrics can be stale
---
Key: HBASE-14166
URL: https://issues.apache.org/jira/browse/HBASE-14166
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch,
HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166-v5.patch,
HBASE-14166.patch
We're seeing some machines that are reporting only old region metrics. It
seems like at some point the Hadoop metrics system decided which metrics to
display and which not to. From then on it was not changing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[
https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682163#comment-14682163
]
Hadoop QA commented on HBASE-14166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749848/HBASE-14166-v3.patch
against master branch at commit 7d4de20cafd6b765bd5f33df72fc0e630d1731f7.
ATTACHMENT ID: 12749848
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 11 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at org.apache.oozie.test.MiniHCatServer$1.run(MiniHCatServer.java:137)
at
org.apache.oozie.test.XTestCase$MiniClusterShutdownMonitor.run(XTestCase.java:1071)
at org.apache.oozie.test.XTestCase.waitFor(XTestCase.java:692)
at
org.apache.oozie.TestCoordinatorEngineStreamLog.testCoordLogStreaming(TestCoordinatorEngineStreamLog.java:105)
at
org.apache.hadoop.hbase.replication.regionserver.TestReplicationWALReaderManager.test(TestReplicationWALReaderManager.java:181)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15044//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15044//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15044//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15044//console
This message is automatically generated.
Per-Region metrics can be stale
---
Key: HBASE-14166
URL: https://issues.apache.org/jira/browse/HBASE-14166
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch,
HBASE-14166-v3.patch, HBASE-14166.patch
We're seeing some machines that are reporting only old region metrics. It
seems like at some point the Hadoop metrics system decided which metrics to
display and which not to. From then on it was not changing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682272#comment-14682272 ] stack commented on HBASE-14166: --- Is the test failure yours? Skimmed patch. Looks good. Looks like you tried it going by nature of the changes. +1 Release note the clear thread interval at least: }, 5, 5, TimeUnit.MINUTES); Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14682304#comment-14682304 ] Elliott Clark commented on HBASE-14166: --- Hmmm I don't think the test failure is related. Let me re-try. Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[ https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692565#comment-14692565 ] Elliott Clark commented on HBASE-14166: --- Hmmm let me look a little closer. Per-Region metrics can be stale --- Key: HBASE-14166 URL: https://issues.apache.org/jira/browse/HBASE-14166 Project: HBase Issue Type: Bug Affects Versions: 1.1.0.1 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch, HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166.patch We're seeing some machines that are reporting only old region metrics. It seems like at some point the Hadoop metrics system decided which metrics to display and which not to. From then on it was not changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[
https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14692555#comment-14692555
]
Hadoop QA commented on HBASE-14166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749917/HBASE-14166-v4.patch
against master branch at commit 38b94709ee3727832cb58446b4fa60cf5c37b9a6.
ATTACHMENT ID: 12749917
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 11 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesUseSecurityEndPoint
org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15054//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15054//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15054//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15054//console
This message is automatically generated.
Per-Region metrics can be stale
---
Key: HBASE-14166
URL: https://issues.apache.org/jira/browse/HBASE-14166
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch,
HBASE-14166-v3.patch, HBASE-14166-v4.patch, HBASE-14166.patch
We're seeing some machines that are reporting only old region metrics. It
seems like at some point the Hadoop metrics system decided which metrics to
display and which not to. From then on it was not changing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[
https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680908#comment-14680908
]
Hadoop QA commented on HBASE-14166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749683/HBASE-14166-v2.patch
against master branch at commit ae35f65e9ac12256b4514e6ba6ef5333e9e90870.
ATTACHMENT ID: 12749683
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 11 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1863 checkstyle errors (more than the master's current 1862 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS
{color:red}-1 core zombie tests{color}. There are 10 zombie test(s):
at
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat2.testMRIncrementalLoadWithSplit(TestHFileOutputFormat2.java:385)
at
org.apache.hadoop.hbase.mapreduce.TestTimeRangeMapRed.testTimeRangeMapRed(TestTimeRangeMapRed.java:163)
at
org.apache.hadoop.hbase.mapreduce.MultiTableInputFormatTestBase.testScan(MultiTableInputFormatTestBase.java:255)
at
org.apache.hadoop.hbase.mapreduce.MultiTableInputFormatTestBase.testScanEmptyToEmpty(MultiTableInputFormatTestBase.java:196)
at
org.apache.hadoop.hbase.mapreduce.TestImportTSVWithVisibilityLabels.testBulkOutputWithTsvImporterTextMapper(TestImportTSVWithVisibilityLabels.java:253)
at
org.apache.hadoop.hbase.util.TestHBaseFsck.testFixByTable(TestHBaseFsck.java:1652)
at
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.testColumnFamilySettings(TestHFileOutputFormat.java:829)
at
org.apache.hadoop.hbase.mapreduce.TestTableMapReduceBase.testCombiner(TestTableMapReduceBase.java:106)
at
org.apache.hadoop.hbase.mapreduce.TestCopyTable.testRenameFamily(TestCopyTable.java:214)
at
org.apache.hadoop.hbase.mapred.TestTableSnapshotInputFormat.testWithMapReduceImpl(TestTableSnapshotInputFormat.java:216)
at
org.apache.hadoop.hbase.mapreduce.TableSnapshotInputFormatTestBase.testWithMapReduce(TableSnapshotInputFormatTestBase.java:112)
at
org.apache.hadoop.hbase.mapred.TestTableSnapshotInputFormat.testWithMapReduceMultiRegion(TestTableSnapshotInputFormat.java:141)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15032//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15032//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15032//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15032//console
This message is automatically generated.
Per-Region metrics can be stale
---
Key: HBASE-14166
URL: https://issues.apache.org/jira/browse/HBASE-14166
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-14166-v1.patch, HBASE-14166-v2.patch,
HBASE-14166.patch
We're seeing some machines that are reporting only old region metrics. It
seems like at some point the Hadoop metrics system decided which metrics to
display and which not to. From then on it was not changing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14166) Per-Region metrics can be stale
[
https://issues.apache.org/jira/browse/HBASE-14166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646855#comment-14646855
]
Hadoop QA commented on HBASE-14166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747864/HBASE-14166.patch
against master branch at commit 9f4aeca7c84d3e0c0b2067275e04c6c29ace948b.
ATTACHMENT ID: 12747864
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail with Hadoop version 2.4.0.
Compilation errors resume:
[ERROR] COMPILATION ERROR :
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java:[8,34]
cannot find symbol
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on
project hbase-hadoop2-compat: Compilation failure
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/metrics2/lib/DefaultMetricsSystemHelper.java:[8,34]
cannot find symbol
[ERROR] symbol: method removeObjectName(java.lang.String)
[ERROR] location: variable INSTANCE of type
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn goals -rf :hbase-hadoop2-compat
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14929//console
This message is automatically generated.
Per-Region metrics can be stale
---
Key: HBASE-14166
URL: https://issues.apache.org/jira/browse/HBASE-14166
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-14166.patch
We're seeing some machines that are reporting only old region metrics. It
seems like at some point the Hadoop metrics system decided which metrics to
display and which not to. From then on it was not changing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
