Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: <CAJA-XLPYuOL-k_zL7WYbYRrFRz8r=dyRk8FODV2JpxHbhYFAcg@mail.gmail.com>
References: <CAJA-XLPYuOL-k_zL7WYbYRrFRz8r=dyRk8FODV2JpxHbhYFAcg@mail.gmail.com>
From: Ilya Pronin <ipronin@twopensource.com>
Date: Fri, 1 Sep 2017 14:35:12 +0100
Message-ID: <CA+Xn3kxG9xv+rekcL6Yp8K1kF7mBPvyOZ1m89gk7bThdg18zOQ@mail.gmail.com>
Subject: Re: recovery_agent_removal_limit usage question?
To: dev@mesos.apache.org
Content-Type: multipart/alternative; boundary="001a114e393299f5c8055820d44f"
archived-at: Fri, 01 Sep 2017 13:35:24 -0000

--001a114e393299f5c8055820d44f
Content-Type: text/plain; charset="UTF-8"

Hey,

I'm not sure I understood your question correctly. But AFAIK
recovery_agent_removal_limit flag is intended to limit the number of agents
that will be marked unreachable after the re-registration timeout. If the
master sees that it has to remove more agents than the limit allows, it
will failover. Otherwise, agents that have not yet re-registered will be
marked unreachable at slave_removal_rate_limit. Here's the code that does
that:
https://github.com/apache/mesos/blob/master/src/master/master.cpp#L1946

We no longer shutdown agents if they try to re-register after being marked
unreachable, so we can safely remove those agents from the registry.
However, it still might be a good signal for the operator to investigate
why a lot of agents did not re-register.

On Fri, Sep 1, 2017 at 6:46 AM, tommy xiao <xiaods@gmail.com> wrote:

> toady i have a curious to read mesos source code for
> --recovery_agent_removal_limit. how does it working from source code. i
> have not found any useful logic for recovery_agent_removal_limit. anyone
> can do me favor?
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>

-- 
Ilya Pronin

--001a114e393299f5c8055820d44f--