Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 12 Jun 2012 05:14:43 +0000 (UTC)
From: "chunhui shen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1988658519.5909.1339478083588.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1215661311.14885.1338359723326.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HBASE-6134) Improvement for split-worker to speed
 up distributed-split-log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HBASE-6134?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

chunhui shen updated HBASE-6134:
--------------------------------

    Attachment: HBASE-6134v4.patch

Updating pach v4 with Ted's comments in review board :
Keep the config param: conf.getInt("hbase.splitlog.report.openedfiles", 3);
               =20
> Improvement for split-worker to speed up distributed-split-log
> --------------------------------------------------------------
>
>                 Key: HBASE-6134
>                 URL: https://issues.apache.org/jira/browse/HBASE-6134
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>            Priority: Critical
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6134.patch, HBASE-6134v2.patch, HBASE-6134v3-9=
2.patch, HBASE-6134v3.patch, HBASE-6134v4.patch
>
>
> First=EF=BC=8Cwe do the test between local-master-splitting and distribut=
ed-log-splitting
> Environment=EF=BC=9A34 hlog files, 5 regionservers,(after kill one, only =
4 rs do ths splitting work), 400 regions in one hlog file
> local-master-split:60s+
> distributed-log-splitting:165s+
> In fact, in our production environment, distributed-log-splitting also to=
ok 60s with 30 regionservers for 34 hlog files (regionserver may be in high=
 load)
> We found split-worker split one log file took about 20s
> (30ms~50ms per writer.close(); 10ms per create writers )
> I think we could do the improvement for this:
> Parallelizing the create and close writers in threads
> In the patch, change the logic for  distributed-log-splitting same as the=
 local-master-splitting and parallelizing the close in threads.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira