[
https://issues.apache.org/jira/browse/MESOS-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904975#comment-14904975
]
Niklas Quarfot Nielsen commented on MESOS-2642:
-----------------------------------------------
Draft document for the design:
https://docs.google.com/document/d/1EfBESIeqJvj_hVGz_oIVHDnJiQtFASKwrtAIQgL0x0k/edit#heading=h.pldb4jdil4u1
Major changes coming up are the notion of SLI (Service Level Indicator) vs SLO
(The target; Service Level Objective).
We see two themes:
- How to produce/export the SLI and SLO from the framework and it's tasks
- How to consume them from the oversubscription modules and external
monitoring solutions
We have highlighted a few ways of doing this, and will follow up with a more
solidified architecture proposal soon (will be in the same document). Stay tuned
> Provide a way for frameworks to report their SLO per executor or task.
> ----------------------------------------------------------------------
>
> Key: MESOS-2642
> URL: https://issues.apache.org/jira/browse/MESOS-2642
> Project: Mesos
> Issue Type: Story
> Reporter: Niklas Quarfot Nielsen
>
> In context of oversubscription, but useful as a general feature; allowing
> frameworks to report their SLO (to which degree, if it is violated, etc)
> allows for better monitoring, scheduling and more aggressive oversubscription
> strategies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
