mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-7721) Master's agent removal rate limit also applies to agent unreachability.
Date Mon, 26 Jun 2017 05:19:00 GMT

     [ https://issues.apache.org/jira/browse/MESOS-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Mahler updated MESOS-7721:
-----------------------------------
    Priority: Critical  (was: Major)

> Master's agent removal rate limit also applies to agent unreachability.
> -----------------------------------------------------------------------
>
>                 Key: MESOS-7721
>                 URL: https://issues.apache.org/jira/browse/MESOS-7721
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>            Reporter: Benjamin Mahler
>            Priority: Critical
>
> Currently, the implementation of partition awareness re-uses the {{--agent_removal_rate_limit}}
when marking agents as unreachable. This means that partition aware frameworks are exposed
to the agent removal rate limit, when they rather would like to see the information immediately
and impose their own rate limiting.
> Rather than waiting for non-partition-aware support to be removed (that may not occur
for a long time) per MESOS-5948, we should instead fix the implementation so that unreachability
does not get gated behind the agent removal rate limiting.
> Marking this as a bug since from the user's perspective it doesn't behave as expected,
there should be a separate flag for rate limiting unreachability marking, but likely unreachability
marking does not need rate limiting, since the intention was for frameworks to impose their
own rate limiting for replacing tasks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message