You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/10/21 19:30:33 UTC

[jira] [Created] (ACCUMULO-3246) More insight into native map utilization/usage

Josh Elser created ACCUMULO-3246:
------------------------------------

             Summary: More insight into native map utilization/usage
                 Key: ACCUMULO-3246
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3246
             Project: Accumulo
          Issue Type: Improvement
          Components: tserver
            Reporter: Josh Elser
             Fix For: 1.7.0


I often find that I choose a value for the size of the native map out of the air without really having a good understanding of why I chose it  (aside from considerations of table.compaction.minor.logs.threshold and tserver.walog.max.size).

We don't have any insight into some basic metrics on the native maps. It would be nice to be able to answer questions like

* What is the utilization (space) of the native maps for a server
* How much time is the server spending writing data as opposed to allocating new blocks

I'm sure there are some other questions too.



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