[
https://issues.apache.org/jira/browse/SLIDER-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148211#comment-14148211
]
ASF subversion and git services commented on SLIDER-453:
--------------------------------------------------------
Commit 94df22c92e48859fbc4b3a560981a6a70cc64b54 in incubator-slider's branch
refs/heads/feature/SLIDER-149_Support_a_YARN_service_registry from
[[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=94df22c ]
SLIDER-453 AM queue processing goes live before init complete
> AM queue processing goes live before init complete
> --------------------------------------------------
>
> Key: SLIDER-453
> URL: https://issues.apache.org/jira/browse/SLIDER-453
> Project: Slider
> Issue Type: Bug
> Components: appmaster
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> The AM queue executor goes live before AM startup; if external events come in
> (e.g. container completion reports), they aren't handled right. This is a
> re-emergence of a sync-startup problem seen before on restarted containers,
> as container completion comes in before cluster state buildup complete.
> Despite the sync block around app state, the extended AM is vulnerable to the
> same race condition.
> Fix: don't start the queues until the last moment...the events will just get
> scheduled awaiting that moment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
