Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77AC117761 for ; Fri, 24 Apr 2015 17:31:35 +0000 (UTC) Received: (qmail 69013 invoked by uid 500); 24 Apr 2015 17:31:34 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 68933 invoked by uid 500); 24 Apr 2015 17:31:34 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 68921 invoked by uid 99); 24 Apr 2015 17:31:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 17:31:34 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for dev@hbase.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 17:31:28 +0000 Received: from mail-wg0-f41.google.com (mail-wg0-f41.google.com [74.125.82.41]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 8E1FB43E47 for ; Fri, 24 Apr 2015 17:31:07 +0000 (UTC) Received: by wgin8 with SMTP id n8so57781877wgi.0 for ; Fri, 24 Apr 2015 10:29:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eN9U1j4mqOXmxgT+5N70BGGzbyXZkklPL8Yndlusc2I=; b=suaLuYwwYVBXFRjEn97pR5TH+JVr7XqOrC29pPP6/YlXFciibDWNTEd1fpWcefADck 6DOAoHB+8AGbxmLgSETR6gu+iU2EjeXFwCL///pGXqM1c1GVXvYKSnS/3YBMbLYhoBwL 23hImXz6X/i9wotCZnPoiNaCB18J9/VBFDNM/U5TtqS0+cp2F9ndtjf/8v8BXJSjGFCU +2NNi9/j3TPQ8Sbc9YHwLTTP76NMUejKc5nDlNZXmfD3gbikWxmYWpvMKRypB5ZsxYGm zI1e8+HY6IY1W9sLDW6wwg+FnEKZRmaF1dlu14xU8JkPCSxGr7KcKDd5hZyHiXNxhZpT TL4Q== MIME-Version: 1.0 X-Received: by 10.180.98.230 with SMTP id el6mr5763217wib.16.1429896576408; Fri, 24 Apr 2015 10:29:36 -0700 (PDT) Received: by 10.194.2.242 with HTTP; Fri, 24 Apr 2015 10:29:36 -0700 (PDT) In-Reply-To: References: Date: Fri, 24 Apr 2015 22:59:36 +0530 Message-ID: Subject: Re: How to retrieve master metrics from JMX client From: Ashish Singhi To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=bcaec555509280a09c05147bbd04 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec555509280a09c05147bbd04 Content-Type: text/plain; charset=UTF-8 Yes, HBASE-10289 -- Ashish Singhi On Fri, Apr 24, 2015 at 10:54 PM, Stack wrote: > Does git blame take you to an issue with any reasoning as to why master jmx > is turned off Ashish? > St.Ack > > On Fri, Apr 24, 2015 at 9:47 AM, Ashish Singhi > > wrote: > > > Hi devs. > > > > I see that in all other code branches other than 0.98 we do not load > > JMXListener for masters. > > Here is the below code snippet from JMXListener class. > > > > {code} > > if (env instanceof MasterCoprocessorEnvironment) { > > LOG.error("JMXListener should not be loaded in Master > Environment!"); > > } else if (env instanceof RegionServerCoprocessorEnvironment) { > > // running on RegionServer --since 0.99 HMaster is also a > > HRegionServer > > rmiRegistryPort = > > conf.getInt("regionserver" + RMI_REGISTRY_PORT_CONF_KEY, > > defRMIRegistryPort); > > rmiConnectorPort = > > conf.getInt("regionserver" + RMI_CONNECTOR_PORT_CONF_KEY, > > rmiRegistryPort); > > LOG.info("RegionServer rmiRegistryPort:" + rmiRegistryPort > > + ",RegionServer rmiConnectorPort:" + rmiConnectorPort); > > > > } else if (env instanceof RegionCoprocessorEnvironment) { > > LOG.error("JMXListener should not be loaded in Region > Environment!"); > > } > > {code} > > > > How can one retrieve master metrics from JMX client ? As we have a > > system like OM(operation management) which monitors master metrics > > using JMX client. We used to retrieve these metrics successfully from > > 0.98 code branch as there JMListener is loaded in both Master and > > RegionServer environments. > > > > -- > > Ashish Singhi > > > --bcaec555509280a09c05147bbd04--