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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/10/19 00:11:51 UTC

[jira] [Commented] (HBASE-9736) Alow more than one log splitter per RS

    [ https://issues.apache.org/jira/browse/HBASE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799580#comment-13799580 ] 

stack commented on HBASE-9736:
------------------------------

It seems hard-baked-in that we do one task/split per RS.  Tasks for a full WAL run about 30-60 seconds.  Doing three splits per server in // could impinge on a serving RS but would cut down the WAL split component of MTTR, the longest pole.

> Alow more than one log splitter per RS
> --------------------------------------
>
>                 Key: HBASE-9736
>                 URL: https://issues.apache.org/jira/browse/HBASE-9736
>             Project: HBase
>          Issue Type: Improvement
>          Components: MTTR
>            Reporter: stack
>            Priority: Critical
>
> IIRC, this is an idea that came from the lads at Xiaomi.
> I have a small cluster of 6 RSs and one went down.  It had a few WALs.  I see this in logs:
> 2013-10-09 05:47:27,890 DEBUG org.apache.hadoop.hbase.master.SplitLogManager: total tasks = 25 unassigned = 21
> WAL splitting is held up for want of slots out on the cluster to split WALs.
> We need to be careful we don't overwhelm the foreground regionservers but more splitters should help get all back online faster.



--
This message was sent by Atlassian JIRA
(v6.1#6144)