[jira] [Created] (MAPREDUCE-3481) [Gridmix] Improve STRESS mode locking
[Gridmix] Improve STRESS mode locking - Key: MAPREDUCE-3481 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3481 Project: Hadoop Map/Reduce Issue Type: Improvement Components: contrib/gridmix Affects Versions: 0.24.0 Reporter: Amar Kamat Assignee: Amar Kamat Fix For: 0.24.0 Gridmix STREES mode code doesnt sufficiently load the cluster due to improper locking. -- 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
Hadoop-Mapreduce-0.23-Build - Build # 108 - Still Failing
See https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/108/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 22550 lines...]
[ivy:resolve] org.slf4j#slf4j-api;1.5.11 by [org.slf4j#slf4j-api;1.6.1] in
[common]
[ivy:resolve] org.slf4j#slf4j-log4j12;1.5.11 by
[org.slf4j#slf4j-log4j12;1.6.1] in [common]
[ivy:resolve] junit#junit;4.8.1 by [junit#junit;4.8.2] in [common]
[ivy:resolve] org.jboss.netty#netty;3.2.3.Final by
[org.jboss.netty#netty;3.2.4.Final] in [common]
[ivy:resolve] commons-codec#commons-codec;${commons-codec.version} by
[commons-codec#commons-codec;1.4] in [common]
[ivy:resolve] org.mortbay.jetty#jetty;6.1.14 by
[org.mortbay.jetty#jetty;6.1.26] in [common]
[ivy:resolve] org.mortbay.jetty#jetty-util;6.1.14 by
[org.mortbay.jetty#jetty-util;6.1.26] in [common]
[ivy:resolve] org.apache.avro#avro;1.5.2 by [org.apache.avro#avro;1.5.3] in
[common]
[ivy:resolve] org.codehaus.jackson#jackson-mapper-asl;${jackson.version} by
[org.codehaus.jackson#jackson-mapper-asl;1.7.1] in [common]
[ivy:resolve] org.codehaus.jackson#jackson-core-asl;${jackson.version} by
[org.codehaus.jackson#jackson-core-asl;1.7.1] in [common]
[ivy:resolve] com.thoughtworks.paranamer#paranamer;2.2 by
[com.thoughtworks.paranamer#paranamer;2.3] in [common]
-
| |modules|| artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
-
| common | 83 | 4 | 4 | 12 || 71 | 4 |
-
ivy-retrieve-common:
[ivy:retrieve] :: retrieving :: org.apache.hadoop#gridmix [sync]
[ivy:retrieve] confs: [common]
[ivy:retrieve] 71 artifacts copied, 0 already retrieved (37968kB/145ms)
[ivy:cachepath] DEPRECATED: 'ivy.conf.file' is deprecated, use
'ivy.settings.file' instead
[ivy:cachepath] :: loading settings :: file =
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-0.23-Build/trunk/hadoop-mapreduce-project/ivy/ivysettings.xml
compile:
[echo] contrib: gridmix
[javac] Compiling 44 source files to
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-0.23-Build/trunk/hadoop-mapreduce-project/build/contrib/gridmix/classes
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
jar:
[echo] contrib: gridmix
[jar] Building jar:
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-0.23-Build/trunk/hadoop-mapreduce-project/build/contrib/gridmix/hadoop-0.23.1-SNAPSHOT-gridmix.jar
BUILD SUCCESSFUL
Total time: 29 seconds
+ RESULT=0
+ [[ 0 -ne 0 ]]
+ gunzip
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-0.23-Build/trunk/hadoop-mapreduce-project/target/hadoop-mapreduce-0.23.0-SNAPSHOT.tar.gz
gzip:
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-0.23-Build/trunk/hadoop-mapreduce-project/target/hadoop-mapreduce-0.23.0-SNAPSHOT.tar.gz:
No such file or directory
+ RESULT=1
+ [[ 1 -ne 0 ]]
+ echo 'gunzip failed'
gunzip failed
+ exit 1
Build step 'Execute shell' marked build as failure
Archiving artifacts
Updating HDFS-2596
Updating HADOOP-7863
Updating HADOOP-
Updating MAPREDUCE-3465
Updating HADOOP-7424
Updating MAPREDUCE-3045
Updating MAPREDUCE-3433
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
[jira] [Created] (MAPREDUCE-3482) Enable HTTP proxy to be specified for job end notification
Enable HTTP proxy to be specified for job end notification
--
Key: MAPREDUCE-3482
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3482
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: applicationmaster, mrv2
Affects Versions: 0.23.0
Reporter: Ravi Prakash
Courtesy Ratandeep Singh Ratti
{quote}
The AM should be able to notify the job.end.notification.url. Hence this
request has to go through HTTP proxy, since ACLs won't be open from the AM to
external machines.
{quote}
--
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
[jira] [Resolved] (MAPREDUCE-3482) Enable HTTP proxy to be specified for job end notification
[
https://issues.apache.org/jira/browse/MAPREDUCE-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash resolved MAPREDUCE-3482.
-
Resolution: Duplicate
This is a duplicate of MAPREDUCE-3382
Enable HTTP proxy to be specified for job end notification
--
Key: MAPREDUCE-3482
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3482
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: applicationmaster, mrv2
Affects Versions: 0.23.0
Reporter: Ravi Prakash
Assignee: Anupam Seth
Courtesy Ratandeep Singh Ratti
{quote}
The AM should be able to notify the job.end.notification.url. Hence this
request has to go through HTTP proxy, since ACLs won't be open from the AM to
external machines.
{quote}
--
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
[jira] [Resolved] (MAPREDUCE-3480) TestJvmReuse fails in 1.0
[ https://issues.apache.org/jira/browse/MAPREDUCE-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey resolved MAPREDUCE-3480. - Resolution: Fixed Hadoop Flags: Reviewed Marking it as fixed. The test should not be disabled in trunk to keep it in the radar. TestJvmReuse fails in 1.0 - Key: MAPREDUCE-3480 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3480 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Jitendra Nath Pandey Assignee: Jitendra Nath Pandey Attachments: MAPREDUCE-3480-branch-1.patch TestJvmReuse is failing in apache builds, although it passes in my local machine. -- 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
[jira] [Created] (MAPREDUCE-3483) CapacityScheduler reserves container on same node as AM but can't ever use due to never enough avail memory
CapacityScheduler reserves container on same node as AM but can't ever use due to never enough avail memory --- Key: MAPREDUCE-3483 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3483 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0 Reporter: Thomas Graves Priority: Blocker Saw a case where a job was stuck trying to get reducers. The issue is the capacity scheduler reserved a container on the same node as the application master but there wasn't ever enough memory to run the reducer on that node. Node total memory was 8G, Reducer needed 8G, AM was using 2G. This particular job had 10 reducers and it was stuck waiting on the one because the AM + reserved reducer memory was already over the queue limit. -- 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
[jira] [Created] (MAPREDUCE-3484) Job end notification method should be called before stop() in handle(JobFinishEvent)
Job end notification method should be called before stop() in handle(JobFinishEvent) Key: MAPREDUCE-3484 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3484 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am, mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash We noticed JobEndNotifier was getting an InterruptedException before completing all its retries. -- 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
[jira] [Created] (MAPREDUCE-3485) DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS
DISKS_FAILED -101 error code should be defined in same location as ABORTED_CONTAINER_EXIT_STATUS Key: MAPREDUCE-3485 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3485 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 0.23.0, 0.24.0 Reporter: Hitesh Shah Fix For: 0.23.1 With MAPREDUCE-3121, it is defined in ContainerExecutor as part of yarn-nodemanager which would be a problem for client-side code if it needs to understand the exit code. A short term fix would be to move it into YarnConfiguration where ABORTED_CONTAINER_EXIT_STATUS is defined. A longer term fix would be to find a more formal and extensible approach for new yarn framework error codes to be added and be easily accessible to client-side code or other AMs. -- 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
[jira] [Resolved] (MAPREDUCE-2951) Problem while building hadoop trunk on Windows 7
[
https://issues.apache.org/jira/browse/MAPREDUCE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhijit Suresh Shingate resolved MAPREDUCE-2951.
Resolution: Invalid
Issue is no longer happening.
Hence invalidating it.
Problem while building hadoop trunk on Windows 7
Key: MAPREDUCE-2951
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2951
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: build, mrv2
Affects Versions: 0.23.0, 0.24.0
Environment: Windows 7
Cygwin-1.7
apache-maven-3.0.3
java version 1.6.0_17
Reporter: Abhijit Suresh Shingate
Hi All,
I am facing problem with generating tar files for all hadoop modbles.
The generated tar files are not correct.
For example, for hadoop-common-0.24.0-SNAPSHOT.tar.gz file/bin folder is
missing all sh files.
Because of this i am not able to launch hdfs or mapreduce.
To generate the tar file i used following command
*mvn package -Pdist -Dtar -DskipTests -P-cbuild
-Dcommons.daemon.os.name=linux -Dcommons.daemon.os.arch=i686 -X*
I am not maven expert but following is the part of the debug information
generated by above command talks about excluding *.sh file from assembly.
[DEBUG] (s) siteDirectory =
D:\iSAP\Hadoop\SVN\trunk\hadoop-common-project\hadoop-common\target\site
[DEBUG] (f) skipAssembly = false
[DEBUG] (s) tarLongFileMode = warn
[DEBUG] (s) tempRoot =
D:\iSAP\Hadoop\SVN\trunk\hadoop-common-project\hadoop-common\target\archive-tmp
[DEBUG] (s) workDirectory =
D:\iSAP\Hadoop\SVN\trunk\hadoop-common-project\hadoop-common\target\assembly\work
[DEBUG] -- end configuration --
[DEBUG] Before assembly is interpolated:
?xml version=1.0 encoding=UTF-8?assembly
idhadoop-distro/id
formats
formatdir/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
fileSets
fileSet
directory${basedir}/src/main/bin/directory
outputDirectory/bin/outputDirectory
excludes
exclude*.sh/exclude
/excludes
fileMode0755/fileMode
/fileSet
Anyone has any idea about this?
Thanks Regards,
Abhijit
--
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
