[jira] [Commented] (MAPREDUCE-6516) JVM reuse in Yarn

[ https://issues.apache.org/jira/browse/MAPREDUCE-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968601#comment-14968601 ] Bikas Saha commented on MAPREDUCE-6516: --- Have you considered using Apache Tez to

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981829#comment-14981829 ] Bikas Saha commented on MAPREDUCE-5485: --- The repeatable commit API seems useful.

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991486#comment-14991486 ] Bikas Saha commented on MAPREDUCE-5485: --- I dont think AM should reboot to retry

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993559#comment-14993559 ] Bikas Saha commented on MAPREDUCE-5485: --- bq. I don't think so. Can you take a lo

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997152#comment-14997152 ] Bikas Saha commented on MAPREDUCE-5485: --- I am not disagreeing with the AM retry

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997949#comment-14997949 ] Bikas Saha commented on MAPREDUCE-5485: --- Separate jira sounds good. We may need

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000291#comment-15000291 ] Bikas Saha commented on MAPREDUCE-5485: --- bq. The cleanupInterruptedCommit() alre

[jira] [Commented] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API

[ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000789#comment-15000789 ] Bikas Saha commented on MAPREDUCE-5485: --- Sorry I missed that the test committer

[jira] [Commented] (MAPREDUCE-6548) Jobs executed can be configurated with specific users and time hours

[ https://issues.apache.org/jira/browse/MAPREDUCE-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005483#comment-15005483 ] Bikas Saha commented on MAPREDUCE-6548: --- Does the admission control added to YAR

[jira] [Created] (MAPREDUCE-6650) Surface error histograms from the AM

Bikas Saha created MAPREDUCE-6650: - Summary: Surface error histograms from the AM Key: MAPREDUCE-6650 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6650 Project: Hadoop Map/Reduce Issu

[jira] [Commented] (MAPREDUCE-5036) Default shuffle handler port should not be 8080

[ https://issues.apache.org/jira/browse/MAPREDUCE-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678873#comment-13678873 ] Bikas Saha commented on MAPREDUCE-5036: --- The title doesnt reflect the change in

[jira] [Commented] (MAPREDUCE-5312) TestRMNMInfo is failing

[ https://issues.apache.org/jira/browse/MAPREDUCE-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679237#comment-13679237 ] Bikas Saha commented on MAPREDUCE-5312: --- The test failure is due the flattening

[jira] [Created] (MAPREDUCE-5314) Fix build break by YARN-686 (flatten node report)

Bikas Saha created MAPREDUCE-5314: - Summary: Fix build break by YARN-686 (flatten node report) Key: MAPREDUCE-5314 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5314 Project: Hadoop Map/Reduce

[jira] [Commented] (MAPREDUCE-5187) Create mapreduce command scripts on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685795#comment-13685795 ] Bikas Saha commented on MAPREDUCE-5187: --- Do we support pipes? I dont think we do

[jira] [Commented] (MAPREDUCE-5278) Distributed cache is broken when JT staging dir is not on the default FS

[ https://issues.apache.org/jira/browse/MAPREDUCE-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685822#comment-13685822 ] Bikas Saha commented on MAPREDUCE-5278: --- We should add a config name and default

[jira] [Commented] (MAPREDUCE-5278) Distributed cache is broken when JT staging dir is not on the default FS

[ https://issues.apache.org/jira/browse/MAPREDUCE-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686079#comment-13686079 ] Bikas Saha commented on MAPREDUCE-5278: --- Great. My bad. Now that I have re-read

[jira] [Commented] (MAPREDUCE-5330) JVM manager should not forcefully kill the process on Signal.TERM on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699219#comment-13699219 ] Bikas Saha commented on MAPREDUCE-5330: --- The TERM signal typically notifies the

[jira] [Commented] (MAPREDUCE-5187) Create mapreduce command scripts on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699258#comment-13699258 ] Bikas Saha commented on MAPREDUCE-5187: --- looks ok to me. +1 > C

[jira] [Commented] (MAPREDUCE-5278) Distributed cache is broken when JT staging dir is not on the default FS

[ https://issues.apache.org/jira/browse/MAPREDUCE-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699264#comment-13699264 ] Bikas Saha commented on MAPREDUCE-5278: --- The config string is still being used i

[jira] [Created] (MAPREDUCE-5398) MR changes for YARN-513

Bikas Saha created MAPREDUCE-5398: - Summary: MR changes for YARN-513 Key: MAPREDUCE-5398 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5398 Project: Hadoop Map/Reduce Issue Type: Bug

[jira] [Updated] (MAPREDUCE-5398) MR changes for YARN-513

[ https://issues.apache.org/jira/browse/MAPREDUCE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5398: -- Issue Type: Improvement (was: Bug) > MR changes for YARN-513 > ---

[jira] [Updated] (MAPREDUCE-5398) MR changes for YARN-513

[ https://issues.apache.org/jira/browse/MAPREDUCE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5398: -- Attachment: MAPREDUCE-5398.patch > MR changes for YARN-513 > --- >

[jira] [Resolved] (MAPREDUCE-5398) MR changes for YARN-513

[ https://issues.apache.org/jira/browse/MAPREDUCE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha resolved MAPREDUCE-5398. --- Resolution: Fixed Fix Version/s: 2.1.0-beta Target Version/s: 2.1.0-beta

[jira] [Commented] (MAPREDUCE-5391) TestNonLocalJobJarSubmission fails on Windows due to missing classpath entries

[ https://issues.apache.org/jira/browse/MAPREDUCE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711644#comment-13711644 ] Bikas Saha commented on MAPREDUCE-5391: --- Looks good. +1. > Test

[jira] [Commented] (MAPREDUCE-5403) Get rid of yarn.application.classpath

[ https://issues.apache.org/jira/browse/MAPREDUCE-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713889#comment-13713889 ] Bikas Saha commented on MAPREDUCE-5403: --- >From what I understand its meant for a

[jira] [Commented] (MAPREDUCE-5403) yarn.application.classpath requires client to know service internals

[ https://issues.apache.org/jira/browse/MAPREDUCE-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718797#comment-13718797 ] Bikas Saha commented on MAPREDUCE-5403: --- why are we using a literal string inste

[jira] [Commented] (MAPREDUCE-5403) yarn.application.classpath requires client to know service internals

[ https://issues.apache.org/jira/browse/MAPREDUCE-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718806#comment-13718806 ] Bikas Saha commented on MAPREDUCE-5403: --- Jira also needs to be moved to YARN pro

[jira] [Commented] (MAPREDUCE-5352) Optimize node local splits generated by CombineFileInputFormat

[ https://issues.apache.org/jira/browse/MAPREDUCE-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725893#comment-13725893 ] Bikas Saha commented on MAPREDUCE-5352: --- blockToNodes doesnt look like it needs

[jira] [Commented] (MAPREDUCE-5352) Optimize node local splits generated by CombineFileInputFormat

[ https://issues.apache.org/jira/browse/MAPREDUCE-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726127#comment-13726127 ] Bikas Saha commented on MAPREDUCE-5352: --- Sounds good. +1. > Opt

[jira] [Commented] (MAPREDUCE-5311) Replace SLOTS_MILLIS counters with MEM_MILLIS

[ https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740037#comment-13740037 ] Bikas Saha commented on MAPREDUCE-5311: --- The uber problem seems that MR happens

[jira] [Commented] (MAPREDUCE-5311) Replace SLOTS_MILLIS counters with MEM_MILLIS

[ https://issues.apache.org/jira/browse/MAPREDUCE-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740733#comment-13740733 ] Bikas Saha commented on MAPREDUCE-5311: --- Let me understand this a bit. There is

[jira] [Commented] (MAPREDUCE-5471) Succeed job tries to restart after RMrestart

[ https://issues.apache.org/jira/browse/MAPREDUCE-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746644#comment-13746644 ] Bikas Saha commented on MAPREDUCE-5471: --- +1 to Jason's comments. I dont underst

[jira] [Commented] (MAPREDUCE-5471) Succeed job tries to restart after RMrestart

[ https://issues.apache.org/jira/browse/MAPREDUCE-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746917#comment-13746917 ] Bikas Saha commented on MAPREDUCE-5471: --- [~yeshavora] Can you please attach the

[jira] [Commented] (MAPREDUCE-5471) Succeed job tries to restart after RMrestart

[ https://issues.apache.org/jira/browse/MAPREDUCE-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746915#comment-13746915 ] Bikas Saha commented on MAPREDUCE-5471: --- Even storing a persistent flag is not e

[jira] [Commented] (MAPREDUCE-5489) MR Job hungs when any NM is blacklisted after RMrestart

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755336#comment-13755336 ] Bikas Saha commented on MAPREDUCE-5489: --- how is this related to rm restart?

[jira] [Commented] (MAPREDUCE-5489) MR Job hangs when any NM is blacklisted after RMrestart

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757011#comment-13757011 ] Bikas Saha commented on MAPREDUCE-5489: --- Can you please update the title to make

[jira] [Commented] (MAPREDUCE-5497) '5s sleep' in MRAppMaster.shutDownJob is only needed before stopping ClientService

[ https://issues.apache.org/jira/browse/MAPREDUCE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764008#comment-13764008 ] Bikas Saha commented on MAPREDUCE-5497: --- Does the client service return job succ

[jira] [Commented] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769936#comment-13769936 ] Bikas Saha commented on MAPREDUCE-5505: --- Can we make either 1) JobImpl go to suc

[jira] [Commented] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770462#comment-13770462 ] Bikas Saha commented on MAPREDUCE-5505: --- Thats right. MRClientProtocolService sh

[jira] [Commented] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771203#comment-13771203 ] Bikas Saha commented on MAPREDUCE-5505: --- I dont think making jobimpl aware of al

[jira] [Updated] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5505: -- Status: Open (was: Patch Available) > Clients should be notified job finished only aft

[jira] [Commented] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772301#comment-13772301 ] Bikas Saha commented on MAPREDUCE-5505: --- Are we sure that previous state is alwa

[jira] [Commented] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772484#comment-13772484 ] Bikas Saha commented on MAPREDUCE-5505: --- We could do that but lets leave it out

[jira] [Commented] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776801#comment-13776801 ] Bikas Saha commented on MAPREDUCE-5505: --- Instead of calling rememberLastState in

[jira] [Updated] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5505: -- Fix Version/s: 2.1.2-beta > Clients should be notified job finished only after job succ

[jira] [Updated] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5505: -- Priority: Critical (was: Major) > Clients should be notified job finished only after j

[jira] [Updated] (MAPREDUCE-5505) Clients should be notified job finished only after job successfully unregistered

[ https://issues.apache.org/jira/browse/MAPREDUCE-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5505: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Avail

[jira] [Updated] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5489: -- Status: Open (was: Patch Available) > MR jobs hangs as it does not use the node-blacklisti

[jira] [Commented] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784898#comment-13784898 ] Bikas Saha commented on MAPREDUCE-5489: --- By the time we clear, could new entries

[jira] [Commented] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785439#comment-13785439 ] Bikas Saha commented on MAPREDUCE-5489: --- Typos + assertBlackListAddtionsAndRemov

[jira] [Updated] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5489: -- Priority: Critical (was: Major) > MR jobs hangs as it does not use the node-blacklisting f

[jira] [Commented] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785546#comment-13785546 ] Bikas Saha commented on MAPREDUCE-5489: --- Looks good +1. > MR jobs hangs as it d

[jira] [Updated] (MAPREDUCE-5559) Reconsidering the policy of ignoring the blacklist after reaching the threshold

[ https://issues.apache.org/jira/browse/MAPREDUCE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5559: -- Summary: Reconsidering the policy of ignoring the blacklist after reaching the threshold (

[jira] [Updated] (MAPREDUCE-5559) Reconsidering the policy of ignoring the blacklist after reaching the threshold

[ https://issues.apache.org/jira/browse/MAPREDUCE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5559: -- Fix Version/s: 2.1.2-beta > Reconsidering the policy of ignoring the blacklist after reachi

[jira] [Updated] (MAPREDUCE-5559) Reconsidering the policy of ignoring the blacklist after reaching the threshold

[ https://issues.apache.org/jira/browse/MAPREDUCE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5559: -- Fix Version/s: (was: 2.1.2-beta) 2.3.0 > Reconsidering the policy of

[jira] [Updated] (MAPREDUCE-5559) Reconsidering the policy of ignoring the blacklist after reaching the threshold

[ https://issues.apache.org/jira/browse/MAPREDUCE-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5559: -- Affects Version/s: 2.1.1-beta > Reconsidering the policy of ignoring the blacklist after re

[jira] [Updated] (MAPREDUCE-5489) MR jobs hangs as it does not use the node-blacklisting feature in RM requests

[ https://issues.apache.org/jira/browse/MAPREDUCE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-5489: -- Resolution: Fixed Fix Version/s: 2.1.2-beta Hadoop Flags: Reviewed St

[jira] [Commented] (MAPREDUCE-5616) MR Client-AppMaster RPC max retries on socket timeout is too high.

[ https://issues.apache.org/jira/browse/MAPREDUCE-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822129#comment-13822129 ] Bikas Saha commented on MAPREDUCE-5616: --- Looks like a fairly straightforward cha

[jira] [Resolved] (MAPREDUCE-3755) Add the equivalent of JobStatus to end of JobHistory file

[ https://issues.apache.org/jira/browse/MAPREDUCE-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha resolved MAPREDUCE-3755. --- Resolution: Won't Fix Target Version/s: 2.0.0-alpha, 0.23.3, 3.0.0 (was: 0.23.3

[jira] [Commented] (MAPREDUCE-3755) Add the equivalent of JobStatus to end of JobHistory file

[ https://issues.apache.org/jira/browse/MAPREDUCE-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977062#comment-13977062 ] Bikas Saha commented on MAPREDUCE-3755: --- Probably not. We may close this. > Add

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Status: Patch Available (was: Open) > MR AM should act on the nodes liveliness informa

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Attachment: MAPREDUCE-3921-4.patch New patch with latest synced changes from trunk.

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Status: Open (was: Patch Available) > MR AM should act on the nodes liveliness informa

[jira] [Commented] (MAPREDUCE-3899) Locking not correct in org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(AllocateRequest request)

[ https://issues.apache.org/jira/browse/MAPREDUCE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260015#comment-13260015 ] Bikas Saha commented on MAPREDUCE-3899: --- Yeah. Those complications have left thi

[jira] [Updated] (MAPREDUCE-3899) Locking not correct in org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService.allocate(AllocateRequest request)

[ https://issues.apache.org/jira/browse/MAPREDUCE-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3899: -- Status: Open (was: Patch Available) > Locking not correct in > org.apache.hadoop.yarn

[jira] [Commented] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260834#comment-13260834 ] Bikas Saha commented on MAPREDUCE-3921: --- bq.Does 'node unhealthy' need to be tre

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Attachment: MAPREDUCE-3921-5.patch > MR AM should act on the nodes liveliness informati

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Status: Open (was: Patch Available) > MR AM should act on the nodes liveliness informa

[jira] [Commented] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260860#comment-13260860 ] Bikas Saha commented on MAPREDUCE-3921: --- added new patch for comments above.

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Status: Patch Available (was: Open) > MR AM should act on the nodes liveliness informa

[jira] [Commented] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261127#comment-13261127 ] Bikas Saha commented on MAPREDUCE-3921: --- I see what you are saying about fetch f

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Status: Open (was: Patch Available) > MR AM should act on the nodes liveliness informa

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Attachment: MAPREDUCE-3921-6.patch Review comments fixed. > MR AM should a

[jira] [Commented] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261167#comment-13261167 ] Bikas Saha commented on MAPREDUCE-3921: --- I will change the map to store Containe

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Attachment: MAPREDUCE-3921-7.patch Changed assignedRequests maps to use Container as the va

[jira] [Updated] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3921: -- Status: Patch Available (was: Open) > MR AM should act on the nodes liveliness informa

[jira] [Commented] (MAPREDUCE-3921) MR AM should act on the nodes liveliness information when nodes go up/down/unhealthy

[ https://issues.apache.org/jira/browse/MAPREDUCE-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261843#comment-13261843 ] Bikas Saha commented on MAPREDUCE-3921: --- Here is how I read TaskAttemptCompleted

[jira] [Created] (MAPREDUCE-4201) Getting PID not working on Windows. Termination of Task/TaskJVM's not working

Bikas Saha created MAPREDUCE-4201: - Summary: Getting PID not working on Windows. Termination of Task/TaskJVM's not working Key: MAPREDUCE-4201 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4201

[jira] [Updated] (MAPREDUCE-4201) Getting PID not working on Windows. Termination of Task/TaskJVM's not working

[ https://issues.apache.org/jira/browse/MAPREDUCE-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-4201: -- Attachment: MAPREDUCE-4201.patch patch addresses the issues. Using windows built in tasklis

[jira] [Created] (MAPREDUCE-4203) Create equivalent of ProcfsBasedProcessTree for Windows

Bikas Saha created MAPREDUCE-4203: - Summary: Create equivalent of ProcfsBasedProcessTree for Windows Key: MAPREDUCE-4203 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4203 Project: Hadoop Map/Re

[jira] [Created] (MAPREDUCE-4204) Refactor ProcfsBasedProcessTree to make the resource collection object pluggable

Bikas Saha created MAPREDUCE-4204: - Summary: Refactor ProcfsBasedProcessTree to make the resource collection object pluggable Key: MAPREDUCE-4204 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4204

[jira] [Updated] (MAPREDUCE-4204) Refactor ProcfsBasedProcessTree to make the resource collection object pluggable

[ https://issues.apache.org/jira/browse/MAPREDUCE-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-4204: -- Attachment: MAPREDUCE-4204.patch Refactor patch. Replaces ProcfsBasedProcessTree with an ab

[jira] [Commented] (MAPREDUCE-4204) Refactor ProcfsBasedProcessTree to make the resource collection object pluggable

[ https://issues.apache.org/jira/browse/MAPREDUCE-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263844#comment-13263844 ] Bikas Saha commented on MAPREDUCE-4204: --- I am not quite sure about replacing Res

[jira] [Updated] (MAPREDUCE-4204) Refactor ProcfsBasedProcessTree to make the resource collection object pluggable

[ https://issues.apache.org/jira/browse/MAPREDUCE-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-4204: -- Attachment: MAPREDUCE-4204-1.patch Tiny diff from previous one to remove unneeded methods i

[jira] [Commented] (MAPREDUCE-4204) Refactor ProcfsBasedProcessTree to make the resource collection object pluggable

[ https://issues.apache.org/jira/browse/MAPREDUCE-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265078#comment-13265078 ] Bikas Saha commented on MAPREDUCE-4204: --- The plan is to eventually merge this ba

[jira] [Commented] (MAPREDUCE-4213) nodemanager should cleanup running containers when shutdown

[ https://issues.apache.org/jira/browse/MAPREDUCE-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265942#comment-13265942 ] Bikas Saha commented on MAPREDUCE-4213: --- Once this jira is done, in which scenar

[jira] [Commented] (MAPREDUCE-4101) nodemanager depends on /bin/bash

[ https://issues.apache.org/jira/browse/MAPREDUCE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267638#comment-13267638 ] Bikas Saha commented on MAPREDUCE-4101: --- Do you have a jira for the pluggable pr

[jira] [Commented] (MAPREDUCE-4101) nodemanager depends on /bin/bash

[ https://issues.apache.org/jira/browse/MAPREDUCE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267763#comment-13267763 ] Bikas Saha commented on MAPREDUCE-4101: --- I assume you mean to do that when that

[jira] [Updated] (MAPREDUCE-3958) RM: Remove RMNodeState and replace it with NodeState

[ https://issues.apache.org/jira/browse/MAPREDUCE-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-3958: -- Attachment: MAPREDUCE-3958-3.patch refreshing patch after latest pull. > R

[jira] [Commented] (MAPREDUCE-3958) RM: Remove RMNodeState and replace it with NodeState

[ https://issues.apache.org/jira/browse/MAPREDUCE-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268589#comment-13268589 ] Bikas Saha commented on MAPREDUCE-3958: --- Thanks Robert! > RM: R

[jira] [Updated] (MAPREDUCE-4203) Create equivalent of ProcfsBasedProcessTree for Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-4203: -- Attachment: MAPREDUCE-4203.patch test.cpp Initial patch with refactorings/n

[jira] [Commented] (MAPREDUCE-4233) NPE can happen in RMNMNodeInfo.

[ https://issues.apache.org/jira/browse/MAPREDUCE-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270634#comment-13270634 ] Bikas Saha commented on MAPREDUCE-4233: --- Does this happen because a node got add

[jira] [Commented] (MAPREDUCE-4252) MR2 job never completes with 1 pending task

[ https://issues.apache.org/jira/browse/MAPREDUCE-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274804#comment-13274804 ] Bikas Saha commented on MAPREDUCE-4252: --- I hesitate at the idea of introducing m

[jira] [Commented] (MAPREDUCE-4252) MR2 job never completes with 1 pending task

[ https://issues.apache.org/jira/browse/MAPREDUCE-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13275995#comment-13275995 ] Bikas Saha commented on MAPREDUCE-4252: --- @Sid ,thanks for clarifying. @Tom, Let

[jira] [Created] (MAPREDUCE-4259) TestDatanodeBlockScanner and TestReplication fail intermittently on Windows

Bikas Saha created MAPREDUCE-4259: - Summary: TestDatanodeBlockScanner and TestReplication fail intermittently on Windows Key: MAPREDUCE-4259 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4259 P

[jira] [Moved] (MAPREDUCE-4260) Investigate use of JobObject to spawn tasks on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha moved HADOOP-8401 to MAPREDUCE-4260: --- Affects Version/s: (was: 1.0.0) 1.0.0

[jira] [Updated] (MAPREDUCE-4260) Investigate use of JobObject to spawn tasks on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-4260: -- Description: Currently, the Windows version spawns the task as a normal cmd shell from whic

[jira] [Created] (MAPREDUCE-4263) Use taskkill /T to terminate tasks on Windows

Bikas Saha created MAPREDUCE-4263: - Summary: Use taskkill /T to terminate tasks on Windows Key: MAPREDUCE-4263 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4263 Project: Hadoop Map/Reduce

[jira] [Commented] (MAPREDUCE-4204) Refactor ProcfsBasedProcessTree to make the resource collection object pluggable

[ https://issues.apache.org/jira/browse/MAPREDUCE-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276894#comment-13276894 ] Bikas Saha commented on MAPREDUCE-4204: --- Trunk versions will be prepared once th

[jira] [Updated] (MAPREDUCE-4260) Investigate use of JobObject to spawn tasks on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated MAPREDUCE-4260: -- Attachment: MAPREDUCE-4260.patch test.cpp Initial patch that looks like it

  1   2   3   4   >