Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 31 Aug 2015 12:40:45 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12860429.1440797139000.210348.1441024845812@Atlassian.JIRA>
In-Reply-To: <JIRA.12860429.1440797139000@Atlassian.JIRA>
References: <JIRA.12860429.1440797139000@Atlassian.JIRA>
 <JIRA.12860429.1440797139785@arcas>
Subject: [jira] [Updated] (HBASE-14333) responseTooLarge/Slow logs are not
 actionable when the rpc method is ExecService
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-14333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-14333:
--------------------------------
    Component/s: Operability

> responseTooLarge/Slow logs are not actionable when the rpc method is ExecService
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-14333
>                 URL: https://issues.apache.org/jira/browse/HBASE-14333
>             Project: HBase
>          Issue Type: Improvement
>          Components: Operability
>            Reporter: Nick Dimiduk
>              Labels: beginner
>
> This seems to come up mostly for users running Phoenix. We get logs saying a response is too large or slow, but the coprocessoring being invoked is masked. This makes it hard to diagnose which aspect of the query needs to be optimized. Adding the coprocessor class and method would make these log lines much more informative.


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