Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 4 May 2012 02:50:48 +0000 (UTC)
From: "Zhihong Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <275671310.25272.1336099848683.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1784335562.1736.1333390763782.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5699) Run with > 1 WAL in HRegionServer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zhihong Yu commented on HBASE-5699:
-----------------------------------

Using trunk has the drawback that performance numbers (without this feature) gathered on day N may be obsolete by day N + 5, considering the amount of changes going into trunk.

I would suggest tackling replication as first priority. Dictionary WAL compression brought unexpected complexities w.r.t. replication. We shouldn't make replication any harder.

w.r.t. refactoring HLog into an interface, I tend to think that the interface should make different implementations possible.
If we only have one implementation, it is not easy to evaluate the effectiveness of the refactoring.
                
> Run with > 1 WAL in HRegionServer
> ---------------------------------
>
>                 Key: HBASE-5699
>                 URL: https://issues.apache.org/jira/browse/HBASE-5699
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: binlijin
>            Assignee: Li Pi
>


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