[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-20 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038701#comment-14038701
 ] 

Hudson commented on HDFS-3848:
--

SUCCESS: Integrated in Hadoop-Yarn-trunk #589 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/589/])
HDFS-3848. A Bug in recoverLeaseInternal method of FSNameSystem class. 
Contributed by Hooman Peiro Sajjad and Chen He. (kihwal: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1604011)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestLeaseRecovery2.java


 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Assignee: Chen He
  Labels: patch
 Fix For: 3.0.0, 2.5.0

 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-20 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038815#comment-14038815
 ] 

Hudson commented on HDFS-3848:
--

FAILURE: Integrated in Hadoop-Hdfs-trunk #1780 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1780/])
HDFS-3848. A Bug in recoverLeaseInternal method of FSNameSystem class. 
Contributed by Hooman Peiro Sajjad and Chen He. (kihwal: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1604011)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestLeaseRecovery2.java


 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Assignee: Chen He
  Labels: patch
 Fix For: 3.0.0, 2.5.0

 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-20 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038904#comment-14038904
 ] 

Hudson commented on HDFS-3848:
--

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1807 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1807/])
HDFS-3848. A Bug in recoverLeaseInternal method of FSNameSystem class. 
Contributed by Hooman Peiro Sajjad and Chen He. (kihwal: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1604011)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestLeaseRecovery2.java


 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Assignee: Chen He
  Labels: patch
 Fix For: 3.0.0, 2.5.0

 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-19 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037617#comment-14037617
 ] 

Hadoop QA commented on HDFS-3848:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12651425/HDFS-3848-v2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-hdfs-project/hadoop-hdfs.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/7176//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7176//console

This message is automatically generated.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-19 Thread Chen He (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037678#comment-14037678
 ] 

Chen He commented on HDFS-3848:
---

Hi [~rike], If you are not working on this issue, I will take it.  

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-19 Thread Kihwal Lee (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037682#comment-14037682
 ] 

Kihwal Lee commented on HDFS-3848:
--

+1 the patch looks good.  Hooman has been inactive for about two years. I will 
assign it to you Chen, but will give credit to all.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-19 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037715#comment-14037715
 ] 

Hudson commented on HDFS-3848:
--

SUCCESS: Integrated in Hadoop-trunk-Commit #5737 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5737/])
HDFS-3848. A Bug in recoverLeaseInternal method of FSNameSystem class. 
Contributed by Hooman Peiro Sajjad and Chen He. (kihwal: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1604011)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestLeaseRecovery2.java


 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Assignee: Chen He
  Labels: patch
 Fix For: 3.0.0, 2.5.0

 Attachments: HDFS-3848-1.patch, HDFS-3848-v2.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-17 Thread Kihwal Lee (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034258#comment-14034258
 ] 

Kihwal Lee commented on HDFS-3848:
--

I kicked the precommit again. It looks like the patch is still good, but it 
will be nice if a test case is added.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-17 Thread Chen He (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034282#comment-14034282
 ] 

Chen He commented on HDFS-3848:
---

I will add the test case. 

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-16 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032955#comment-14032955
 ] 

Hadoop QA commented on HDFS-3848:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12545609/HDFS-3848-1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-hdfs-project/hadoop-hdfs.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/7136//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7136//console

This message is automatically generated.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2014-06-16 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032961#comment-14032961
 ] 

Hadoop QA commented on HDFS-3848:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12545609/HDFS-3848-1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:

  org.apache.hadoop.hdfs.server.datanode.TestBPOfferService

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/7135//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7135//console

This message is automatically generated.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
 Attachments: HDFS-3848-1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2012-09-18 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13458211#comment-13458211
 ] 

Hadoop QA commented on HDFS-3848:
-

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12545609/HDFS-3848-1.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:

  org.apache.hadoop.hdfs.TestDatanodeBlockScanner

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/3203//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3203//console

This message is automatically generated.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Priority: Minor
  Labels: patch
 Attachments: HDFS-3848-1.patch

   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))

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


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2012-09-17 Thread Suresh Srinivas (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457256#comment-13457256
 ] 

Suresh Srinivas commented on HDFS-3848:
---

Hooman, could you post a patch for this? I will review and commit it.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Priority: Minor
  Labels: patch
   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))

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


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2012-09-17 Thread Hooman Peiro Sajjad (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457416#comment-13457416
 ] 

Hooman Peiro Sajjad commented on HDFS-3848:
---

Hi Suresh, no problem. I will post a patch soon.

 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
Priority: Minor
  Labels: patch
   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))

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


[jira] [Commented] (HDFS-3848) A Bug in recoverLeaseInternal method of FSNameSystem class

2012-08-23 Thread Kihwal Lee (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440481#comment-13440481
 ] 

Kihwal Lee commented on HDFS-3848:
--

Good find! 

I think we can just get rid of {{lease.getHolder().equals(holder)}}. The first 
condition, {{(leaseFile != null  leaseFile.equals(lease))}}, is sufficient, 
because {{Lease#equals()}} checks whether the holders are equal.



 A Bug in recoverLeaseInternal method of FSNameSystem class
 --

 Key: HDFS-3848
 URL: https://issues.apache.org/jira/browse/HDFS-3848
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Affects Versions: 0.23.1
Reporter: Hooman Peiro Sajjad
  Labels: patch
   Original Estimate: 1h
  Remaining Estimate: 1h

 This is a bug in logic of the method recoverLeaseInternal. In line 1322 it 
 checks if the owner of the file is trying to recreate the file. The condition 
 of the if statement is 
 (leaseFile != null  leaseFile.equals(lease)) || 
 lease.getHolder().equals(holder)
 As it can be seen, there are two operands (conditions) connected with an or 
 operator. The first operand is straight and will be true only if the holder 
 of the file is the new holder. But the problem is the second operand which 
 will be always true since the lease object is the one found by the holder 
 by calling Lease lease = leaseManager.getLease(holder); in line 1315.
 To fix this I think the if statement only should contain the following the 
 condition:
 (leaseFile != null  leaseFile.getHolder().equals(holder))

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira