Re: REMINDER! REGISTRATIONS CLOSING 5/6!

Thanks Allen a lot for organizing the Haoop Bug Bash, very happy to see many folks by face! Wish you all a nice weekend! --Yongjun On Tue, May 5, 2015 at 9:31 PM, Allen Wittenauer wrote: > > On May 5, 2015, at 8:10 PM, Allen Wittenauer wrote: > > > * We’ll be closing registrat

[jira] [Resolved] (MAPREDUCE-5617) map task is not re-launched when the task is failed while reducers are running with full cluster capacity - which will lead to job hang

[ https://issues.apache.org/jira/browse/MAPREDUCE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved MAPREDUCE-5617. Resolution: Invalid Yes Vinod. I am marking this as invalid. I checked a similar scenario, and

[jira] [Resolved] (MAPREDUCE-1396) Display more details about memory usage on jobtracker web UI

[ https://issues.apache.org/jira/browse/MAPREDUCE-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-1396. Resolution: Won't Fix We haven't done a 1.x release in ~2 years.

[jira] [Resolved] (MAPREDUCE-488) JobTracker webui should report heap memory used

[ https://issues.apache.org/jira/browse/MAPREDUCE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-488. --- Resolution: Won't Fix We haven't done a 1.x release in ~2 years. Un

[jira] [Resolved] (MAPREDUCE-2769) TT should give more info for failed file operations

[ https://issues.apache.org/jira/browse/MAPREDUCE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-2769. Resolution: Won't Fix We haven't done a 1.x/0.21/0.22 based rele

[jira] [Resolved] (MAPREDUCE-2759) TaskTrackerAction should follow Open Closed Principle

[ https://issues.apache.org/jira/browse/MAPREDUCE-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-2759. Resolution: Won't Fix We haven't done a 1.x/0.21/0.22 based rele

[jira] [Resolved] (MAPREDUCE-2049) JT and TT should prune invalid local dirs on startup

[ https://issues.apache.org/jira/browse/MAPREDUCE-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-2049. Resolution: Won't Fix We haven't done a 1.x/0.21/0.22 based rele

[jira] [Resolved] (MAPREDUCE-472) Unassigned tasks cannot be killed/failed from the web UI

[ https://issues.apache.org/jira/browse/MAPREDUCE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-472. --- Resolution: Won't Fix We haven't done a 1.x release in ~2 years. Un

[jira] [Resolved] (MAPREDUCE-5903) If Kerberos Authentication is enabled, MapReduce job is failing on reducer phase

[ https://issues.apache.org/jira/browse/MAPREDUCE-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5903. Resolution: Invalid My comment [above|https://issues.apache.org

[jira] [Resolved] (MAPREDUCE-5703) Job client gets failure though RM side job execution result is FINISHED and SUCCEEDED

[ https://issues.apache.org/jira/browse/MAPREDUCE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5703. Resolution: Duplicate I have run into the same problem many time

[jira] [Resolved] (MAPREDUCE-5606) JobTracker blocked for DFSClient: Failed recovery attempt

[ https://issues.apache.org/jira/browse/MAPREDUCE-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5606. Resolution: Won't Fix I originally debugged the user.location bu

[jira] [Resolved] (MAPREDUCE-5582) Setting mapred.job.reduce.memory.mb to 0 from a job with CapacityTracker leads to inconsistent state in JVMManager

[ https://issues.apache.org/jira/browse/MAPREDUCE-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5582. Resolution: Won't Fix We haven't done a 1.x release in ~2 years.

[jira] [Resolved] (MAPREDUCE-5697) My MapReduce program read .gz packets from HDFS, but if one of the packets is incorrect, the program will throw exception, then job will stop.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5697. Resolution: Invalid Not sure if this is a real bug or not. In an

[jira] [Resolved] (MAPREDUCE-5716) yarn framework occurs Shell$ExitCodeException

[ https://issues.apache.org/jira/browse/MAPREDUCE-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5716. Resolution: Invalid Exit code 127 usually means that the command

[jira] [Resolved] (MAPREDUCE-5563) TestMiniMRChildTask test cases failing on trunk

[ https://issues.apache.org/jira/browse/MAPREDUCE-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5563. Resolution: Invalid It passes now on trunk for me too. Closing t

Re: Jenkins precommit-*-build

Thank you Allen! --Konst On Tue, May 5, 2015 at 5:14 PM, Allen Wittenauer wrote: > > HDFS, MAPREDUCE, and YARN have been migrated. > > Let me know of any issues and I’ll try to get to them as I can. This > should be the end of the Jenkins race conditions for our pre commits! > *crosses fingers

Re: [DISCUSS] branch-1

+1 to auto-closing branch-1 issues. -Sandy On Fri, May 8, 2015 at 11:14 AM, Karthik Kambatla wrote: > Closing out the JIRAs as "Auto Closed" or "Closed due to Inactivity" seems > reasonable to me. For branch-1, we can be more aggressive. We should > probably do the same less aggressively for ot

[jira] [Resolved] (MAPREDUCE-4672) RM with lost NMs results in massive log of AppAttemptId doesnt exist in cache

[ https://issues.apache.org/jira/browse/MAPREDUCE-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-4672. Resolution: Duplicate bq. But when NM goes down, it doesn't kill

[jira] [Resolved] (MAPREDUCE-3945) JobHistoryServer should store tokens to authenticate clients across restart

[ https://issues.apache.org/jira/browse/MAPREDUCE-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-3945. Resolution: Duplicate This got fixed much later at MAPREDUCE-533

[jira] [Resolved] (MAPREDUCE-3101) [Umbrella] Security issues in YARN

[ https://issues.apache.org/jira/browse/MAPREDUCE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-3101. Resolution: Fixed Assignee: (was: Vinod Kumar Vavilapal

Re: [DISCUSS] branch-1

Closing out the JIRAs as "Auto Closed" or "Closed due to Inactivity" seems reasonable to me. For branch-1, we can be more aggressive. We should probably do the same less aggressively for other branches too. On Fri, May 8, 2015 at 11:01 AM, Arun C Murthy wrote: > +1 > > Arun > > On May 8, 2015, a

[jira] [Resolved] (MAPREDUCE-3561) [Umbrella ticket] Performance issues in YARN+MR

[ https://issues.apache.org/jira/browse/MAPREDUCE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-3561. Resolution: Fixed I originally opened this to track performance

[jira] [Resolved] (MAPREDUCE-5567) [Umbrella] Stabilize MR framework w.r.t ResourceManager restart

[ https://issues.apache.org/jira/browse/MAPREDUCE-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-5567. Resolution: Fixed Resolving this umbrella JIRA. RM restart has l

[jira] [Resolved] (MAPREDUCE-116) Have a test to verify that descendent processes of tasks that ignore SIGTERM are eventually cleaned up by a SIGKILL

[ https://issues.apache.org/jira/browse/MAPREDUCE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-116. --- Resolution: Won't Fix Long past when it was needed. The SIGTERM+SI

[jira] [Resolved] (MAPREDUCE-41) Write unit tests to verify the fix for HADOOP-5349

[ https://issues.apache.org/jira/browse/MAPREDUCE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-41. -- Resolution: Won't Fix Long past when it was needed. Closing as Won't F

Re: [DISCUSS] branch-1

+1 Arun On May 8, 2015, at 10:41 AM, Allen Wittenauer wrote: > > May we declare this branch dead and just close bugs (but not > necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has > any intention of working on the 1.3 release, especially given that 1.2.1 w

Re: [DISCUSS] branch-1

I think it would be fine to "auto-close" most remaining branch-1 issues even if the branch is still formally considered alive. I don't expect us to create a new 1.x release unless a security vulnerability or critical bug forces it. Closing all non-critical issues would match with the reality that

[jira] [Resolved] (MAPREDUCE-1) Hadoop mapreduce should always ship the jar file(s) specified by the user

[ https://issues.apache.org/jira/browse/MAPREDUCE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-1. - Resolution: Duplicate Very old JIRA. Seems like a dup of HADOOP-6103 per

[jira] [Resolved] (MAPREDUCE-97) Increase map/reduce child tasks' heapsize from current default of 200M to 512M

[ https://issues.apache.org/jira/browse/MAPREDUCE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved MAPREDUCE-97. -- Resolution: Invalid Very old JIRA. With MRv2, we have largely also mo

Re: [DISCUSS] branch-1

I would be -1 to declaring the branch dead just yet. There have been 7 commits to that branch this year. I know this isn't comparable to trunk or branch-2, but it is not negligible either. I propose we come up with a policy for deprecating past major release branches. May be, something along the l

[DISCUSS] branch-1

May we declare this branch dead and just close bugs (but not necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any intention of working on the 1.3 release, especially given that 1.2.1 was Aug 2013 …. I guess we need a PMC member to declare a vo

Hadoop-Mapreduce-trunk - Build # 2137 - Failure

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2137/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32389 lines...] [ERROR] To see the full stack trace

[jira] [Resolved] (MAPREDUCE-3847) Job in running state without any progress and no tasks running

[ https://issues.apache.org/jira/browse/MAPREDUCE-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K resolved MAPREDUCE-3847. -- Resolution: Cannot Reproduce Not a problem anymore, closing it. Feel free to reopen if you s

[jira] [Resolved] (MAPREDUCE-4127) Resource manager UI does not show the Job Priority

[ https://issues.apache.org/jira/browse/MAPREDUCE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K resolved MAPREDUCE-4127. -- Resolution: Duplicate It will be handled as part of YARN-1963. > Resource manager UI does n