[jira] [Resolved] (MAPREDUCE-5721) RM occur exception while unregistering
[ https://issues.apache.org/jira/browse/MAPREDUCE-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved MAPREDUCE-5721. -- Resolution: Not a Problem Configuration issue. Resolving as 'not a problem'. RM occur exception while unregistering -- Key: MAPREDUCE-5721 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5721 Project: Hadoop Map/Reduce Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.0 Environment: rhel 5.8_x86 ;jrockit 1.6.0_31-R28.2.3-4.1.0;hadoop 2.2.0 Reporter: chillon_m when i run WORDCOUNT EXAMPLES,it occur. [hadoop@namenode0 ~]$ hadoop jar hadoop-2.2.0/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.2.0.jar wordcount /wordcount-input /wordcount-output 14/01/10 14:42:58 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 14/01/10 14:43:01 INFO client.RMProxy: Connecting to ResourceManager at namenode0/192.168.0.133:8032 14/01/10 14:43:03 INFO input.FileInputFormat: Total input paths to process : 2 14/01/10 14:43:03 INFO mapreduce.JobSubmitter: number of splits:2 14/01/10 14:43:03 INFO Configuration.deprecation: user.name is deprecated. Instead, use mapreduce.job.user.name 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.jar is deprecated. Instead, use mapreduce.job.jar 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.output.value.class is deprecated. Instead, use mapreduce.job.output.value.class 14/01/10 14:43:03 INFO Configuration.deprecation: mapreduce.combine.class is deprecated. Instead, use mapreduce.job.combine.class 14/01/10 14:43:03 INFO Configuration.deprecation: mapreduce.map.class is deprecated. Instead, use mapreduce.job.map.class 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.job.name is deprecated. Instead, use mapreduce.job.name 14/01/10 14:43:03 INFO Configuration.deprecation: mapreduce.reduce.class is deprecated. Instead, use mapreduce.job.reduce.class 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.input.dir is deprecated. Instead, use mapreduce.input.fileinputformat.inputdir 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.output.dir is deprecated. Instead, use mapreduce.output.fileoutputformat.outputdir 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.map.tasks is deprecated. Instead, use mapreduce.job.maps 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.output.key.class is deprecated. Instead, use mapreduce.job.output.key.class 14/01/10 14:43:03 INFO Configuration.deprecation: mapred.working.dir is deprecated. Instead, use mapreduce.job.working.dir 14/01/10 14:43:03 INFO mapreduce.JobSubmitter: Submitting tokens for job: job_1389336130986_0001 14/01/10 14:43:05 INFO impl.YarnClientImpl: Submitted application application_1389336130986_0001 to ResourceManager at namenode0/192.168.0.133:8032 14/01/10 14:43:05 INFO mapreduce.Job: The url to track the job: http://namenode0:8088/proxy/application_1389336130986_0001/ 14/01/10 14:43:05 INFO mapreduce.Job: Running job: job_1389336130986_0001 14/01/10 14:43:16 INFO mapreduce.Job: Job job_1389336130986_0001 running in uber mode : false 14/01/10 14:43:16 INFO mapreduce.Job: map 0% reduce 0% 14/01/10 14:44:20 INFO mapreduce.Job: map 50% reduce 0% 14/01/10 14:44:34 INFO mapreduce.Job: map 100% reduce 0% 14/01/10 14:44:51 INFO mapreduce.Job: map 100% reduce 100% 14/01/10 14:44:58 INFO ipc.Client: Retrying connect to server: datanode0.hadoop/192.168.0.134:43052. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1 SECONDS) 14/01/10 14:44:59 INFO ipc.Client: Retrying connect to server: datanode0.hadoop/192.168.0.134:43052. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1 SECONDS) 14/01/10 14:45:00 INFO ipc.Client: Retrying connect to server: datanode0.hadoop/192.168.0.134:43052. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1 SECONDS) 14/01/10 14:45:01 INFO ipc.Client: Retrying connect to server: datanode0.hadoop/192.168.0.134:43052. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1 SECONDS) 14/01/10 14:45:02 INFO ipc.Client: Retrying connect to server: datanode0.hadoop/192.168.0.134:43052. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1 SECONDS) 14/01/10 14:45:03 INFO ipc.Client: Retrying connect to server: datanode0.hadoop/192.168.0.134:43052. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1 SECONDS) 14/01/10 14:45:17 INFO mapreduce.Job: map 0% reduce 0%
[jira] [Commented] (MAPREDUCE-5083) MiniMRCluster should use a random component when creating an actual cluster
[ https://issues.apache.org/jira/browse/MAPREDUCE-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621193#comment-13621193 ] stack commented on MAPREDUCE-5083: -- Can we have this in 2.0.4-alpha? It was suggested by [~sseth] after he grokked how hbase runs its mapreduce unit tests. Thanks. MiniMRCluster should use a random component when creating an actual cluster --- Key: MAPREDUCE-5083 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5083 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 2.0.3-alpha Reporter: Siddharth Seth Assignee: Siddharth Seth Fix For: 2.0.5-beta Attachments: MAPREDUCE-5083-branch2.txt, MAPREDUCE-5083-trunk_2.txt, MAPREDUCE-5083-trunk.txt Currently all unit tests end up using the same work dir - which can affect anyone trying to run parallel instances. -- 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] [Commented] (MAPREDUCE-5083) MiniMRCluster should use a random component when creating an actual cluster
[ https://issues.apache.org/jira/browse/MAPREDUCE-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13621197#comment-13621197 ] stack commented on MAPREDUCE-5083: -- I will commit in a day or so unless someone does it before me or unless objection. Thanks. MiniMRCluster should use a random component when creating an actual cluster --- Key: MAPREDUCE-5083 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5083 Project: Hadoop Map/Reduce Issue Type: Bug Components: mrv2 Affects Versions: 2.0.3-alpha Reporter: Siddharth Seth Assignee: Siddharth Seth Fix For: 2.0.5-beta Attachments: MAPREDUCE-5083-branch2.txt, MAPREDUCE-5083-trunk_2.txt, MAPREDUCE-5083-trunk.txt Currently all unit tests end up using the same work dir - which can affect anyone trying to run parallel instances. -- 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] Commented: (MAPREDUCE-1352) 0.21.0 - snapshot incorrect dependency published in .pom files
[ https://issues.apache.org/jira/browse/MAPREDUCE-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796320#action_12796320 ] stack commented on MAPREDUCE-1352: -- Or, in case some one else wants to commit it: +1. 0.21.0 - snapshot incorrect dependency published in .pom files --- Key: MAPREDUCE-1352 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1352 Project: Hadoop Map/Reduce Issue Type: Task Components: build Affects Versions: 0.21.0 Reporter: Kay Kay Assignee: Giridharan Kesavan Priority: Critical Fix For: 0.21.0 Attachments: mapreduce-1352.patch The snapshot available here at - https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.21.0-SNAPSHOT/ , has an incorrect dependency specified for hadoop-core ( in the .pom file ). The source code ( in branch-0.21 ) refers to hadoop-core-0.21 in ivy/libaries.properties but pom.xml published in the repository refers to 0.22 . Please fix the same by republishing a .pom again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1352) 0.21.0 - snapshot incorrect dependency published in .pom files
[ https://issues.apache.org/jira/browse/MAPREDUCE-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796327#action_12796327 ] stack commented on MAPREDUCE-1352: -- Now I see that there were test failures too. 3 look to have been present before application of this patch. This failure might be related to this change: org.apache.hadoop.mapreduce.TestMRJobClient.testMissingProfileOutput . 0.21.0 - snapshot incorrect dependency published in .pom files --- Key: MAPREDUCE-1352 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1352 Project: Hadoop Map/Reduce Issue Type: Task Components: build Affects Versions: 0.21.0 Reporter: Kay Kay Assignee: Giridharan Kesavan Priority: Critical Fix For: 0.21.0 Attachments: mapreduce-1352.patch The snapshot available here at - https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-mapred/0.21.0-SNAPSHOT/ , has an incorrect dependency specified for hadoop-core ( in the .pom file ). The source code ( in branch-0.21 ) refers to hadoop-core-0.21 in ivy/libaries.properties but pom.xml published in the repository refers to 0.22 . Please fix the same by republishing a .pom again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
