[
https://issues.apache.org/jira/browse/ACCUMULO-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886880#comment-13886880
]
Mike Drob commented on ACCUMULO-2288:
-------------------------------------
For the tserver log, I just started at midnight and stopped after it died. The
next message is ~10 minutes later saying that it is starting up.
For the master, I started just before the splits began and stopped after the
tserver was declared dead and tablets were moving off of it. I removed all the
lines from the master log saying "Telling a.b.c.d to use loggers [logger1,
logger2]"
I had 10 clients writing simultaneously. Each mutation was ~200MB, and it looks
like they were all going to a single tablet server because the splits had not
yet balanced around.
> 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)
