accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3246) More insight into native map utilization/usage
Date Tue, 21 Oct 2014 19:38:34 GMT


Josh Elser commented on ACCUMULO-3246:

So, that's a good example of what you could notice if you oversize the memory maps. Significantly
large maps will be underused, and I would hope that we would see that in an active system.
Conversely, if the maps don't reach that threshold, I would expect to see that they're mostly

Perhaps it wouldn't tell us more than what we already know, but I was thinking that it would
be nice to be certain of that instead of just assuming. 

> More insight into native map utilization/usage
> ----------------------------------------------
>                 Key: ACCUMULO-3246
>                 URL:
>             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

View raw message