Isolation Runner not working as expected?

Hi, I would like to know if any one has used isolation runner for debugging? I have tried a lot but it is not at all working? My steps are as follows: 1. In the mapper function i have created an divided by zero exception. 2. In the hdfs-site.xml i have set the property keep.failed.task.files to

Setting up Hadoop in Eclipse

Hi list, I am having problems setting up Hadoop for Eclipse. I followed the instructions under: http://wiki.apache.org/hadoop/EclipseEnvironment Since I want to debug MapReduce jobs in distributed mode, I decided to check out common, hdfs and mapreduce from SVN. This leaves me with three differen

how to get each task's process?

hi,guys: I want to monitor each tasks' io usage, do can I get each task's process id? I used jvmManager.getPid(tip.getTaskRunner()); but it didn't seem to be the task's process. Thanks

Re: VOTE: Committing HADOOP-6949 to 0.22 branch

[bcc'ing hdfs-dev and mapreduce-dev] Konstantin, can you outline the effects of this incompatibility? Thx, Nige On Mar 28, 2011, at 10:19 PM, Dhruba Borthakur wrote: > This is a very effective optimization, +1 on pulling it to 0.22. > > -dhruba > > > On Mon, Mar 28, 2011 at 9:39 PM, Konstant

Re: VOTE: Committing HADOOP-6949 to 0.22 branch

good news. +1. On Tue, Mar 29, 2011 at 10:02 AM, Nigel Daley wrote: > [bcc'ing hdfs-dev and mapreduce-dev] > > Konstantin, can you outline the effects of this incompatibility? > > Thx, > Nige > > On Mar 28, 2011, at 10:19 PM, Dhruba Borthakur wrote: > > > This is a very effective optimization, +

Re: Isolation Runner not working as expected?

Hello, Which Hadoop version are you using? On Tue, Mar 29, 2011 at 7:03 PM, som_shekhar wrote: > Now as per the documentation i ran the isolation runner: > bin/hadoop org.apache.hadoop.mapred.IsolationRunner ../job.xml > > But it throws me class not found exception. So i checked the class path,

Re: VOTE: Committing HADOOP-6949 to 0.22 branch

+1 n.b. that the vote lost hdfs and common dev at some point. I've added them back. On Tue, Mar 29, 2011 at 9:18 AM, Amit Sangroya wrote: > +1 > > On Tue, Mar 29, 2011 at 6:04 PM, Stephen Boesch wrote: >> +1 >> >> 2011/3/29 Doug Cutting >> >>> +1 >>> >>> I don't think this creates an incompati

[jira] [Created] (HADOOP-7212) Reuse connection

Reuse connection Key: HADOOP-7212 URL: https://issues.apache.org/jira/browse/HADOOP-7212 Project: Hadoop Common Issue Type: Bug Components: ipc Reporter: Hairong Kuang Assignee: Hairong Kuan

Re: VOTE: Committing HADOOP-6949 to 0.22 branch

Nigel, The nature of incompatibility is that the RPC version is changing, which means VersionedProtocol-s become incompatible all at once. As opposed to say only DatanodeProtocol or mr.ClientProtocol. Doug is right because of our strict requirements for protocol compatibility this will not affect

[jira] [Resolved] (HADOOP-7212) Reuse connection

[ https://issues.apache.org/jira/browse/HADOOP-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang resolved HADOOP-7212. --- Resolution: Invalid Just found out that the regression was introduced to only our internal b