Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Date: Thu, 5 Apr 2012 18:04:26 +0000 (UTC)
From: "Keith Turner (Updated) (JIRA)" <jira@apache.org>
To: dev@accumulo.apache.org
Message-ID: 
 <651815241.18405.1333649066141.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <149226687.18375.1333648947006.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (ACCUMULO-517) Improve scan information available
 on monitor page
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner updated ACCUMULO-517:
----------------------------------

    Assignee: Keith Turner  (was: Eric Newton)
    
> Improve scan information available on monitor page
> --------------------------------------------------
>
>                 Key: ACCUMULO-517
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-517
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor, tserver
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.5.0
>
>
> The monitor page does not give good awareness with respect to what is actually happening with scans.  It would be interesting to know the following.
>  * Number of seeks done on server side
>  * Number of entries read on the server side
>  * Number of entries returned on the servers die
> A filtering iterator may do a lot of seeks and drop a lot of data, but this is not really shown in anyway on the monitor page.  If we displayed the info above, then a user could see the filter seeking, reading and not returning data.  Currently only the amount of data returned by iterators is displayed, not the amount of data read by iterators.
> Also the current monitor page displays scan session, which corresponds to a user starting a scan on a tablet server.  It does give the user a info about how many seeks the iterators that are running as part of that scan session are doing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira