Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 17 Jun 2011 11:00:50 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1077396033.14470.1308308450643.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <828631395.3593.1307549399377.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-3963) Schedule all log-spliiting at
 startup all at once
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-3963:
-------------------------------

Integrated in HBase-TRUNK #1976 (See [https://builds.apache.org/job/HBase-TRUNK/1976/])
    

> Schedule all log-spliiting at startup all at once
> -------------------------------------------------
>
>                 Key: HBASE-3963
>                 URL: https://issues.apache.org/jira/browse/HBASE-3963
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Prakash Khemani
>            Assignee: Prakash Khemani
>             Fix For: 0.92.0
>
>         Attachments: schedule-all-splitlog-trunk.patch, schedule-all-splitlog.patch
>
>
> When distributed log splitting is enabled then it is better to call splitLog() for all region servers simultaneously. A large number of splitlog tasks will get scheduled - one for each log file. But a splitlog-worker (region server) executes only one task at a time and there shouldn't be a danger of DFS overload. Scheduling all the tasks at once ensures maximum parallelism.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira