Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 16 Aug 2011 21:45:36 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2002235009.42870.1313531136104.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <726277654.5522.1311112738101.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4117) Slow Query Log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-4117:
------------------------------

Thanks Riley.

Over in hbase-880 when we were talking refactoring, base class there was Operation -- e.g. https://issues.apache.org/jira/secure/attachment/12391309/NewCilentAPIProposoal4.gif -- in a few proposals and RowOperation in others.  You already have a Row interface, so maybe Operation is ok... (I don't see row specifics going on in your Operation instance currently).  Good stuff.

> Slow Query Log
> --------------
>
>                 Key: HBASE-4117
>                 URL: https://issues.apache.org/jira/browse/HBASE-4117
>             Project: HBase
>          Issue Type: New Feature
>          Components: ipc
>            Reporter: Riley Patterson
>            Assignee: Riley Patterson
>            Priority: Minor
>              Labels: client, ipc
>         Attachments: HBASE-4117.patch
>
>
> Produce log messages for slow queries. The RPC server will decide what is slow based on a configurable "warn response time" parameter. Queries designated as slow will then output a "response too slow" message followed by a fingerprint of the query, and a summary limited in size by another configurable parameter (to limit log spamming).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira