Jenkins build is back to normal : Hadoop-Hdfs-0.23-Build #466

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1257/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 9749 lines...]
Running org.apache.hadoop.hdfs.web.TestFSMainOperationsWebHdfs
Tests run: 49, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.093 sec
Running org.apache.hadoop.hdfs.web.resources.TestParam
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.496 sec
Running org.apache.hadoop.hdfs.web.TestWebHdfsWithMultipleNameNodes
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.59 sec
Running org.apache.hadoop.hdfs.web.TestOffsetUrlInputStream
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.163 sec
Running org.apache.hadoop.hdfs.web.TestWebHDFS
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 309.079 sec
Running org.apache.hadoop.hdfs.web.TestWebHdfsUrl
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.103 sec
Running org.apache.hadoop.hdfs.web.TestJsonUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.167 sec
Running org.apache.hadoop.hdfs.web.TestAuthFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.381 sec
Running org.apache.hadoop.hdfs.TestConnCache
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.567 sec
Running org.apache.hadoop.hdfs.TestDFSClientRetries
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 127.489 sec
Running org.apache.hadoop.hdfs.TestListPathServlet
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.134 sec
Running org.apache.hadoop.hdfs.TestDFSStorageStateRecovery
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 118.316 sec
Running org.apache.hadoop.hdfs.TestFileCreationEmpty
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.027 sec
Running org.apache.hadoop.hdfs.TestSetrepIncreasing

Results :

Tests run: 1112, Failures: 0, Errors: 0, Skipped: 5

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop HDFS  FAILURE 
[1:38:46.149s]
[INFO] Apache Hadoop HttpFS .. SKIPPED
[INFO] Apache Hadoop HDFS BookKeeper Journal . SKIPPED
[INFO] Apache Hadoop HDFS Project  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1:38:46.928s
[INFO] Finished at: Mon Dec 17 13:14:36 UTC 2012
[INFO] Final Memory: 39M/670M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on 
project hadoop-hdfs: ExecutionException; nested exception is 
java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked 
VM terminated without saying properly goodbye. VM crash or System.exit called ? 
-> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Build step 'Execute shell' marked build as failure
Archiving artifacts
Updating HDFS-4315
Sending e-mails to: hdfs-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Build failed in Jenkins: Hadoop-Hdfs-trunk #1257

[Apache Jenkins Server]

See 

Changes:

[atm] HDFS-4315. DNs with multiple BPs can have BPOfferServices fail to start 
due to unsynchronized map access. Contributed by Aaron T. Myers.

--
[...truncated 9556 lines...]
Running org.apache.hadoop.hdfs.server.namenode.ha.TestFailureToReadEdits
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.534 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestHAStateTransitions
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 55.942 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestDFSUpgradeWithHA
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.962 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestDFSZKFailoverController
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.912 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestGetGroupsWithHA
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.026 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestStateTransitionFailure
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.343 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestInitializeSharedEdits
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.951 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestDNFencingWithReplication
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 52.343 sec
Running org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 104.678 sec
Running org.apache.hadoop.hdfs.server.namenode.TestTransferFsImage
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.73 sec
Running org.apache.hadoop.hdfs.server.namenode.TestProcessCorruptBlocks
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.56 sec
Running org.apache.hadoop.hdfs.server.namenode.TestAllowFormat
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.184 sec
Running org.apache.hadoop.hdfs.server.namenode.TestEditLog
Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.521 sec
Running 
org.apache.hadoop.hdfs.server.namenode.web.resources.TestWebHdfsDataLocality
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.227 sec
Running org.apache.hadoop.hdfs.server.namenode.TestEditsDoubleBuffer
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 sec
Running org.apache.hadoop.hdfs.server.namenode.TestValidateConfigurationSettings
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.137 sec
Running org.apache.hadoop.hdfs.server.namenode.TestGetImageServlet
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.714 sec
Running org.apache.hadoop.hdfs.server.namenode.TestParallelImageWrite
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.07 sec
Running org.apache.hadoop.hdfs.server.namenode.TestFSDirectory
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.804 sec
Running org.apache.hadoop.hdfs.server.namenode.TestLargeDirectoryDelete
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.744 sec
Running org.apache.hadoop.hdfs.server.namenode.TestFileLimit
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.742 sec
Running org.apache.hadoop.hdfs.server.namenode.TestNNStorageRetentionFunctional
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.974 sec
Running org.apache.hadoop.hdfs.server.namenode.TestNameCache
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.132 sec
Running org.apache.hadoop.hdfs.server.namenode.TestNNStorageRetentionManager
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.9 sec
Running org.apache.hadoop.hdfs.server.namenode.TestNameNodeResourcePolicy
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.281 sec
Running org.apache.hadoop.hdfs.server.namenode.TestCorruptFilesJsp
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.045 sec
Running org.apache.hadoop.hdfs.server.namenode.TestDeadDatanode
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.857 sec
Running org.apache.hadoop.hdfs.server.namenode.TestFSImageStorageInspector
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.335 sec
Running org.apache.hadoop.hdfs.server.namenode.TestFsck
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.342 sec
Running org.apache.hadoop.hdfs.server.namenode.TestGenericJournalConf
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.827 sec
Running org.apache.hadoop.hdfs.server.namenode.TestSecureNameNodeWithExternalKdc
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.066 sec
Running org.apache.hadoop.hdfs.server.namenode.TestSaveNamespace
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.051 sec
Running org.apache.hadoop.hdfs.server.namenode.TestSec

[jira] [Created] (HDFS-4319) FSShell copyToLocal creates files with the executable bit set

[Colin Patrick McCabe (JIRA)]

Colin Patrick McCabe created HDFS-4319:
--

 Summary: FSShell copyToLocal creates files with the executable bit 
set
 Key: HDFS-4319
 URL: https://issues.apache.org/jira/browse/HDFS-4319
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 2.0.3-alpha
Reporter: Colin Patrick McCabe
Priority: Minor


With the default value of {{fs.permissions.umask-mode}}, {{022}},  {{FSShell 
copyToLocal}} creates files with the executable bit set.

If, on the other hand, you change {{fs.permissions.umask-mode}} to something 
like {{133}}, you encounter a different problem.  When you use {{copyToLocal}} 
to create directories, they don't have the executable bit set, meaning they do 
not have search permission.

Since HDFS doesn't allow the executable bit to be set on files, it seems 
illogical to add it in when using {{copyToLocal}}.  This is also a regression, 
since branch 1 did not have this problem.

--
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] [Created] (HDFS-4320) NameNode tries to get its address by looking at fs.default.name instead of its own config keys

[Mostafa Elhemali (JIRA)]

Mostafa Elhemali created HDFS-4320:
--

 Summary: NameNode tries to get its address by looking at 
fs.default.name instead of its own config keys
 Key: HDFS-4320
 URL: https://issues.apache.org/jira/browse/HDFS-4320
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Mostafa Elhemali


When NameNode starts up, it tries to find out its address by looking at the 
fs.default.name configuration key instead of using its own keys (namely 
dfs.namenode.servicerpc-address). This breaks scenarios where we try to 
configure a Hadoop cluster that uses a different default file system than DFS, 
but still try to prop up namenode and datanode services as a secondary file 
system.

--
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] [Resolved] (HDFS-4241) DataNode unit test failures on Windows

[Arpit Agarwal (JIRA)]

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

Arpit Agarwal resolved HDFS-4241.
-

Resolution: Fixed

DataNode test failures are no longer reproducible on Windows as of 12/17/2012.

It is likely that some of [~cnauroth]'s fixes have fixed these failures. I am 
resolving this issue.

> DataNode unit test failures on Windows
> --
>
> Key: HDFS-4241
> URL: https://issues.apache.org/jira/browse/HDFS-4241
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: hdfs-client
>Affects Versions: trunk-win
>Reporter: Arpit Agarwal
>Assignee: Arpit Agarwal
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>


--
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] [Created] (HDFS-4321) FileSystem class should override .equals(Object)

[Thejas M Nair (JIRA)]

Thejas M Nair created HDFS-4321:
---

 Summary: FileSystem class should override .equals(Object)
 Key: HDFS-4321
 URL: https://issues.apache.org/jira/browse/HDFS-4321
 Project: Hadoop HDFS
  Issue Type: Improvement
Affects Versions: 1.1.1
Reporter: Thejas M Nair


The FileSystem class has a notion of equality, based on the uri. The class 
should override .equal(Object) so that it returns true if FileSystem objects 
are logically same. 
This is useful when FileSystem cache is disabled, as FileSystem.get(..) will 
return new object each time.


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