[
https://issues.apache.org/jira/browse/SLIDER-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711704#comment-14711704
]
Gour Saha commented on SLIDER-868:
----------------------------------
Thanks [~mding]. I think YARN-4080 rightly captures the requirements of what is
required from YARN for this feature in Slider.
The only thing which I wanted to highlight is that in this bug, Slider is
expecting a certain level of *guaranteed* resource reservation commitment from
YARN. Hence after the request is made, Slider would expect some sort of
feedback from YARN about the level of guarantee at the given point in future
time (like say CONFIRMED, POSSIBLE_BUT_NOT_CONFIRMED, NOT_POSSIBLE for lack of
better terms). Slider can then take certain actions based on the feedback, say
confirm the long running service owner that his/her application is doing fine
in auto pilot mode or that at a given point in future time the skyline is not
guaranteed due to resource constraint, so that the app owner can take
appropriate actions if required, etc.
Do you think YARN-4080 captures this feedback loop as well?
> Ability to put a Slider application on cruise control
> -----------------------------------------------------
>
> Key: SLIDER-868
> URL: https://issues.apache.org/jira/browse/SLIDER-868
> Project: Slider
> Issue Type: New Feature
> Components: agent, app-package, appmaster
> Affects Versions: Slider 0.70
> Reporter: Gour Saha
>
> You create a Slider application package, deploy it to a YARN cluster and
> manage it. From the management perspective it is primarily flexing. Based on
> needs (and the architecture of the application) you grow or shrink specific
> components of your long running application from time to time. Of course you
> can set some constraints like affinity, anti-affinity, and strict placement
> (for data locality or other reasons). Some of these are handled very well by
> Slider, others are best efforts.
> However long running applications have an inherent need to be auto (or even
> self) managed. This can be achieved by a custom management tool, interacting
> with Slider client based on constant feedback on the health of the
> application (metrics, alerts, etc.). This is primarily reactive management.
> There is also proactive management, where the application owner is aware of
> the usage pattern of the application over time. For example, a financial
> application usage peaks between 8am to 4pm Mon to Sat (local time), and slows
> down at other times. A tax application usage peaks for a few months prior to
> April 15 and then slows down for several months. Certain healthcare
> applications peak during flu season. You get the point!
> It should be possible to declaratively define such an application usage
> skyline, which can be fed to Slider and put an application on cruise control.
> The specification can be modified dynamically and Slider should honor the
> modified version for (reasonably acceptable) future state of the application.
> This kind of feature would need support from YARN. There should be a way for
> Slider to provide details to YARN for guaranteed future capacity planning.
> Note: It is the negotiation that Slider will do with YARN, to ensure the
> guaranteed (or best effort) future capacity planning to maintain the skyline
> is what makes this pro-active management useful. Nothing stops an application
> owner to write pro-active tools to manage a skyline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
