[ https://issues.apache.org/jira/browse/HDFS-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131538#comment-14131538 ]
Hudson commented on HDFS-7042: ------------------------------ FAILURE: Integrated in Hadoop-Mapreduce-trunk #1894 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1894/]) HDFS-7042. Upgrade fails for Windows HA cluster due to file locks held during rename in JournalNode. Contributed by Chris Nauroth. (cnauroth: rev 80ac6aabcea9f808fd55504cdaef2da7b50da7f1) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/Journal.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/util/BestEffortLongFile.java > Upgrade fails for Windows HA cluster due to file locks held during rename in > JournalNode. > ----------------------------------------------------------------------------------------- > > Key: HDFS-7042 > URL: https://issues.apache.org/jira/browse/HDFS-7042 > Project: Hadoop HDFS > Issue Type: Bug > Components: journal-node > Affects Versions: 2.4.1 > Reporter: Chris Nauroth > Assignee: Chris Nauroth > Priority: Blocker > Fix For: 2.6.0 > > Attachments: HDFS-7042.1.patch > > > During upgrade of an HA cluster, the JournalNode attempts to rename the > current storage directory to previous. However, the process still holds the > last committed transaction ID file opened while this is happening. On > Windows, this is a locking violation that causes the rename operation to > fail. Ultimately the whole upgrade fails. There is a similar problem during > rollback too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)