You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/08/12 03:26:20 UTC
[jira] [Updated] (MESOS-6034) Adding Subscribe and event stream to
agent Operator API
[ https://issues.apache.org/jira/browse/MESOS-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anand Mazumdar updated MESOS-6034:
----------------------------------
Description:
Use case:
We have local daemons at every machine in the cluster. They often need to know what tasks is running at the local host and perform operations.
Right now they can only poll `/state` endpoint or operator API. Let them able to subscribe task changes on the agent seems a good improvement.
The only way to be actively notified otherwise is to implement part of all logic as a hook, but doing this directly in agent is better and easier for everyone.
For MVP, something similar to current master API's `TASK_ADDED` and `TASK_STATUS` seems a pretty good starter.
was:
Use case:
We have local daemons at every machine in the cluster. They often need to know what tasks is running at the local host and perform operations.
Right now they can only poll `/state` endpoint or operator API. Let them able to subscribe task changes on the agent seems a good improvement.
The only to be actively notified otherwise is to implement part of all logic as a hook, but I think doing this directly in agent is better and easier for everyone.
For MPV, something similar to current master API's `TASK_ADDED` and `TASK_STATUS` seems pretty good starter.
> Adding Subscribe and event stream to agent Operator API
> -------------------------------------------------------
>
> Key: MESOS-6034
> URL: https://issues.apache.org/jira/browse/MESOS-6034
> Project: Mesos
> Issue Type: Improvement
> Components: HTTP API
> Reporter: Zhitao Li
>
> Use case:
> We have local daemons at every machine in the cluster. They often need to know what tasks is running at the local host and perform operations.
> Right now they can only poll `/state` endpoint or operator API. Let them able to subscribe task changes on the agent seems a good improvement.
> The only way to be actively notified otherwise is to implement part of all logic as a hook, but doing this directly in agent is better and easier for everyone.
> For MVP, something similar to current master API's `TASK_ADDED` and `TASK_STATUS` seems a pretty good starter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)