[
https://issues.apache.org/jira/browse/MESOS-7100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860442#comment-15860442
]
Anand Mazumdar commented on MESOS-7100:
---------------------------------------
Thanks for reporting the issue.
{{AGENT_REMOVED}} is only sent when the agent is explicitly shutdown for
[maintenance|http://mesos.apache.org/documentation/latest/maintenance] or when
the agent is explicitly shutdown using the {{SIGUSR1}} signal.
We want to introduce the following events as you alluded to in the future:
- {{AGENT_UNREACHABLE}}: Sent when the agent gets partitioned away from the
master. In the example you mentioned above, the event would be sent by the
master when the agent fails health checks. (Default: 75 seconds)
- {{AGENT_UPDATED}}: Sent when the partitioned agent re-registers with the
master.
> Missing AGENT_REMOVED event in event stream
> -------------------------------------------
>
> Key: MESOS-7100
> URL: https://issues.apache.org/jira/browse/MESOS-7100
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API
> Affects Versions: 1.1.0
> Reporter: Haralds Ulmanis
> Priority: Minor
>
> I'm playing with event stream via HTTP endpoints.
> So - i got all events - SUBSCRIBED, TASK_ADDED, TASK_UPDATED, AGENT_ADDED
> except AGENT_REMOVED.
> What i do:
> Just stop agent or terminate server(if cloud).
> What i expect:
> Once it disappear from agent list (in mesos UI) to get event AGENT_REMOVED.
> Not sure about internals, maybe that is not correct event and agents got
> removed after some period, if they do not come up. But in general some event
> to indicate that agent went offline and not available would be good.
> If AGENT_REMOVED and AGENT_ADDED is kinda one-time events .. maybe something
> like: AGENT_CONNECTED/RECONNECTED, AGENT_LEAVE events would be great.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
