Hadoop-Hdfs-trunk - Build # 590 - Still Failing

[Apache Hudson Server]

See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk/590/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 735848 lines...]
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target
 [echo]  Including clover.jar in the war file ...
[cactifywar] Analyzing war: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/hdfsproxy-2.0-test.war
[cactifywar] Building war: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/test.war

cactifywar:

test-cactus:
 [echo]  Free Ports: startup-13253 / http-13254 / https-13255
 [echo] Please take a deep breath while Cargo gets the Tomcat for running 
the servlet tests...
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/conf
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/webapps
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/temp
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/logs
[mkdir] Created dir: 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/reports
 [copy] Copying 1 file to 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/conf
 [copy] Copying 1 file to 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/conf
 [copy] Copying 1 file to 
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/conf
   [cactus] -
   [cactus] Running tests against Tomcat 5.x @ http://localhost:13254
   [cactus] -
   [cactus] Deploying 
[/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/test.war]
 to 
[/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build/contrib/hdfsproxy/target/tomcat-config/webapps]...
   [cactus] Tomcat 5.x starting...
Server [Apache-Coyote/1.1] started
   [cactus] WARNING: multiple versions of ant detected in path for junit 
   [cactus]  
jar:file:/homes/hudson/tools/ant/latest/lib/ant.jar!/org/apache/tools/ant/Project.class
   [cactus]  and 
jar:file:/homes/hudson/.ivy2/cache/ant/ant/jars/ant-1.6.5.jar!/org/apache/tools/ant/Project.class
   [cactus] Running org.apache.hadoop.hdfsproxy.TestAuthorizationFilter
   [cactus] Tests run: 4, Failures: 2, Errors: 0, Time elapsed: 0.477 sec
   [cactus] Test org.apache.hadoop.hdfsproxy.TestAuthorizationFilter FAILED
   [cactus] Running org.apache.hadoop.hdfsproxy.TestLdapIpDirFilter
   [cactus] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.341 sec
   [cactus] Tomcat 5.x started on port [13254]
   [cactus] Running org.apache.hadoop.hdfsproxy.TestProxyFilter
   [cactus] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.323 sec
   [cactus] Running org.apache.hadoop.hdfsproxy.TestProxyForwardServlet
   [cactus] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.319 sec
   [cactus] Running org.apache.hadoop.hdfsproxy.TestProxyUtil
   [cactus] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.806 sec
   [cactus] Tomcat 5.x is stopping...
   [cactus] Tomcat 5.x is stopped

BUILD FAILED
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build.xml:750: 
The following error occurred while executing this line:
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/build.xml:731: 
The following error occurred while executing this line:
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/src/contrib/build.xml:48:
 The following error occurred while executing this line:
/grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-trunk/trunk/src/contrib/hdfsproxy/build.xml:343:
 Tests failed!

Total time: 61 minutes 19 seconds
[FINDBUGS] Skipping publisher since build result is FAILURE
Publishing Javadoc
Archiving artifacts
Recording test results
Recording fingerprints
Publishing Clover coverage report...
No Clover report will be published due to a Build Failure
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  org.apache.hadoop.hdfsproxy.TestAu

[jira] Created: (HDFS-1635) Pump up LAYOUT_VERSION in FSConstants.java for Federation before committing to trunk

[Tanping Wang (JIRA)]

Pump up LAYOUT_VERSION in FSConstants.java for Federation before committing to 
trunk


 Key: HDFS-1635
 URL: https://issues.apache.org/jira/browse/HDFS-1635
 Project: Hadoop HDFS
  Issue Type: New Feature
Affects Versions: Federation Branch
Reporter: Tanping Wang
 Fix For: Federation Branch


We need to pump up LAYOUT_VERSION for Federation release from current.  We will 
wait until before committing to trunk to avoid conflicting with other 
contributions.

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

[jira] Resolved: (HDFS-1632) HDFS Federation: data node storage structure changes and introduce block pool storage for Federation.

[Suresh Srinivas (JIRA)]

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

Suresh Srinivas resolved HDFS-1632.
---

  Resolution: Fixed
Hadoop Flags: [Reviewed]

I committed the patch. Thank you Tanping.

> HDFS Federation: data node storage structure changes and introduce block pool 
> storage for Federation. 
> --
>
> Key: HDFS-1632
> URL: https://issues.apache.org/jira/browse/HDFS-1632
> Project: Hadoop HDFS
>  Issue Type: New Feature
>  Components: data-node
>Affects Versions: Federation Branch
>Reporter: Tanping Wang
>Assignee: Tanping Wang
> Fix For: Federation Branch
>
> Attachments: Federation-upgrade.htm, HDFS-1632.patch
>
>
> In Federation, we introduced block pool into HDFS.  We are making changes to 
> data node storage and and block pool storage.

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

[jira] Created: (HDFS-1636) If dfs.name.dir points to an empty dir, namenode format shouldn't require confirmation

[Todd Lipcon (JIRA)]

If dfs.name.dir points to an empty dir, namenode format shouldn't require 
confirmation
--

 Key: HDFS-1636
 URL: https://issues.apache.org/jira/browse/HDFS-1636
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: name-node
Affects Versions: 0.23.0
Reporter: Todd Lipcon
Priority: Minor


Right now, running namenode -format when dfs.name.dir is configured to a dir 
which exists but is empty still asks for confirmation. This is unnecessary 
since it isn't blowing away any real data.

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

[jira] Created: (HDFS-1637) Federation: FSDataset in Datanode should be created after initial handshake with namenode

[Jitendra Nath Pandey (JIRA)]

Federation: FSDataset in Datanode should be created after initial handshake 
with namenode
-

 Key: HDFS-1637
 URL: https://issues.apache.org/jira/browse/HDFS-1637
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: Federation Branch
Reporter: Jitendra Nath Pandey
Assignee: Jitendra Nath Pandey
 Fix For: Federation Branch


Currently storage is initialized only after handshake with a namenode.However 
FSDataset is created before handshake and hence before storage initialization. 
At this time, storage does not have storage directories resulting in FSDataset 
initialized with no volumes.

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

[jira] Created: (HDFS-1638) DataNode.handleDiskError needs to inform ALL namenodes if a disk failed

[Boris Shkolnik (JIRA)]

DataNode.handleDiskError needs to inform ALL namenodes if a disk failed 


 Key: HDFS-1638
 URL: https://issues.apache.org/jira/browse/HDFS-1638
 Project: Hadoop HDFS
  Issue Type: Sub-task
Reporter: Boris Shkolnik
Assignee: Boris Shkolnik




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

[jira] Created: (HDFS-1639) Add block pool management to FSDataset.

[Suresh Srinivas (JIRA)]

Add block pool management to FSDataset.
---

 Key: HDFS-1639
 URL: https://issues.apache.org/jira/browse/HDFS-1639
 Project: Hadoop HDFS
  Issue Type: New Feature
  Components: data-node
Affects Versions: Federation Branch
Reporter: Suresh Srinivas
Assignee: Suresh Srinivas
 Fix For: Federation Branch


FSDataset needs to changes to add the notion of block pools. More description 
in comments.

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