Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <633070599.1236202796304.JavaMail.jira@brutus>
Date: Wed, 4 Mar 2009 13:39:56 -0800 (PST)
From: "Billy Pearson (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1185) wrong request/sec in the gui
 reporting wrong
In-Reply-To: <220432380.1233854999797.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Billy Pearson commented on HBASE-1185:
--------------------------------------

+1 the numbers look good now
thanks for the patch

> wrong request/sec in the gui reporting wrong
> --------------------------------------------
>
>                 Key: HBASE-1185
>                 URL: https://issues.apache.org/jira/browse/HBASE-1185
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client, regionserver
>    Affects Versions: 0.19.0
>         Environment: 0.19.0
>            Reporter: Billy Pearson
>            Priority: Minor
>             Fix For: 0.20.0
>
>         Attachments: hbase-1185.patch
>
>
> I am seeing lower number of request in the masters gui then I have seen in 0.18.0 while scanning.
> I thank part of it is we moved to report per sec request not per 3 secs so the request should be 1/3 of the old numbers I was getting.
> hbase.client.scanner.caching is not the reason the request are under reported.
> I set hbase.client.scanner.caching = 1 and still get about 2K request a sec in the gui
> but when the job is done I take records / job time and get 36,324/ records /sec. So
> there must be some caching out side of the hbase.client.scanner.caching making the
> request per sec lower then it should be. I know it running faster then reported just thought
> it might give some new users the wrong impression that request/sec = read/write /sec.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.