Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 29 Aug 2011 23:01:37 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1972451129.5337.1314658897998.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <386243305.34777.1313186727209.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2258) TestLeaseRecovery2 fails as lease
 hard limit is not reset to default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers commented on HDFS-2258:
--------------------------------------

+1, the latest patch looks good to me. TestOfflineEditsViewer and TestDfsOverAvroRpc are currently failing on trunk. I feel confident the other test failures are unrelated to this patch.

> TestLeaseRecovery2 fails as lease hard limit is not reset to default
> --------------------------------------------------------------------
>
>                 Key: HDFS-2258
>                 URL: https://issues.apache.org/jira/browse/HDFS-2258
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node, test
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: leaseRecovery2-trunk.patch, leaseRecovery2-trunk.patch, leaseRecovery2-trunk.patch, leaseRecovery2.patch
>
>
> TestLeaseRecovery2.testSoftLeaseRecovery() fails as lease hard limit remains set to 1 sec from the previous test case. If initial file creation in testSoftLeaseRecovery() takes longer than 1 sec, NN correctly reassigns the lease to itself and starts recovery. The test fails as the client cannot hflush() and close the file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira