mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Park (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7100) Missing AGENT_REMOVED event in event stream
Date Thu, 27 Apr 2017 03:25:04 GMT

    [ https://issues.apache.org/jira/browse/MESOS-7100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985925#comment-15985925
] 

Michael Park commented on MESOS-7100:
-------------------------------------

Pushing the target to 1.4.

> 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
>              Labels: mesosphere
>
> 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)

Mime
View raw message