[jira] [Commented] (MAPREDUCE-2399) The embedded web framework for MAPREDUCE-279

[ https://issues.apache.org/jira/browse/MAPREDUCE-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177977#comment-13177977 ] Harsh J commented on MAPREDUCE-2399: I guess there isn't anything to discuss as th

[jira] [Resolved] (MAPREDUCE-80) Counter formatting for the user logs should be pulled out of the public Counters API

[ https://issues.apache.org/jira/browse/MAPREDUCE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-80. -- Resolution: Not A Problem This has gone stale as well, not a problem anymore. > Coun

[jira] [Resolved] (MAPREDUCE-62) job.xml should have high replication factor by default

[ https://issues.apache.org/jira/browse/MAPREDUCE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-62. -- Resolution: Not A Problem This is now done via {{mapred.submit.replication}} and the likes. Default i

[jira] [Resolved] (MAPREDUCE-68) Hadoop reduce scheduler sometimes leaves machines idle

[ https://issues.apache.org/jira/browse/MAPREDUCE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-68. -- Resolution: Not A Problem Not a problem with current release schedulers. > Hadoop re

[jira] [Resolved] (MAPREDUCE-74) JobClient hangs when getting map-task reports

[ https://issues.apache.org/jira/browse/MAPREDUCE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-74. -- Resolution: Not A Problem This has gone stale. Not reported again in recent years. >

[jira] [Resolved] (MAPREDUCE-66) The local bytes read of Mapper tasks are too high than bytes written

[ https://issues.apache.org/jira/browse/MAPREDUCE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-66. -- Resolution: Not A Problem This can be explained by looking at the task logs and the sort outputs.

[jira] [Resolved] (MAPREDUCE-69) NPE in TaskTracker RenitTrackerAction

[ https://issues.apache.org/jira/browse/MAPREDUCE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-69. -- Resolution: Cannot Reproduce Gone stale, was probably fixed elsewhere. > NPE in Task

[jira] [Resolved] (MAPREDUCE-71) JobClient can be constructed without initializing object state

[ https://issues.apache.org/jira/browse/MAPREDUCE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-71. -- Resolution: Not A Problem The JobClient is deprecated. The empty constructor seems to be used only fo

[jira] [Resolved] (MAPREDUCE-61) Counters value of reduce input records do not match map output records

[ https://issues.apache.org/jira/browse/MAPREDUCE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-61. -- Resolution: Not A Problem See comment above. > Counters value of reduce input recor

[jira] [Resolved] (MAPREDUCE-58) Duplicate metric name getTask

[ https://issues.apache.org/jira/browse/MAPREDUCE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-58. -- Resolution: Not A Problem Does not occur in task launches anymore. > Duplicate metri

[jira] [Resolved] (MAPREDUCE-57) The JobConf instance passed to JobClient is unnecessarily modified

[ https://issues.apache.org/jira/browse/MAPREDUCE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-57. -- Resolution: Not A Problem This isn't an issue anymore. And submit job being called twice is not prop

[jira] [Resolved] (MAPREDUCE-56) Client recovery from Job tracker restarts and connectivity failures

[ https://issues.apache.org/jira/browse/MAPREDUCE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-56. -- Resolution: Not A Problem This looked to be part of some larger JT HA operation, but has gone stale.

[jira] [Resolved] (MAPREDUCE-51) TestTaskLimits fails occassionally

[ https://issues.apache.org/jira/browse/MAPREDUCE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-51. -- Resolution: Not A Problem Has not been seen in over two years. Probably fixed long ago.

[jira] [Resolved] (MAPREDUCE-54) distcp failed due to problem in creating files

[ https://issues.apache.org/jira/browse/MAPREDUCE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-54. -- Resolution: Not A Problem Hasn't been seen in a while now. > distcp failed due to pr

[jira] [Resolved] (MAPREDUCE-53) JUnit tests should not create directories in the current directory

[ https://issues.apache.org/jira/browse/MAPREDUCE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-53. -- Resolution: Not A Problem Doesn't seem to do so anymore. > JUnit tests should not cr

[jira] [Resolved] (MAPREDUCE-37) MAP_OUTPUT_BYTES counter is not recorded in Job history log for Map only jobs

[ https://issues.apache.org/jira/browse/MAPREDUCE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-37. -- Resolution: Not A Problem It is recorded in current releases. > MAP_OUTPUT_BYTES cou

[jira] [Resolved] (MAPREDUCE-49) JobTracker UI shows Incorrect reporter progress.

[ https://issues.apache.org/jira/browse/MAPREDUCE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-49. -- Resolution: Duplicate See comment above. > JobTracker UI shows Incorrect reporter pr

[jira] [Resolved] (MAPREDUCE-47) Tasklog servlet doesn't display any logs when logs are short

[ https://issues.apache.org/jira/browse/MAPREDUCE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-47. -- Resolution: Duplicate See comment above. > Tasklog servlet doesn't display any logs

[jira] [Resolved] (MAPREDUCE-45) JobStatus should contain user name and carry forward start time when job is killed.

[ https://issues.apache.org/jira/browse/MAPREDUCE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-45. -- Resolution: Cannot Reproduce This doesn't seem to be a problem with current versions anymore.

[jira] [Resolved] (MAPREDUCE-43) Retired jobs are not present in the job list returned to the job-client.

[ https://issues.apache.org/jira/browse/MAPREDUCE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-43. -- Resolution: Invalid I think it is OK to not show retired to users. Retired should mean GC'd (or summ

[jira] [Resolved] (MAPREDUCE-46) mapred/local/jobTracker is not cleanup correctly

[ https://issues.apache.org/jira/browse/MAPREDUCE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-46. -- Resolution: Cannot Reproduce Haven't noticed this issue in branch-1. > mapred/local/

[jira] [Resolved] (MAPREDUCE-39) Task tracker should wait for the process to exit before declaring the task successful or failed.

[ https://issues.apache.org/jira/browse/MAPREDUCE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-39. -- Resolution: Invalid This'd be complicated with JVM reuse. Besides, if a task reports itself done, it

[jira] [Resolved] (MAPREDUCE-38) TaskCompletionEvents do not distinguish between FAILED and KILLED task-attempts

[ https://issues.apache.org/jira/browse/MAPREDUCE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-38. -- Resolution: Not A Problem Don't think this is a problem on current versions. Please reopen or open a

[jira] [Resolved] (MAPREDUCE-42) task trackers should not restart for having a late heartbeat

[ https://issues.apache.org/jira/browse/MAPREDUCE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-42. -- Resolution: Invalid This was decided as not a good approach. Also gone stale. > task

[jira] [Resolved] (MAPREDUCE-48) Expired launching tasks affect small jobs' execution time

[ https://issues.apache.org/jira/browse/MAPREDUCE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-48. -- Resolution: Not A Problem Not a problem anymore with the current versions. > Expired

[jira] [Resolved] (MAPREDUCE-32) Killed task is logged as Failed upon a lost tracker

[ https://issues.apache.org/jira/browse/MAPREDUCE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-32. -- Resolution: Not A Problem This has gone stale. If this is still an issue, lets open a new one (if it

[jira] [Resolved] (MAPREDUCE-33) Avoid using deprecated api's

[ https://issues.apache.org/jira/browse/MAPREDUCE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-33. -- Resolution: Not A Problem This has gone stale. We should pursue this as a new ticket, given MR2.

[jira] [Resolved] (MAPREDUCE-34) Reduce step hangs while recovering a block from bad datanode

[ https://issues.apache.org/jira/browse/MAPREDUCE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-34. -- Resolution: Not A Problem This was probably fixed. DFSClient recovery works as intended in current r

[jira] [Resolved] (MAPREDUCE-36) LInks in http://jobtracker/machines.jsp are broken while running hadoop locally

[ https://issues.apache.org/jira/browse/MAPREDUCE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-36. -- Resolution: Cannot Reproduce The links have been fine for me since 0.20, when I began using Hadoop. P

[jira] [Resolved] (MAPREDUCE-29) JVM reuse across task types

[ https://issues.apache.org/jira/browse/MAPREDUCE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-29. -- Resolution: Invalid Given the feature of different heap sizes per task type, this does not make sens

[jira] [Resolved] (MAPREDUCE-26) The shuffle keeps the ReduceTask locked while doing a FileSystem.rename leading to task timeouts

[ https://issues.apache.org/jira/browse/MAPREDUCE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-26. -- Resolution: Not A Problem We attempt a proper rename now, and only fall back to copy+delete otherwise

[jira] [Resolved] (MAPREDUCE-30) setting io.sort.factor does not have effect?

[ https://issues.apache.org/jira/browse/MAPREDUCE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-30. -- Resolution: Invalid The sort factor works as intended. This was probably fixed a while ago.

[jira] [Resolved] (MAPREDUCE-31) Have a better shutdown and cleanup mechanism in JobTracker

[ https://issues.apache.org/jira/browse/MAPREDUCE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-31. -- Resolution: Not A Problem This isn't a problem anymore on trunk. The JT has gone away and I do not th

[jira] [Resolved] (MAPREDUCE-19) TaskMemoryMonitorThread is not stopped in close

[ https://issues.apache.org/jira/browse/MAPREDUCE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-19. -- Resolution: Not A Problem This hasn't been reported in the recent past, please reopen if its still a

[jira] [Resolved] (MAPREDUCE-22) Per task memory usage stats from TaskMemoryManager on mapred web ui

[ https://issues.apache.org/jira/browse/MAPREDUCE-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-22. -- Resolution: Invalid Looks like the displaying was determined to be a bad idea? Please reopen if not.

[jira] [Resolved] (MAPREDUCE-24) Reduce stuck in pending state for ever even though the job tracker shows a lot of free slots

[ https://issues.apache.org/jira/browse/MAPREDUCE-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-24. -- Resolution: Not A Problem This has gone stale, and has not been reported again recently. Was probably

[jira] [Resolved] (MAPREDUCE-14) extensive map tasks failures because of SocketTimeoutException during statusUpdate

[ https://issues.apache.org/jira/browse/MAPREDUCE-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-14. -- Resolution: Not A Problem Haven't seen this occur with any of recent versions, having also seen jobs

[jira] [Resolved] (MAPREDUCE-23) Start times for some tasks are missing from task reports after job tracker restart

[ https://issues.apache.org/jira/browse/MAPREDUCE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-23. -- Resolution: Not A Problem This has gone stale, and has not been seen recently. With MR2, I do not thi

[jira] [Resolved] (MAPREDUCE-13) Mapper failed due to out of memory

[ https://issues.apache.org/jira/browse/MAPREDUCE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-13. -- Resolution: Not A Problem This isn't a problem anymore. Compressed inputs work nicely at present and

[jira] [Resolved] (MAPREDUCE-17) Changing priority of a completed job causes problems in JobInProgressListeners

[ https://issues.apache.org/jira/browse/MAPREDUCE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-17. -- Resolution: Not A Problem This isn't an issue anymore. I've not noticed it with branch-1, nor is it a

[jira] [Resolved] (MAPREDUCE-20) If a mapper of a map/reduce job with combiner has to spill the map output, the performance degrades significantly

[ https://issues.apache.org/jira/browse/MAPREDUCE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-20. -- Resolution: Duplicate HADOOP-2399 possibly had fixed this. This has gone stale, and has not been rep

[jira] [Resolved] (MAPREDUCE-10) NPE in SocketChannelOutputStream during large sort benchmark

[ https://issues.apache.org/jira/browse/MAPREDUCE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-10. -- Resolution: Not A Problem This has gone stale, and has not been reported again recently. Was probably

[jira] [Resolved] (MAPREDUCE-16) Reduce task failed at shuffling time, throwing null pointer exception

[ https://issues.apache.org/jira/browse/MAPREDUCE-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-16. -- Resolution: Not A Problem This has gone stale, and has not been reported again recently. Was probably

[jira] [Resolved] (MAPREDUCE-8) "Bad File Descriptor" in closing local file

[ https://issues.apache.org/jira/browse/MAPREDUCE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-8. - Resolution: Not A Problem Not a problem anymore. HADOOP-757 apparently fixed it a long time ago.

[jira] [Resolved] (MAPREDUCE-6) Task attempt stopped shuffling and hung the job

[ https://issues.apache.org/jira/browse/MAPREDUCE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-6. - Resolution: Not A Problem Gone stale. Not an observed problem anymore. > Task attempt s

[jira] [Commented] (MAPREDUCE-3611) trunk build failure

[ https://issues.apache.org/jira/browse/MAPREDUCE-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177918#comment-13177918 ] Harsh J commented on MAPREDUCE-3611: Thanks for taking the time and reporting thou

[jira] [Resolved] (MAPREDUCE-3611) trunk build failure

[ https://issues.apache.org/jira/browse/MAPREDUCE-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved MAPREDUCE-3611. Resolution: Duplicate Fix Version/s: 0.23.1 This was recently fixed by MAPREDUCE-3608, p

[jira] [Created] (MAPREDUCE-3611) trunk build failure

trunk build failure --- Key: MAPREDUCE-3611 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3611 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Sho Shimauchi Priority: Critical https://bui