[jira] [Commented] (MAPREDUCE-3772) MultipleOutputs output lost if baseOutputPath starts with ../

2012-12-01 Thread Alejandro Abdelnur (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508169#comment-13508169
 ] 

Alejandro Abdelnur commented on MAPREDUCE-3772:
---

Radim, if you have speculative execution enabled, any file written by 
MultipleOutputs outside of the output dir of the job (where the temp dir 
mechanism for output files of tasks is not in place) is at risk of having 
incomplete data.

> MultipleOutputs output lost if baseOutputPath starts with ../
> -
>
> Key: MAPREDUCE-3772
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3772
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: client
>Affects Versions: 0.20.2
>Reporter: Radim Kolar
>Assignee: Harsh J
> Attachments: MAPREDUCE-3772.patch
>
>
> Lets say you have output directory set:
> FileOutputFormat.setOutputPath(job, "/tmp/multi1/out");
> and want to place output from MultipleOutputs into /tmp/multi1/extra
> I expect following code to work:
> mos = new MultipleOutputs(context);
> mos.write(new Text("zrr"), value, "../extra/");
> but no Exception is throw and expected output directory /tmp/multi1/extra 
> does not even exists. All data written to this output vanish without trace.
> To make it work fullpath must be used
> mos.write(new Text("zrr"), value, "/tmp/multi1/extra/");
> Output is listed in statistics from MultipleOutputs correctly:
> org.apache.hadoop.mapreduce.lib.output.MultipleOutputs
> ../gaja1/=1 (* everything is lost *)
> /tmp/multi1/out/../ksd34/=1 (* this using full path works 
> *)
> list1=6667

--
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-2257) distcp can copy blocks in parallel

2012-12-01 Thread Harsh J (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508168#comment-13508168
 ] 

Harsh J commented on MAPREDUCE-2257:


[~mithun] - I know its been a while, but are you still working on this?

Since HDFS-222 is getting some attention, I feel it would be good to have this 
as an inbuilt usage of the same (and since Dhruba has already mentioned it is a 
great improvement to DistCp).

> distcp can copy blocks in parallel
> --
>
> Key: MAPREDUCE-2257
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2257
> Project: Hadoop Map/Reduce
>  Issue Type: Improvement
>  Components: distcp
>Affects Versions: 0.21.0
>Reporter: dhruba borthakur
>Assignee: Mithun Radhakrishnan
> Attachments: MAPREDUCE-2257.patch
>
>
> The minimum unit of work for a distcp task is a file. We have files that are 
> greater than 1 TB with a block size of  1 GB. If we use distcp to copy these 
> files, the tasks either take a long long long time or finally fails. A better 
> way for distcp would be to copy all the source blocks in parallel, and then 
> stich the blocks back to files at the destination via the HDFS Concat API 
> (HDFS-222)

--
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-1347) Missing synchronization in MultipleOutputFormat

2012-12-01 Thread Harsh J (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508167#comment-13508167
 ] 

Harsh J commented on MAPREDUCE-1347:


Patch still applies cleanly to trunk. Any further comments atop jenkins' +1?

> Missing synchronization in MultipleOutputFormat
> ---
>
> Key: MAPREDUCE-1347
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1347
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: client
>Affects Versions: 1.0.0
>Reporter: Todd Lipcon
>Assignee: Harsh J
>  Labels: concurrency
> Attachments: MAPREDUCE-1347.r10.diff, mapreduce.1347.r1.diff, 
> MAPREDUCE-1347.r2.diff, MAPREDUCE-1347.r3.diff, MAPREDUCE-1347.r4.diff, 
> MAPREDUCE-1347.r5.diff, MAPREDUCE-1347.r6.diff, MAPREDUCE-1347.r7.diff, 
> MAPREDUCE-1347.r8.diff, MAPREDUCE-1347.r9.diff
>
>
> MultipleOutputFormat's RecordWriter implementation doesn't use 
> synchronization when accessing the recordWriters member. When using 
> multithreaded mappers or reducers, this can result in problems where two 
> threads will both try to create the same file, causing 
> AlreadyBeingCreatedException. Doing this more fine-grained than just 
> synchronizing the whole method is probably a good idea, so that multithreaded 
> mappers can actually achieve parallelism writing into separate output streams.
> From what I can tell, the new API's MultipleOutputs seems not to have this 
> issue.

--
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-4172) Clean up java warnings in the hadoop-mapreduce-project sub projects

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4172.


Resolution: Won't Fix

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

> Clean up java warnings in the hadoop-mapreduce-project sub projects
> ---
>
> Key: MAPREDUCE-4172
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4172
> Project: Hadoop Map/Reduce
>  Issue Type: Task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>
> There are lots of warnings in the hadoop-mapreduce-project presently. We can 
> clear almost all of this away:
> * Unused imports
> * Unused variables
> ** For loops that can be replaced with while instead to save an unused 
> variable
> * Unused methods
> * Deprecation warnings where an alternative can be used (Especially 
> SequenceFile reader/writer usage and MiniDFSCluster usage)
> * Deprecation warnings where an alternative isn't clear (Especially 
> MiniMRCluster usage and DistributedCache API usage where a Job object may not 
> be available)
> * Unchecked conversions
> * Raw type usage
> * (etc.)
> I'm going to open one sub-task per sub-project we have, with patches attached 
> to them.

--
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-4173) Clean up hadoop-mapreduce-client-app

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4173.


Resolution: Won't Fix

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up hadoop-mapreduce-client-app
> 
>
> Key: MAPREDUCE-4173
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4173
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0001-MR-Client-App-Cleanup.patch, 
> 0001-MR-Client-App-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-mapreduce-client-app 
> module.

--
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-4174) Clean up hadoop-mapreduce-client-common

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4174.


Resolution: Won't Fix

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up hadoop-mapreduce-client-common
> ---
>
> Key: MAPREDUCE-4174
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4174
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0002-MR-Client-Common-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-mapreduce-client-common 
> module.

--
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-4175) Clean up hadoop-mapreduce-client-core

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4175.


Resolution: Won't Fix

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up hadoop-mapreduce-client-core
> -
>
> Key: MAPREDUCE-4175
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4175
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0003-MapReduce-Client-Core-Cleanup.patch, 
> 0003-MapReduce-Client-Core-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-mapreduce-client-core 
> module.

--
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] [Updated] (MAPREDUCE-4177) Clean up hadoop-mapreduce-client-jobclient

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4177:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up hadoop-mapreduce-client-jobclient
> --
>
> Key: MAPREDUCE-4177
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4177
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0005-MapReduce-Client-JobClient-Cleanup.patch, 
> 0005-MapReduce-Client-JobClient-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in 
> hadoop-mapreduce-client-jobclient module.

--
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-4176) Clean up hadoop-mapreduce-client-hs

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4176.


Resolution: Won't Fix

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up hadoop-mapreduce-client-hs
> ---
>
> Key: MAPREDUCE-4176
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4176
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0004-MapReduce-Client-HistoryServer-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-mapreduce-client-hs 
> module.

--
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] [Updated] (MAPREDUCE-4181) Remove the unused maybeInitBuilder() method from various classes in hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4181:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Remove the unused maybeInitBuilder() method from various classes in 
> hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-api/
> -
>
> Key: MAPREDUCE-4181
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4181
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0009-YARN-API-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-yarn-api module.

--
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] [Updated] (MAPREDUCE-4179) Clean up hadoop-mapreduce-examples

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4179:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up hadoop-mapreduce-examples
> --
>
> Key: MAPREDUCE-4179
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4179
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0006-MapReduce-Examples-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-mapreduce-examples 
> module.

--
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-4182) Remove an used import from TestDistributedShell

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4182.


Resolution: Won't Fix

Setting proper resolution.

> Remove an used import from TestDistributedShell
> ---
>
> Key: MAPREDUCE-4182
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4182
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 
> 0010-YARN-Applications-DistributedShell-Example-Cleanup.patch, 
> 0010-YARN-Applications-DistributedShell-Example-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in 
> hadoop-yarn-applications-distributedshell module.

--
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] [Reopened] (MAPREDUCE-4182) Remove an used import from TestDistributedShell

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J reopened MAPREDUCE-4182:



> Remove an used import from TestDistributedShell
> ---
>
> Key: MAPREDUCE-4182
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4182
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 
> 0010-YARN-Applications-DistributedShell-Example-Cleanup.patch, 
> 0010-YARN-Applications-DistributedShell-Example-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in 
> hadoop-yarn-applications-distributedshell module.

--
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-4183) Clean up yarn-common

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-4183.


Resolution: Won't Fix

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up yarn-common
> 
>
> Key: MAPREDUCE-4183
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4183
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0011-YARN-Common-Cleanup.patch, 
> 0011-YARN-Common-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-yarn-common module.

--
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] [Updated] (MAPREDUCE-4184) Clean up yarn-server-common

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4184:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up yarn-server-common
> ---
>
> Key: MAPREDUCE-4184
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4184
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0012-YARN-Server-Common-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-yarn-server-common 
> module.

--
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] [Updated] (MAPREDUCE-4182) Remove an used import from TestDistributedShell

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4182:
---

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Remove an used import from TestDistributedShell
> ---
>
> Key: MAPREDUCE-4182
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4182
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 
> 0010-YARN-Applications-DistributedShell-Example-Cleanup.patch, 
> 0010-YARN-Applications-DistributedShell-Example-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in 
> hadoop-yarn-applications-distributedshell module.

--
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] [Updated] (MAPREDUCE-4186) Clean up yarn-server-resourcemanager

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4186:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up yarn-server-resourcemanager
> 
>
> Key: MAPREDUCE-4186
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4186
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0014-YARN-Server-ResourceManager-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in 
> hadoop-yarn-server-resourcemanager module.

--
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] [Updated] (MAPREDUCE-4185) Clean up yarn-server-nodemanager

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4185:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up yarn-server-nodemanager
> 
>
> Key: MAPREDUCE-4185
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4185
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0013-YARN-Server-NodeManager-Cleanup.patch, 
> 0013-YARN-Server-NodeManager-Cleanup.patch, 
> 0013-YARN-Server-NodeManager-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-yarn-server-nodemanager 
> module.

--
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] [Updated] (MAPREDUCE-4187) Clean up yarn-server-tests

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4187:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up yarn-server-tests
> --
>
> Key: MAPREDUCE-4187
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4187
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0015-YARN-Server-Tests-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-yarn-server-tests 
> module.

--
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] [Updated] (MAPREDUCE-4188) Clean up yarn-server-web-proxy

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4188:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Patches were too broad and have gone stale. Will address these forms of issue 
over separate, smaller and more divided JIRAs in future.

Closing out parent JIRA MAPREDUCE-4172, and hence closing out this.

> Clean up yarn-server-web-proxy
> --
>
> Key: MAPREDUCE-4188
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4188
> Project: Hadoop Map/Reduce
>  Issue Type: Sub-task
>  Components: build
>Affects Versions: trunk
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Minor
> Attachments: 0016-YARN-Server-Web-Proxy-Cleanup.patch
>
>
> Clean up a bunch of existing javac warnings in hadoop-yarn-server-web-proxy 
> module.

--
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] [Updated] (MAPREDUCE-4324) JobClient can perhaps set mapreduce.job.credentials.binary rather than expect its presence?

2012-12-01 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-4324:
---

Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

Doing this would break (or be defunct due to) MAPREDUCE-3727 I think. Resolving 
as Won't Fix at this point.

Users should continue manually configuring this.

> JobClient can perhaps set mapreduce.job.credentials.binary rather than expect 
> its presence?
> ---
>
> Key: MAPREDUCE-4324
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4324
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: mrv1, mrv2, security
>Affects Versions: 0.22.0, 2.0.0-alpha
>Reporter: Harsh J
>Assignee: Harsh J
> Attachments: MAPREDUCE-4324.patch
>
>
> HDFS-1007 added in this requirement property 
> "mapreduce.job.credentials.binary", that has lead Oozie to add the following 
> duplicate snippet to all its Job-launching main classes such as the Pig, 
> Hive, MR and Sqoop actions:
> {code}
> if (System.getenv("HADOOP_TOKEN_FILE_LOCATION") != null) {
> jobConf.set("mapreduce.job.credentials.binary", 
> System.getenv("HADOOP_TOKEN_FILE_LOCATION"));
> }
> {code}
> Same is required for any client program that launches a job from within a 
> task.
> Why can't this simply be set by the JobClient initialization bits itself? If 
> no one imagines it causing issues, I'd like to add this snippet somewhere in 
> JobSubmitter before it requests NN/JT, as otherwise we'd get…
> {code}
> org.apache.hadoop.ipc.RemoteException: java.io.IOException: Delegation Token 
> can be issued only with kerberos or web authentication 
> at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getDelegationToken(FSNamesystem.java:5509)
>  
> at 
> org.apache.hadoop.hdfs.server.namenode.NameNode.getDelegationToken(NameNode.java:536)
>  
> at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  
> at java.lang.reflect.Method.invoke(Method.java:597) 
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:557) 
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1434) 
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1430) 
> at java.security.AccessController.doPrivileged(Native Method) 
> at javax.security.auth.Subject.doAs(Subject.java:396) 
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1157)
>  
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1428)
> at org.apache.hadoop.ipc.Client.call(Client.java:1107) 
> at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:226) 
> at $Proxy6.getDelegationToken(Unknown Source) 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  
> at java.lang.reflect.Method.invoke(Method.java:597) 
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:82)
>  
> at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:59)
>  
> at $Proxy6.getDelegationToken(Unknown Source) 
> at org.apache.hadoop.hdfs.DFSClient.getDelegationToken(DFSClient.java:331) 
> at 
> org.apache.hadoop.hdfs.DistributedFileSystem.getDelegationToken(DistributedFileSystem.java:605)
>  
> at 
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:115)
>  
> at 
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:79)
>  
> at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:851) 
> at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:833) 
> at java.security.AccessController.doPrivileged(Native Method) 
> at javax.security.auth.Subject.doAs(Subject.java:396) 
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1157)
>  
> at org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:833) 
> at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:807) 
> at org.apache.hadoop.mapred.JobClient.runJob(JobClient.java:1242) 
> {code}
> … or similar errors when a user submits a job from a task running in a 
> secured cluster.
> Let me know your thoughts on this!

--
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-4798) TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address already in use'

2012-12-01 Thread Eric Yang (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508121#comment-13508121
 ] 

Eric Yang commented on MAPREDUCE-4798:
--

Thanks Sam.

> TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address 
> already in use'
> -
>
> Key: MAPREDUCE-4798
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4798
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: jobhistoryserver, test
>Affects Versions: 1.0.3
> Environment: Red Hat Ent Server 6.2
>Reporter: sam liu
>Priority: Minor
>  Labels: patch
> Attachments: MAPREDUCE-4798_branch-1.patch, MAPREDUCE-4798.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> UT Failure in IHC 1.0.3: org.apache.hadoop.mapred.TestJobHistoryServer. This 
> UT fails sometimes.
> The error message is:
> 'Testcase: testHistoryServerStandalone took 5.376 sec
>   Caused an ERROR
> Address already in use
> java.lang.AssertionError: Address already in use
>   at 
> org.apache.hadoop.mapred.TestJobHistoryServer.testHistoryServerStandalone(TestJobHistoryServer.java:113)'

--
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] [Updated] (MAPREDUCE-4798) TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address already in use'

2012-12-01 Thread Eric Yang (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Yang updated MAPREDUCE-4798:
-

Resolution: Fixed
Status: Resolved  (was: Patch Available)

I just committed this to 1.x branches.  JobHistoryServer doesn't exist in 
trunk, hence no action there.

> TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address 
> already in use'
> -
>
> Key: MAPREDUCE-4798
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4798
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: jobhistoryserver, test
>Affects Versions: 1.0.3
> Environment: Red Hat Ent Server 6.2
>Reporter: sam liu
>Priority: Minor
>  Labels: patch
> Attachments: MAPREDUCE-4798_branch-1.patch, MAPREDUCE-4798.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> UT Failure in IHC 1.0.3: org.apache.hadoop.mapred.TestJobHistoryServer. This 
> UT fails sometimes.
> The error message is:
> 'Testcase: testHistoryServerStandalone took 5.376 sec
>   Caused an ERROR
> Address already in use
> java.lang.AssertionError: Address already in use
>   at 
> org.apache.hadoop.mapred.TestJobHistoryServer.testHistoryServerStandalone(TestJobHistoryServer.java:113)'

--
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] [Updated] (MAPREDUCE-4798) TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address already in use'

2012-12-01 Thread Eric Yang (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Yang updated MAPREDUCE-4798:
-

Status: Patch Available  (was: Open)

+1 looks good.

> TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address 
> already in use'
> -
>
> Key: MAPREDUCE-4798
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4798
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: jobhistoryserver, test
>Affects Versions: 1.0.3
> Environment: Red Hat Ent Server 6.2
>Reporter: sam liu
>Priority: Minor
>  Labels: patch
> Attachments: MAPREDUCE-4798_branch-1.patch, MAPREDUCE-4798.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> UT Failure in IHC 1.0.3: org.apache.hadoop.mapred.TestJobHistoryServer. This 
> UT fails sometimes.
> The error message is:
> 'Testcase: testHistoryServerStandalone took 5.376 sec
>   Caused an ERROR
> Address already in use
> java.lang.AssertionError: Address already in use
>   at 
> org.apache.hadoop.mapred.TestJobHistoryServer.testHistoryServerStandalone(TestJobHistoryServer.java:113)'

--
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] [Updated] (MAPREDUCE-4798) TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address already in use'

2012-12-01 Thread Eric Yang (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Yang updated MAPREDUCE-4798:
-

Target Version/s: 1.0.4, 1.2.0, 1.1.2  (was: 1.0.3)
   Fix Version/s: (was: 1.0.3)

> TestJobHistoryServer fails some times with 'java.lang.AssertionError: Address 
> already in use'
> -
>
> Key: MAPREDUCE-4798
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4798
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: jobhistoryserver, test
>Affects Versions: 1.0.3
> Environment: Red Hat Ent Server 6.2
>Reporter: sam liu
>Priority: Minor
>  Labels: patch
> Attachments: MAPREDUCE-4798_branch-1.patch, MAPREDUCE-4798.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> UT Failure in IHC 1.0.3: org.apache.hadoop.mapred.TestJobHistoryServer. This 
> UT fails sometimes.
> The error message is:
> 'Testcase: testHistoryServerStandalone took 5.376 sec
>   Caused an ERROR
> Address already in use
> java.lang.AssertionError: Address already in use
>   at 
> org.apache.hadoop.mapred.TestJobHistoryServer.testHistoryServerStandalone(TestJobHistoryServer.java:113)'

--
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-3772) MultipleOutputs output lost if baseOutputPath starts with ../

2012-12-01 Thread Priyo Mustafi (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508108#comment-13508108
 ] 

Priyo Mustafi commented on MAPREDUCE-3772:
--

In that case for current releases we should send out a very visible warning in 
the mapreduce output when somebody attempts to use the baseOutputPath with a 
fully qualified path which is outside main output along with the javadoc 
changes.  This way folks who are currently using this feature in the incorrect 
way are aware that there would be data-loss.  In a later release we should 
enforce it so whether somebody reads the javadoc in detail or not, they are 
never faced with data loss.  

> MultipleOutputs output lost if baseOutputPath starts with ../
> -
>
> Key: MAPREDUCE-3772
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3772
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: client
>Affects Versions: 0.20.2
>Reporter: Radim Kolar
>Assignee: Harsh J
> Attachments: MAPREDUCE-3772.patch
>
>
> Lets say you have output directory set:
> FileOutputFormat.setOutputPath(job, "/tmp/multi1/out");
> and want to place output from MultipleOutputs into /tmp/multi1/extra
> I expect following code to work:
> mos = new MultipleOutputs(context);
> mos.write(new Text("zrr"), value, "../extra/");
> but no Exception is throw and expected output directory /tmp/multi1/extra 
> does not even exists. All data written to this output vanish without trace.
> To make it work fullpath must be used
> mos.write(new Text("zrr"), value, "/tmp/multi1/extra/");
> Output is listed in statistics from MultipleOutputs correctly:
> org.apache.hadoop.mapreduce.lib.output.MultipleOutputs
> ../gaja1/=1 (* everything is lost *)
> /tmp/multi1/out/../ksd34/=1 (* this using full path works 
> *)
> list1=6667

--
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-3772) MultipleOutputs output lost if baseOutputPath starts with ../

2012-12-01 Thread Radim Kolar (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508045#comment-13508045
 ] 

Radim Kolar commented on MAPREDUCE-3772:


data loss with ../path is not related to speculative execution.

> MultipleOutputs output lost if baseOutputPath starts with ../
> -
>
> Key: MAPREDUCE-3772
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3772
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: client
>Affects Versions: 0.20.2
>Reporter: Radim Kolar
>Assignee: Harsh J
> Attachments: MAPREDUCE-3772.patch
>
>
> Lets say you have output directory set:
> FileOutputFormat.setOutputPath(job, "/tmp/multi1/out");
> and want to place output from MultipleOutputs into /tmp/multi1/extra
> I expect following code to work:
> mos = new MultipleOutputs(context);
> mos.write(new Text("zrr"), value, "../extra/");
> but no Exception is throw and expected output directory /tmp/multi1/extra 
> does not even exists. All data written to this output vanish without trace.
> To make it work fullpath must be used
> mos.write(new Text("zrr"), value, "/tmp/multi1/extra/");
> Output is listed in statistics from MultipleOutputs correctly:
> org.apache.hadoop.mapreduce.lib.output.MultipleOutputs
> ../gaja1/=1 (* everything is lost *)
> /tmp/multi1/out/../ksd34/=1 (* this using full path works 
> *)
> list1=6667

--
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] [Updated] (MAPREDUCE-4839) TextPartioner for hashing Text with good hashing function to get better distribution

2012-12-01 Thread Radim Kolar (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radim Kolar updated MAPREDUCE-4839:
---

Attachment: textpartitioner1.txt

> TextPartioner for hashing Text with good hashing function to get better 
> distribution
> 
>
> Key: MAPREDUCE-4839
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4839
> Project: Hadoop Map/Reduce
>  Issue Type: New Feature
>Reporter: Radim Kolar
> Attachments: textpartitioner1.txt
>
>
> partitioner for Text keys using util.Hash framework for hashing function

--
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-4839) TextPartioner for hashing Text with good hashing function to get better distribution

2012-12-01 Thread Radim Kolar (JIRA)
Radim Kolar created MAPREDUCE-4839:
--

 Summary: TextPartioner for hashing Text with good hashing function 
to get better distribution
 Key: MAPREDUCE-4839
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4839
 Project: Hadoop Map/Reduce
  Issue Type: New Feature
Reporter: Radim Kolar


partitioner for Text keys using util.Hash framework for hashing function

--
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-4836) Elapsed time for running tasks on AM web UI tasks page is 0

2012-12-01 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507970#comment-13507970
 ] 

Hudson commented on MAPREDUCE-4836:
---

Integrated in Hadoop-Mapreduce-trunk #1274 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1274/])
MAPREDUCE-4836. Elapsed time for running tasks on AM web UI tasks page is 
0. (Ravi Prakash via jeagles) (Revision 1415860)

 Result = SUCCESS
jeagles : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1415860
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/dao/TaskInfo.java


> Elapsed time for running tasks on AM web UI tasks page is 0
> ---
>
> Key: MAPREDUCE-4836
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4836
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.5
>Reporter: Ravi Prakash
>Assignee: Ravi Prakash
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.6
>
> Attachments: MAPREDUCE-4836.patch, MAPREDUCE-4836.patch
>
>
> Yeah! The summary

--
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-4836) Elapsed time for running tasks on AM web UI tasks page is 0

2012-12-01 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507959#comment-13507959
 ] 

Hudson commented on MAPREDUCE-4836:
---

Integrated in Hadoop-Hdfs-trunk #1243 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1243/])
MAPREDUCE-4836. Elapsed time for running tasks on AM web UI tasks page is 
0. (Ravi Prakash via jeagles) (Revision 1415860)

 Result = FAILURE
jeagles : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1415860
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/dao/TaskInfo.java


> Elapsed time for running tasks on AM web UI tasks page is 0
> ---
>
> Key: MAPREDUCE-4836
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4836
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.5
>Reporter: Ravi Prakash
>Assignee: Ravi Prakash
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.6
>
> Attachments: MAPREDUCE-4836.patch, MAPREDUCE-4836.patch
>
>
> Yeah! The summary

--
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-4836) Elapsed time for running tasks on AM web UI tasks page is 0

2012-12-01 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507953#comment-13507953
 ] 

Hudson commented on MAPREDUCE-4836:
---

Integrated in Hadoop-Hdfs-0.23-Build #452 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/452/])
MAPREDUCE-4836. Elapsed time for running tasks on AM web UI tasks page is 
0. (Ravi Prakash via jeagles) (Revision 1415866)

 Result = SUCCESS
jeagles : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1415866
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/dao/TaskInfo.java


> Elapsed time for running tasks on AM web UI tasks page is 0
> ---
>
> Key: MAPREDUCE-4836
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4836
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.5
>Reporter: Ravi Prakash
>Assignee: Ravi Prakash
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.6
>
> Attachments: MAPREDUCE-4836.patch, MAPREDUCE-4836.patch
>
>
> Yeah! The summary

--
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-4836) Elapsed time for running tasks on AM web UI tasks page is 0

2012-12-01 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507929#comment-13507929
 ] 

Hudson commented on MAPREDUCE-4836:
---

Integrated in Hadoop-Yarn-trunk #53 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/53/])
MAPREDUCE-4836. Elapsed time for running tasks on AM web UI tasks page is 
0. (Ravi Prakash via jeagles) (Revision 1415860)

 Result = SUCCESS
jeagles : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1415860
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/dao/TaskInfo.java


> Elapsed time for running tasks on AM web UI tasks page is 0
> ---
>
> Key: MAPREDUCE-4836
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4836
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.5
>Reporter: Ravi Prakash
>Assignee: Ravi Prakash
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.6
>
> Attachments: MAPREDUCE-4836.patch, MAPREDUCE-4836.patch
>
>
> Yeah! The summary

--
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