[
https://issues.apache.org/jira/browse/HDFS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487232#comment-13487232
]
Hudson commented on HDFS-3789:
------------------------------
Integrated in Hadoop-trunk-Commit #2944 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/2944/])
Moved HDFS-3789 entry in CHANGES.txt from trunk to 2.0.3-alpha section
(Revision 1403765)
Result = SUCCESS
umamahesh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403765
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> JournalManager#format() should be able to throw IOException
> -----------------------------------------------------------
>
> Key: HDFS-3789
> URL: https://issues.apache.org/jira/browse/HDFS-3789
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: 3.0.0
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 3.0.0, 2.0.3-alpha
>
> Attachments: 0003-HDFS-3789-for-branch-2.patch, HDFS-3789.diff
>
>
> Currently JournalManager#format cannot throw any exception. As format can
> fail, we should be able to propogate this failure upwards. Otherwise, format
> will fail silently, and the admin will start using the cluster with a
> failed/unusable journal manager.
--
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
