hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7939) Two fsimage_rollback_* files are created which are not deleted after rollback.
Date Fri, 10 Apr 2015 13:09:15 GMT

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

Hudson commented on HDFS-7939:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #160 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/160/])
HDFS-7939. Two fsimage_rollback_* files are created which are not deleted after rollback.
(Contributed by J.Andreina) (vinayakumarb: rev 987c9e12e184b35a5abab49f4188e22509ad63a5)
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> Two fsimage_rollback_* files are created which are not deleted after rollback.
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-7939
>                 URL: https://issues.apache.org/jira/browse/HDFS-7939
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: J.Andreina
>            Assignee: J.Andreina
>            Priority: Critical
>             Fix For: 2.8.0
>
>         Attachments: HDFS-7939.1.patch
>
>
> During checkpoint , if any failure in uploading to the remote Namenode  then restarting
Namenode with "rollingUpgrade started" option creates 2 fsimage_rollback_* at Active Namenode
.
> On rolling upgrade rollback , initially created fsimage_rollback_* file is not been deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message