hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12665) When aborting, dump metrics
Date Tue, 09 Dec 2014 21:46:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240114#comment-14240114
] 

stack commented on HBASE-12665:
-------------------------------

Hard to write a test for this. I tried /jmx in UI and looking in tests that abort I see this:

{code}
 781 2014-12-09 13:44:21,244 FATAL [main] regionserver.HRegionServer(1921): ABORTING region
server kalashnikov-19.att.net,61685,1418161460417: I'm dead
 782 2014-12-09 13:44:21,244 FATAL [main] regionserver.HRegionServer(1927): RegionServer abort:
loaded coprocessors are: [org.apache.hadoop.hbase.coprocessor.MultiRowMutationEndpoint]
 783 {
 784   "beans" : [ {
 785     "name" : "java.lang:type=MemoryPool,name=PS Survivor Space",
 786     "modelerType" : "sun.management.MemoryPoolImpl",
 787     "Name" : "PS Survivor Space",
 788     "Type" : "HEAP",
 789     "Valid" : true,
 790     "Usage" : {
 791       "committed" : 35127296,
 792       "init" : 11010048,
 793       "max" : 35127296,
 794       "used" : 34974144
 795     },
 796     "PeakUsage" : {
 797       "committed" : 35127296,
 798       "init" : 11010048,
 799       "max" : 35127296,
 800       "used" : 34974144
 801     },
 802     "MemoryManagerNames" : [ "PS MarkSweep", "PS Scavenge" ],
 803     "UsageThresholdSupported" : false,
 804     "CollectionUsageThreshold" : 0,
 805     "CollectionUsageThresholdExceeded" : false,
 806     "CollectionUsageThresholdCount" : 0,
 807     "CollectionUsage" : {
 808       "committed" : 35127296,
 809       "init" : 11010048,
 810       "max" : 35127296,
 811       "used" : 34974144
 812     },
 813     "CollectionUsageThresholdSupported" : true,
 814     "ObjectName" : "java.lang:type=MemoryPool,name=PS Survivor Space"
 815   }, {
 816     "name" : "Hadoop:service=HBase,name=Master,sub=AssignmentManger",
 817     "modelerType" : "Master,sub=AssignmentManger",
 818     "tag.Context" : "master",
 819     "tag.Hostname" : "kalashnikov-19.att.net",
 820     "ritOldestAge" : 0,
 821     "ritCount" : 0,
 822     "BulkAssign_num_ops" : 5,
 823     "BulkAssign_min" : 0,
 824     "BulkAssign_max" : 17,
 825     "BulkAssign_mean" : 5.8,
 826     "BulkAssign_median" : 0.0,
 827     "BulkAssign_75th_percentile" : 14.5,
 828     "BulkAssign_95th_percentile" : 17.0,
 829     "BulkAssign_99th_percentile" : 17.0,
...
{code}

> When aborting, dump metrics
> ---------------------------
>
>                 Key: HBASE-12665
>                 URL: https://issues.apache.org/jira/browse/HBASE-12665
>             Project: HBase
>          Issue Type: Bug
>          Components: Operability
>            Reporter: stack
>            Assignee: stack
>             Fix For: 1.0.0, 2.0.0, 0.98.9
>
>         Attachments: 0001-First-cut.patch
>
>
> We used to dump out all metrics when we were exiting on abort. Was of use debugging why
the abort.  We used to have this.  [~jdcryans] noticed it was dropped by his brother [~eclark]
over in HBASE-6410 "Move RegionServer Metrics to metrics2" To stop the two brothers fighting
I intervened with this patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message