You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2014/01/30 19:28:16 UTC
[jira] [Commented] (ACCUMULO-2288) Tserver under heavy ingest dies
when unloading many tablets
[ https://issues.apache.org/jira/browse/ACCUMULO-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886873#comment-13886873 ]
Keith Turner commented on ACCUMULO-2288:
----------------------------------------
What was your selection criteria for trimming the logs? I am curious what the logs related to compactions look like. What type of data were you writing?
> Tserver under heavy ingest dies when unloading many tablets
> -----------------------------------------------------------
>
> Key: ACCUMULO-2288
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2288
> 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
(v6.1.5#6160)