[jira] [Updated] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

2012-08-27 Thread Eli Collins (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3856:
--

  Resolution: Fixed
   Fix Version/s: 2.2.0-alpha
Target Version/s:   (was: 2.2.0-alpha)
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

I've committed this and merged to branch-2.

> TestHDFSServerPorts failure is causing surefire fork failure
> 
>
> Key: HDFS-3856
> URL: https://issues.apache.org/jira/browse/HDFS-3856
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.2.0-alpha
>Reporter: Thomas Graves
>Assignee: Eli Collins
>Priority: Blocker
> Fix For: 2.2.0-alpha
>
> Attachments: hdfs-3856.txt, hdfs-3856.txt
>
>
> We have been seeing the hdfs tests on trunk and branch-2 error out with fork 
> failures.  I see the hadoop jenkins trunk build is also seeing these:
> https://builds.apache.org/view/Hadoop/job/Hadoop-trunk/lastCompletedBuild/console

--
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] [Updated] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

2012-08-27 Thread Eli Collins (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3856:
--

Attachment: hdfs-3856.txt

Slightly updated patch to cleanup the log message following the check.

> TestHDFSServerPorts failure is causing surefire fork failure
> 
>
> Key: HDFS-3856
> URL: https://issues.apache.org/jira/browse/HDFS-3856
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.2.0-alpha
>Reporter: Thomas Graves
>Assignee: Eli Collins
>Priority: Blocker
> Attachments: hdfs-3856.txt, hdfs-3856.txt
>
>
> We have been seeing the hdfs tests on trunk and branch-2 error out with fork 
> failures.  I see the hadoop jenkins trunk build is also seeing these:
> https://builds.apache.org/view/Hadoop/job/Hadoop-trunk/lastCompletedBuild/console

--
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] [Updated] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

2012-08-27 Thread Eli Collins (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3856:
--

Attachment: hdfs-3856.txt

Thanks for triaging Kihwal!

Patch attached.

NN#startTrashEmptier is not currently making an RPC. This patch updates 
NameNode#startTrashEmptier to use the conf to determine the interval rather 
than get the server defaults object (which checks the operation, which fails in 
the BN case). The conf is the same that was used to initialize server defaults 
so it's the same value. 

> TestHDFSServerPorts failure is causing surefire fork failure
> 
>
> Key: HDFS-3856
> URL: https://issues.apache.org/jira/browse/HDFS-3856
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.2.0-alpha
>Reporter: Thomas Graves
>Assignee: Eli Collins
>Priority: Blocker
> Attachments: hdfs-3856.txt
>
>
> We have been seeing the hdfs tests on trunk and branch-2 error out with fork 
> failures.  I see the hadoop jenkins trunk build is also seeing these:
> https://builds.apache.org/view/Hadoop/job/Hadoop-trunk/lastCompletedBuild/console

--
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] [Updated] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

2012-08-27 Thread Eli Collins (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eli Collins updated HDFS-3856:
--

 Target Version/s: 2.2.0-alpha
Affects Version/s: (was: 3.0.0)
   Status: Patch Available  (was: Open)

Forgot to mention TestHDFSServerPorts now passes for me.

> TestHDFSServerPorts failure is causing surefire fork failure
> 
>
> Key: HDFS-3856
> URL: https://issues.apache.org/jira/browse/HDFS-3856
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.2.0-alpha
>Reporter: Thomas Graves
>Assignee: Eli Collins
>Priority: Blocker
> Attachments: hdfs-3856.txt
>
>
> We have been seeing the hdfs tests on trunk and branch-2 error out with fork 
> failures.  I see the hadoop jenkins trunk build is also seeing these:
> https://builds.apache.org/view/Hadoop/job/Hadoop-trunk/lastCompletedBuild/console

--
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] [Updated] (HDFS-3856) TestHDFSServerPorts failure is causing surefire fork failure

2012-08-27 Thread Kihwal Lee (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kihwal Lee updated HDFS-3856:
-

Summary: TestHDFSServerPorts failure is causing surefire fork failure  
(was: fork failure running hdfs unit tests trunk and branch-2)

> TestHDFSServerPorts failure is causing surefire fork failure
> 
>
> Key: HDFS-3856
> URL: https://issues.apache.org/jira/browse/HDFS-3856
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 3.0.0, 2.2.0-alpha
>Reporter: Thomas Graves
>Priority: Blocker
>
> We have been seeing the hdfs tests on trunk and branch-2 error out with fork 
> failures.  I see the hadoop jenkins trunk build is also seeing these:
> https://builds.apache.org/view/Hadoop/job/Hadoop-trunk/lastCompletedBuild/console

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