You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/05/30 20:53:02 UTC
[jira] [Updated] (SLIDER-84) switch from thread-based container
launch to Futures
[ https://issues.apache.org/jira/browse/SLIDER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated SLIDER-84:
---------------------------------
Sprint: slider may 2
> switch from thread-based container launch to Futures
> ----------------------------------------------------
>
> Key: SLIDER-84
> URL: https://issues.apache.org/jira/browse/SLIDER-84
> Project: Slider
> Issue Type: Improvement
> Components: appmaster
> Affects Versions: Slider 0.30
> Reporter: Steve Loughran
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The role launching code in the AM is based off Distributed Shell: uses a thread per launched container. This will have scale limits when launching a very large cluster if the assignments all come in near-simultaneously.
> Switching to a Java futures model would allow the AM to deploy via an executor that limited the number of operations active; possibly also support a better shutdown
--
This message was sent by Atlassian JIRA
(v6.2#6252)