Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 11 Sep 2014 01:47:34 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12740634.1410389522000.5904.1410400054112@Atlassian.JIRA>
In-Reply-To: <JIRA.12740634.1410389522000@Atlassian.JIRA>
References: <JIRA.12740634.1410389522000@Atlassian.JIRA>
 <JIRA.12740634.1410389522105@arcas>
Subject: [jira] [Commented] (HDFS-7042) Upgrade fails for Windows HA cluster
 due to file locks held during rename in JournalNode.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arpit Agarwal commented on HDFS-7042:
-------------------------------------

+1

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