Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 16 Apr 2012 18:40:19 +0000 (UTC)
From: "dhruba borthakur (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1349220659.29667.1334601619501.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <595597907.12772.1331732678494.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3092) Enable journal protocol based
 editlog streaming for standby namenode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

dhruba borthakur commented on HDFS-3092:
----------------------------------------

I still somehow like the BK approach, especially because it can store transaction logs from multiple namenodes, this is something that is very needed for HDFS-federation. If we can get BK to scale and be performant, it is a possibility that HBase can store transaction logs in there too, especially of the latencies are much smaller (and disk-failure recoveries faster) than a typical HDFS write pipeline.  
                
> Enable journal protocol based editlog streaming for standby namenode
> --------------------------------------------------------------------
>
>                 Key: HDFS-3092
>                 URL: https://issues.apache.org/jira/browse/HDFS-3092
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha, name-node
>    Affects Versions: 0.24.0, 0.23.3
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: MultipleSharedJournals.pdf, MultipleSharedJournals.pdf, MultipleSharedJournals.pdf
>
>
> Currently standby namenode relies on reading shared editlogs to stay current with the active namenode, for namespace changes. BackupNode used streaming edits from active namenode for doing the same. This jira is to explore using journal protocol based editlog streams for the standby namenode. A daemon in standby will get the editlogs from the active and write it to local edits. To begin with, the existing standby mechanism of reading from a file, will continue to be used, instead of from shared edits, from the local edits.

--
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