Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 5 Apr 2012 20:46:31 +0000 (UTC)
From: "Suresh Srinivas (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <461785048.19552.1333658791260.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <594828263.17235.1333638503422.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-3204) Minor modification to
 JournalProtocol.proto to make it generic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas updated HDFS-3204:
----------------------------------

    Attachment: HDFS-3204.txt
    
> Minor modification to JournalProtocol.proto to make it generic
> --------------------------------------------------------------
>
>                 Key: HDFS-3204
>                 URL: https://issues.apache.org/jira/browse/HDFS-3204
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.24.0
>            Reporter: Suresh Srinivas
>         Attachments: HDFS-3204.txt, HDFS-3204.txt, HDFS-3204.txt
>
>
> JournalProtocol.proto uses NamenodeRegistration in methods such as journal() for identifying the source. I want to make it generic so that the method can be called with journal information to identify the journal. I plan to use the protocol also for sync purposes, where the source of the journal can be some thing other than namenode.

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