[jira] [Created] (MAPREDUCE-3562) Concurrency issues in MultipleOutputs,JobControl,Counters

Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Teja Ch N V Assignee: Ravi Teja Ch N V bq.MultipleOutputs The close of recordwriters should be synchronized. public void close() throws IOException, InterruptedException { for (RecordWriter

[jira] [Created] (MAPREDUCE-3494) The RM should handle the graceful shutdown of the NM.

Components: nodemanager, resourcemanager Reporter: Ravi Teja Ch N V Instead of waiting for the NM expiry, RM should remove and handle the NM, which is shutdown gracefully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your

RE: 0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar?

I feel #4 as a better option. Regards, Ravi Teja -Original Message- From: Alejandro Abdelnur [mailto:t...@cloudera.com] Sent: Wednesday, October 12, 2011 9:38 PM To: common-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org Subject: 0.23 & trunk

RE: native compilation failing

Hi , A small correction Luke, the 'cbuild' profile is renamed to 'native' in MAPREDUCE-3014. I too ran into the same problem, I am using Suse Linux 11 automake 1.10.1 autoconf 2.63 Regards, Ravi Teja -Original Message- From: vic...@gmail.com [mailto:vic...@gma

RE: Lost task tracker reschedules all tasktracker's successful map tasks

to be re-executed. If reducer finishes, even if TT is down, no rescheduling is done, as final output is copied to the shared file system. Regards, Ravi Teja -Original Message- From: Leonardo Gamas [mailto:leoga...@jusbrasil.com.br] Sent: Monday, September 26, 2011 11:11 PM

[jira] [Created] (MAPREDUCE-3070) NM not able to register with RM after NM restart

: mrv2 Reporter: Ravi Teja Ch N V Priority: Blocker After stopping NM gracefully then starting NM, NM registration fails with RM with Duplicate registration from the node! error. {noformat} 2011-09-23 01:50:46,705 FATAL nodemanager.NodeManager (NodeManager.java:main(204

[jira] [Resolved] (MAPREDUCE-2912) Trunk build failing due to testcase failures from many builds

[ https://issues.apache.org/jira/browse/MAPREDUCE-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Teja Ch N V resolved MAPREDUCE-2912. - Resolution: Invalid The issue is no longer valid.The trunk is now passing

[jira] [Created] (MAPREDUCE-2949) NodeManager in a inconsistent state if a service startup fails.

Type: Bug Components: nodemanager Affects Versions: 0.24.0 Reporter: Ravi Teja Ch N V When a service startup fails at the Nodemanager, the Nodemanager JVM doesnot exit as the following threads are still running. Daemon Thread [Timer for 'NodeManager' metr

[jira] [Created] (MAPREDUCE-2912) Trunk build failing due to testcase failures from many builds

: Bug Components: build Affects Versions: 0.20.203.0 Reporter: Ravi Teja Ch N V run-test-mapred: BUILD FAILED /home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-trunk/trunk/hadoop-mapreduce-project/build.xml:848: Tests failed! Total time: 115 minutes 23 seconds

Re: Build failure in map reduce trunk

Hi Tharindu, I think it is trying to compile the native code. you can add -P-cbuild as argument to skip it, as mentioned earlier by Arun. Regards, Ravi Teja Thanks Praveen. I managed to proceed further. Now I'm stuck at this point. Appreciate if you can tell me what I'm d

Re: Build failure in map reduce trunk

Hi Tharindu, I think it is trying to compile the native code. you can add -P-cbuild as argument to skip it, as mentioned earlier by Arun. Regards, Ravi Teja Thanks Praveen. I managed to proceed further. Now I'm stuck at this point. Appreciate if you can tell me what I'm d

RE: Problem building yarn in trunk, which was working earlier.

Hi Ravi , I think that's the problem. The problem got resolved when I updated today. Thanks for the reply :) Regards, Ravi Teja *** This e-mail and attachments contain confidential information from H

Problem building yarn in trunk, which was working earlier.

; [Help 1] Regards, Ravi Teja

RE: trouble building MR-279 branch

anks and Regards, Ravi Teja -Original Message- From: Ravi Teja [mailto:ravit...@huawei.com] Sent: Thursday, July 28, 2011 5:09 PM To: 'mapreduce-dev@hadoop.apache.org' Subject: Re: trouble building MR-279 branch Hi, I have followed the procedure mentioned below, for building

Re: trouble building MR-279 branch

n\java\org\apache\hadoop\yarn\ap i\records\impl\pb\ContainerPBImpl.java:[23,33] package org.apache.commons.logging does not exist [ERROR] -> [Help 1] Regards, Ravi Teja -Original Message- From: Josh Wills [mailto:jwi...@cloudera.com] Sent: Saturday, July 02, 2011 6:34 AM To:

[jira] [Created] (MAPREDUCE-2632) Avoid calling the partitioner when the numReduceTasks is 1.

: Improvement Components: tasktracker Affects Versions: 0.23.0 Reporter: Ravi Teja Ch N V We can avoid the call to the partitioner when the number of reducers is 1.This will avoid the unnecessary computations by the partitioner. -- This message is automatically generated by

[jira] [Created] (MAPREDUCE-2631) Potential resource leaks in BinaryProtocol$TeeOutputStream.java and TaskLogServlet.java

Project: Hadoop Map/Reduce Issue Type: Bug Components: jobtracker Affects Versions: 0.23.0 Reporter: Ravi Teja Ch N V {code:title=TaskLogServlet.java|borderStyle=solid} private void printTaskLog(HttpServletResponse response

Reg ChainReducer usage

value pair can be passed or not to the next Mapper/Reducer. But why is this property significant, as only reducer is called at last in the chain, no matter whatever the order is in the chain and there is nothing to pass to. Regards, Ravi Teja