accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2288) Tserver under heavy ingest dies when unloading many tablets
Date Thu, 30 Jan 2014 19:38:12 GMT


Keith Turner commented on ACCUMULO-2288:

Another thing to consider is that the memory management decisions may be slightly delayed.
  In {{o.a.a.s.tabletserver.TabletServerResourceManager.TabletResourceManager.updateMemoryUsageStats()}}
changes to a tablets memory are added to a queue.  Another thread takes messages off of this
queue and uses them to make decisions about global memory usage such as initiating minor compactions
and holding writes.  With these large mutations and the delay in memory mgmt decisions introduced
by the queue this may allow more than the configured amount to be written.  

> Tserver under heavy ingest dies when unloading many tablets
> -----------------------------------------------------------
>                 Key: ACCUMULO-2288
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.4.4
>         Environment: 4G heap, 6G native map for tserver;
> table.compaction.minor.logs.threshold=6
>            Reporter: Mike Drob
>         Attachments: logs.tar.gz
> # Create a table
> # Add lots of splits (they'll all be on the same server)
> # Start a heavy ingest load
> # Wait for master to decide to balance
> # When master sends unload requests, tablet server dies.
> It would be good if instead of trying to flush everything at once, the tserver could
go a little bit slower, but stay up. Or at least provide better logging.

This message was sent by Atlassian JIRA

View raw message