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

Hudson commented on HDFS-3695:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1212 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1212/])
    Moved HDFS-3695 entry in CHANGES.txt from trunk to 2.0.3-alpha section 
(Revision 1403748)

     Result = FAILURE
umamahesh : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403748
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

                
> Genericize format() to non-file JournalManagers
> -----------------------------------------------
>
>                 Key: HDFS-3695
>                 URL: https://issues.apache.org/jira/browse/HDFS-3695
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: QuorumJournalManager (HDFS-3077)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 3.0.0, 2.0.3-alpha
>
>         Attachments: 0002-HDFS-3695-for-branch-2.patch, hdfs-3695.txt, 
> hdfs-3695.txt, hdfs-3695.txt
>
>
> Currently, the "namenode -format" and "namenode -initializeSharedEdits" 
> commands do not understand how to do anything with non-file-based shared 
> storage. This affects both BookKeeperJournalManager and QuorumJournalManager.
> This JIRA is to plumb through the formatting of edits directories using 
> pluggable journal manager implementations so that no separate step needs to 
> be taken to format them -- the same commands will work for NFS-based storage 
> or one of the alternate implementations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to