[jira] [Resolved] (MAPREDUCE-4106) Fix skipping tests in mapreduce
[ https://issues.apache.org/jira/browse/MAPREDUCE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K resolved MAPREDUCE-4106. -- Resolution: Fixed Assignee: Devaraj K Fix skipping tests in mapreduce --- Key: MAPREDUCE-4106 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4106 Project: Hadoop Map/Reduce Issue Type: Test Components: mrv2 Affects Versions: 2.0.0-alpha, 3.0.0 Reporter: Devaraj K Assignee: Devaraj K There are 22 tests skipping in hadoop-mapreduce-client-jobclient module, all these can be corrected as part of this umbrella jira. -- 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] (MAPREDUCE-4078) Hadoop-Mapreduce-0.23-Build - Build # 239 - Still Failing
[
https://issues.apache.org/jira/browse/MAPREDUCE-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj K resolved MAPREDUCE-4078.
--
Resolution: Not A Problem
Hadoop-Mapreduce-0.23-Build - Build # 239 - Still Failing
--
Key: MAPREDUCE-4078
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4078
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 2.0.0-alpha
Reporter: Devaraj K
See https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/239/
{code:xml}
See https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/239/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
Building remotely on hadoop2 in workspace
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-0.23-Build
Location 'http://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.23'
does not exist
One or more repository locations do not exist anymore for
Hadoop-Mapreduce-0.23-Build, project will be disabled.
Retrying after 10 seconds
Location 'http://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.23'
does not exist
One or more repository locations do not exist anymore for
Hadoop-Mapreduce-0.23-Build, project will be disabled.
Retrying after 10 seconds
Location 'http://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.23'
does not exist
One or more repository locations do not exist anymore for
Hadoop-Mapreduce-0.23-Build, project will be disabled.
Archiving artifacts
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
{code}
--
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] (MAPREDUCE-4907) TrackerDistributedCacheManager issues too many getFileStatus calls
Sandy Ryza created MAPREDUCE-4907: - Summary: TrackerDistributedCacheManager issues too many getFileStatus calls Key: MAPREDUCE-4907 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4907 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv1, tasktracker Affects Versions: 1.1.1 Reporter: Sandy Ryza Assignee: Sandy Ryza TrackerDistributedCacheManager issues a number of redundant getFileStatus calls when determining the timestamps and visibilities of files in the distributed cache. 300 distributed cache files deep in the directory structure can hammer HDFS with a couple thousand requests. A couple optimizations can reduce this load: 1. determineTimestamps and determineCacheVisibilities both call getFileStatus on every file. We could cache the results of the former and use them for the latter. 2. determineCacheVisibilities needs to check that all ancestor directories of each file have execute permissions for everyone. This currently entails a getFileStatus on each ancestor directory for each file. The results of these getFileStatus calls could be cached as well. -- 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
