Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 25 Dec 2017 10:42:00 +0000 (UTC)
From: "Jingyun Tian (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13121195.1511849288000.529349.1514198520391@Atlassian.JIRA>
In-Reply-To: <JIRA.13121195.1511849288000@Atlassian.JIRA>
References: <JIRA.13121195.1511849288000@Atlassian.JIRA> <JIRA.13121195.1511849288924@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-19358) Improve the stability of splitting
 log when do fail over
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 25 Dec 2017 10:42:07 -0000


     [ https://issues.apache.org/jira/browse/HBASE-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jingyun Tian updated HBASE-19358:
---------------------------------
    Attachment: HBASE-19358-v5.patch

> Improve the stability of splitting log when do fail over
> --------------------------------------------------------
>
>                 Key: HBASE-19358
>                 URL: https://issues.apache.org/jira/browse/HBASE-19358
>             Project: HBase
>          Issue Type: Improvement
>          Components: MTTR
>    Affects Versions: 0.98.24
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>         Attachments: HBASE-19358-v1.patch, HBASE-19358-v4.patch, HBASE-19358-v5.patch, HBASE-19358.patch
>
>
> The way we splitting log now is like the following figure:
> !https://issues.apache.org/jira/secure/attachment/12902997/split-logic-old.jpg!
> The problem is the OutputSink will write the recovered edits during splitting log, which means it will create one WriterAndPath for each region and retain it until the end. If the cluster is small and the number of regions per rs is large, it will create too many HDFS streams at the same time. Then it is prone to failure since each datanode need to handle too many streams.
> Thus I come up with a new way to split log.  
> !https://issues.apache.org/jira/secure/attachment/12902998/split-logic-new.jpg!
> We try to cache all the recovered edits, but if it exceeds the MaxHeapUsage, we will pick the largest EntryBuffer and write it to a file (close the writer after finish). Then after we read all entries into memory, we will start a writeAndCloseThreadPool, it starts a certain number of threads to write all buffers to files. Thus it will not create HDFS streams more than *_hbase.regionserver.hlog.splitlog.writer.threads_* we set.
> The biggest benefit is we can control the number of streams we create during splitting log, 
> it will not exceeds *_hbase.regionserver.wal.max.splitters * hbase.regionserver.hlog.splitlog.writer.threads_*, but before it is *_hbase.regionserver.wal.max.splitters * the number of region the hlog contains_*.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)