[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413085#comment-15413085
]
sandflee commented on YARN-5483:
thanks [~rohithsharma], I don't think YARN-5262 breaks thi
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5483:
---
Attachment: YARN-5483.03.patch
> Optimize RMAppAttempt#pullJustFinishedContainers
> ---
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413177#comment-15413177
]
sandflee commented on YARN-5483:
update the patch, rename keepContainersAcressAttempts to
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413570#comment-15413570
]
sandflee commented on YARN-5453:
any reason to limit resource demand to maxResource? cc [~
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413744#comment-15413744
]
sandflee commented on YARN-5453:
thanks for your explain,
bq. the scheduler allows allocat
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5483:
---
Attachment: YARN-5483.04.patch
> Optimize RMAppAttempt#pullJustFinishedContainers
> ---
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413844#comment-15413844
]
sandflee commented on YARN-5483:
1, update a new patch to minor fix diamond operator issues
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413857#comment-15413857
]
sandflee commented on YARN-5483:
without YARN-5262 , there will be too many FINISHED_CONTAI
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413844#comment-15413844
]
sandflee edited comment on YARN-5483 at 8/9/16 5:08 PM:
1, update a
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5483:
---
Attachment: YARN-5483-branch-2.6.patch
YARN-5483-branch-2.7.patch
> Optimize RMAppAttempt#pullJ
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5483:
---
Attachment: YARN-5483-branch-2.7.patch.02
YARN-5483-branch-2.6.patch.02
> Optimize RMAppAttempt
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414431#comment-15414431
]
sandflee commented on YARN-5483:
update the patch.
> Optimize RMAppAttempt#pullJustFinishe
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5453:
---
Attachment: YARN-5453.02.patch
> FairScheduler#update may skip update demand resource of child queue/app if
>
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414452#comment-15414452
]
sandflee commented on YARN-5453:
agree, update the patch as you suggested.
> FairScheduler
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5453:
---
Attachment: YARN-5453.03.patch
> FairScheduler#update may skip update demand resource of child queue/app if
>
[
https://issues.apache.org/jira/browse/YARN-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416202#comment-15416202
]
sandflee commented on YARN-5483:
thanks [~jlowe] [~templedf] [~jianhe] and [~rohithsharma]
[
https://issues.apache.org/jira/browse/YARN-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628654#comment-15628654
]
sandflee commented on YARN-5276:
Thanks [~miklos.szeg...@cloudera.com] for your detailed re
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5453:
---
Attachment: YARN-5453.05.patch
> FairScheduler#update may skip update demand resource of child queue/app if
>
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15642979#comment-15642979
]
sandflee commented on YARN-5453:
thanks [~kasha], patch updated.
> FairScheduler#update ma
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.09.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643429#comment-15643429
]
sandflee commented on YARN-5375:
update the patch to fix TestFairScheduler, adding drainEve
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653433#comment-15653433
]
sandflee commented on YARN-5453:
thanks [~kasha] for review and commit !
> FairScheduler#
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663934#comment-15663934
]
sandflee commented on YARN-5375:
thanks [~rohithsharma], TestTokenClientRMService test fail
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.11.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666843#comment-15666843
]
sandflee commented on YARN-5375:
update the patch to invoke drainEventsImplicitly() at the
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.12.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.12.new.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test fail
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669662#comment-15669662
]
sandflee commented on YARN-5375:
update YARN-5375.12.new.patch to trigger jenkins
> invoke
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672354#comment-15672354
]
sandflee commented on YARN-5375:
Thanks Rohith,Sunil, Varun for review and commit ! after t
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee reassigned YARN-5895:
--
Assignee: sandflee
> TestRMRestart#testFinishedAppRemovalAfterRMRestart is still flakey
> -
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672377#comment-15672377
]
sandflee commented on YARN-5895:
thanks [~wilfreds] for reporting this, before YARN-5375, d
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672377#comment-15672377
]
sandflee edited comment on YARN-5895 at 11/17/16 1:48 AM:
--
thanks
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672483#comment-15672483
]
sandflee commented on YARN-5895:
yes.
> TestRMRestart#testFinishedAppRemovalAfterRMRestar
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672602#comment-15672602
]
sandflee commented on YARN-5895:
yes, I think there are two main places not drain Events:
1
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672604#comment-15672604
]
sandflee commented on YARN-5895:
will do
> TestRMRestart#testFinishedAppRemovalAfterRMRest
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672967#comment-15672967
]
sandflee commented on YARN-5375:
yes, to keep the patch simple, not replace MemoryRMStateSt
[
https://issues.apache.org/jira/browse/YARN-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672972#comment-15672972
]
sandflee commented on YARN-5548:
agree, and maybe we could try to replace all MemoryStateS
[
https://issues.apache.org/jira/browse/YARN-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672972#comment-15672972
]
sandflee edited comment on YARN-5548 at 11/17/16 6:54 AM:
--
agree,
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee resolved YARN-5895.
Resolution: Duplicate
> TestRMRestart#testFinishedAppRemovalAfterRMRestart is still flakey
> ---
[
https://issues.apache.org/jira/browse/YARN-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672982#comment-15672982
]
sandflee commented on YARN-5895:
I'm ok, close it with dup
> TestRMRestart#testFinishedApp
sandflee created YARN-5896:
--
Summary: add drainEvents to MockAM to reduce test failure
Key: YARN-5896
URL: https://issues.apache.org/jira/browse/YARN-5896
Project: Hadoop YARN
Issue Type: Improvemen
sandflee created YARN-5897:
--
Summary: using drainEvent to replace sleep-wait in
MockRM#waitForState
Key: YARN-5897
URL: https://issues.apache.org/jira/browse/YARN-5897
Project: Hadoop YARN
Issue Ty
[
https://issues.apache.org/jira/browse/YARN-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee reassigned YARN-5897:
--
Assignee: sandflee
> using drainEvent to replace sleep-wait in MockRM#waitForState
> ---
[
https://issues.apache.org/jira/browse/YARN-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673309#comment-15673309
]
sandflee commented on YARN-5898:
had AM ever restarted?
> Container can not stop, because
[
https://issues.apache.org/jira/browse/YARN-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15678114#comment-15678114
]
sandflee commented on YARN-5911:
thanks [~varun_saxena], one minor comment:
if events not d
[
https://issues.apache.org/jira/browse/YARN-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683146#comment-15683146
]
sandflee commented on YARN-5911:
seems no need to keep var stopped in DrainDispatcher?
> D
[
https://issues.apache.org/jira/browse/YARN-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684917#comment-15684917
]
sandflee commented on YARN-5911:
sorry, not noticed it was removed in the patch,
patch LGT
[
https://issues.apache.org/jira/browse/YARN-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419643#comment-15419643
]
sandflee commented on YARN-5393:
YARN-5375 aims to add drainAllEvents to waitForState to re
[
https://issues.apache.org/jira/browse/YARN-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419674#comment-15419674
]
sandflee commented on YARN-4743:
bq. I think the root cause is NodeAvailableResourceCompara
[
https://issues.apache.org/jira/browse/YARN-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419963#comment-15419963
]
sandflee commented on YARN-5479:
seems no need to compute minShare/isNeed/MinShareRatio/Use
[
https://issues.apache.org/jira/browse/YARN-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420796#comment-15420796
]
sandflee commented on YARN-5479:
will do, thx
> FairScheduler: Scheduling performance impr
[
https://issues.apache.org/jira/browse/YARN-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee reassigned YARN-5521:
--
Assignee: sandflee
> TestCapacityScheduler#testKillAllAppsInQueue fails randomly
> -
[
https://issues.apache.org/jira/browse/YARN-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421202#comment-15421202
]
sandflee commented on YARN-5521:
thanks [~bibinchundatt], seems caused by app went to KILLE
[
https://issues.apache.org/jira/browse/YARN-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5521:
---
Attachment: YARN-5521.01.patch
> TestCapacityScheduler#testKillAllAppsInQueue fails randomly
>
[
https://issues.apache.org/jira/browse/YARN-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421781#comment-15421781
]
sandflee commented on YARN-5521:
Thanks [~varun_saxena], [~sunilg], [~bibinchundatt]
> Tes
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.06.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures
sandflee created YARN-5526:
--
Summary: DrainDispacher#ServiceStop blocked if
setDrainEventsOnStop invoked
Key: YARN-5526
URL: https://issues.apache.org/jira/browse/YARN-5526
Project: Hadoop YARN
Iss
[
https://issues.apache.org/jira/browse/YARN-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422691#comment-15422691
]
sandflee commented on YARN-5526:
DrainDispacher override AsyncDispacher#CreateThead, and As
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422698#comment-15422698
]
sandflee commented on YARN-5375:
1, replace rmStateStore#AsyncDispatcher with DrainDispatch
[
https://issues.apache.org/jira/browse/YARN-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5526:
---
Attachment: YARN-5526.01.patch
> DrainDispacher#ServiceStop blocked if setDrainEventsOnStop invoked
> -
[
https://issues.apache.org/jira/browse/YARN-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5526:
---
Attachment: YARN-5526.02.patch
> DrainDispacher#ServiceStop blocked if setDrainEventsOnStop invoked
> -
[
https://issues.apache.org/jira/browse/YARN-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423746#comment-15423746
]
sandflee commented on YARN-5526:
Thanks [~varun_saxena], that's more reasonable! update th
[
https://issues.apache.org/jira/browse/YARN-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426170#comment-15426170
]
sandflee commented on YARN-5526:
thanks [~varun_saxena] for suggestion and review !
> Drai
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431785#comment-15431785
]
sandflee commented on YARN-5375:
Thanks [~varun_saxena], yes this will reduce the change f
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434024#comment-15434024
]
sandflee commented on YARN-5375:
also see YARN-5043, if StateStore Event is not processed,
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434730#comment-15434730
]
sandflee commented on YARN-5375:
bq. One comment from earlier patch in MockRM is need to ta
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435099#comment-15435099
]
sandflee commented on YARN-5375:
thanks [~rohithsharma], even if we using the order rmDis
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.07-drain-statestore.patch
YARN-5375.07-sync-statestore.patch
> invoke Moc
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.07-sync-statestore.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to redu
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: (was: YARN-5375.07-sync-statestore.patch)
> invoke MockRM#drainEvents implicitly in MockRM meth
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1565#comment-1565
]
sandflee commented on YARN-5375:
thanks [~varun_saxena], [~sunilg], [~rohithsharma] for you
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1565#comment-1565
]
sandflee edited comment on YARN-5375 at 8/29/16 1:24 AM:
-
thanks [~
[
https://issues.apache.org/jira/browse/YARN-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15522338#comment-15522338
]
sandflee commented on YARN-5315:
{quote}
shutdownNow :
Attempts to stop all actively execut
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15522347#comment-15522347
]
sandflee commented on YARN-5375:
I'm ok for both method, any thought?
> invoke MockRM#drai
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15538216#comment-15538216
]
sandflee commented on YARN-5375:
Thanks [~rohithsharma] for your review !
bq. private vola
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5453:
---
Attachment: YARN-5453.04.patch
> FairScheduler#update may skip update demand resource of child queue/app if
>
[
https://issues.apache.org/jira/browse/YARN-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15551422#comment-15551422
]
sandflee commented on YARN-5453:
Hi, [~kasha], patch updated, failed test could run pass lo
[
https://issues.apache.org/jira/browse/YARN-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15559054#comment-15559054
]
sandflee commented on YARN-5362:
thanks [~Naganarasimha], I'll have a look.
> TestRMRestar
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601173#comment-15601173
]
sandflee commented on YARN-5375:
sorry for the delay, will do this in these days
> invoke
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5375:
---
Attachment: YARN-5375.08.patch
> invoke MockRM#drainEvents implicitly in MockRM methods to reduce test failures
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605288#comment-15605288
]
sandflee commented on YARN-5375:
update YARN-5375.08.patch to address the comment of [~rohi
[
https://issues.apache.org/jira/browse/YARN-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612189#comment-15612189
]
sandflee commented on YARN-5375:
Thanks [~rohithsharma], yes, MockRM#createSchedulerEventDi
[
https://issues.apache.org/jira/browse/YARN-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613741#comment-15613741
]
sandflee commented on YARN-5276:
Thanks for your comment, the patch just add some log info,
[
https://issues.apache.org/jira/browse/YARN-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-5276:
---
Attachment: YARN-5276.04.patch
> print more info when event queue is blocked
>
[
https://issues.apache.org/jira/browse/YARN-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626528#comment-14626528
]
sandflee commented on YARN-3327:
There is no logs any more, it's a long time and I just fix
sandflee created YARN-3987:
--
Summary: am container complete msg ack to NM once RM receive it
Key: YARN-3987
URL: https://issues.apache.org/jira/browse/YARN-3987
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-3987:
---
Attachment: YARN-3987.001.patch
> am container complete msg ack to NM once RM receive it
>
[
https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645136#comment-14645136
]
sandflee commented on YARN-3987:
yes, we set getKeepContainersAcrossApplicationAttempts tru
[
https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-3987:
---
Attachment: YARN-3987.002.patch
> am container complete msg ack to NM once RM receive it
>
[
https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645326#comment-14645326
]
sandflee commented on YARN-3987:
Yes the old AM container in NM aren't cleaned up. in our c
[
https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645341#comment-14645341
]
sandflee commented on YARN-3987:
AM crashes before it register to RM
> am container compl
[
https://issues.apache.org/jira/browse/YARN-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650644#comment-14650644
]
sandflee commented on YARN-4005:
seems there's no need to add to recentlyStoppedContainers,
sandflee created YARN-4020:
--
Summary: Exception happens while stopContainer in AM
Key: YARN-4020
URL: https://issues.apache.org/jira/browse/YARN-4020
Project: Hadoop YARN
Issue Type: Bug
sandflee created YARN-4040:
--
Summary: container complete msg should passed to AM,even if the
container is released.
Key: YARN-4040
URL: https://issues.apache.org/jira/browse/YARN-4040
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692709#comment-14692709
]
sandflee commented on YARN-2038:
I thought it's the same issue to YARN-3519, but it seems n
sandflee created YARN-4050:
--
Summary: NM event dispatcher may blocked by LogAggregationService
if NameNode is slow
Key: YARN-4050
URL: https://issues.apache.org/jira/browse/YARN-4050
Project: Hadoop YARN
sandflee created YARN-4051:
--
Summary: ContainerKillEvent is lost when container is In New
State and is recovering
Key: YARN-4051
URL: https://issues.apache.org/jira/browse/YARN-4051
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-4051:
---
Attachment: YARN-4051.01.patch
> ContainerKillEvent is lost when container is In New State and is recovering
>
[
https://issues.apache.org/jira/browse/YARN-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee resolved YARN-4040.
Resolution: Not A Problem
If AM release a container, the complete msg(released by AM) is stored by
RMAppAtte
[
https://issues.apache.org/jira/browse/YARN-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696433#comment-14696433
]
sandflee commented on YARN-3987:
Thanks [~jianhe]!
> am container complete msg ack to NM o
301 - 400 of 468 matches
Mail list logo
