Get desktop application:
View/edit binary Protocol Buffers messages
* Calls that can be sent to the v1 master API. A call is described using the standard protocol buffer "union" trick, see https://developers.google.com/protocol-buffers/docs/techniques#union.
Create persistent volumes on reserved resources. The request is forwarded asynchronously to the Mesos agent where the reserved resources are located. That asynchronous message may not be delivered or creating the volumes at the agent might fail. Volume creation can be verified by sending a `GET_VOLUMES` call.
Used in:
Destroy persistent volumes. The request is forwarded asynchronously to the Mesos agent where the reserved resources are located. That asynchronous message may not be delivered or destroying the volumes at the agent might fail. Volume deletion can be verified by sending a `GET_VOLUMES` call.
Used in:
Provides a snapshot of the current metrics tracked by the master.
Used in:
If set, `timeout` would be used to determines the maximum amount of time the API will take to respond. If the timeout is exceeded, some metrics may not be included in the response.
Grow a volume by an additional disk resource. NOTE: This is currently experimental and only for persistent volumes created on ROOT/PATH disks.
Used in:
`agent_id` must be set if `volume` is an agent-local resource, and must be unset if `volume` is an external resource.
Provides the file listing for a directory.
Used in:
Mark an agent as gone. This can be used by an operator to assert that the agent instance has failed and is never coming back (e.g., ephemeral instance from cloud provider). The master would shutdown the agent and send 'TASK_GONE_BY_OPERATOR' updates for all the running tasks. The persistent volumes/reservations on the agent won't be accessible anymore. NOTE: It is possible that the tasks might still be running if the operator's assertion was wrong and the agent was partitioned away from the master. The agent would be shutdown when it tries to reregister with the master when the partition heals.
Used in:
Reads data from a file.
Used in:
The path of file.
Initial offset in file to start reading from.
The maximum number of bytes to read. The read length is capped at 16 memory pages.
Used in:
Reserve resources dynamically on a specific agent.
Used in:
Sets the logging verbosity level for a specified duration. Mesos uses [glog](https://github.com/google/glog) for logging. The library only uses verbose logging which means nothing will be output unless the verbosity level is set (by default it's 0, libprocess uses levels 1, 2, and 3).
Used in:
The verbosity level.
The duration to keep verbosity level toggled. After this duration, the verbosity level of log would revert to the original level.
Sets the quota for resources to be used by a particular role.
Used in:
Shrink a volume by the size specified in the `subtract` field. NOTE: This is currently experimental and only for persistent volumes created on ROOT/PATH disks.
Used in:
`agent_id` must be set if `volume` is an agent-local resource, and must be unset if `volume` is an external resource.
See comments in `Value.Scalar` for maximum precision supported.
Starts the maintenance of the cluster, this would bring a set of machines down.
Used in:
Stops the maintenance of the cluster, this would bring a set of machines back up.
Used in:
Tears down a running framework by shutting down all tasks/executors and removing the framework.
Used in:
Used in:
If a call of type `Call::FOO` requires additional parameters they can be included in the corresponding `Call::Foo` message. Similarly, if a call receives a synchronous response it will be returned as a `Response` message of type `Response::FOO`. Currently all calls except `Call::SUBSCRIBE` receive synchronous responses; `Call::SUBSCRIBE` returns a streaming response of `Event`.
Retrieves the master's health status.
Retrieves the master's flag configuration.
Retrieves the master's version information.
See 'GetMetrics' below.
Retrieves the master's logging level.
See 'SetLoggingLevel' below.
See 'ReadFile' below.
Retrieves the information about all executors.
Retrieves the information about known operations.
Retrieves the information about all known tasks.
Retrieves the information about roles.
Retrieves the information about role weights.
Retrieves the master's information.
Subscribes the master to receive events.
See 'CreateVolumes' below.
See 'DestroyVolumes' below.
See 'GrowVolume' below.
See 'ShrinkVolume' below.
Retrieves the cluster's maintenance status.
Retrieves the cluster's maintenance schedule.
See 'UpdateMaintenanceSchedule' below.
See 'StartMaintenance' below.
See 'StopMaintenance' below.
See 'SetQuota' below.
See 'RemoveQuota' below.
See 'Teardown' below.
See 'MarkAgentGone' below.
Unreserve resources dynamically on a specific agent.
Used in:
Updates the cluster's maintenance schedule.
Used in:
Used in:
* Streaming response to `Call::SUBSCRIBE` made to the master.
Forwarded by the master when an agent becomes known to it. This can happen when an agent registered for the first time, or reregistered after a master failover.
Used in:
Forwarded by the master when an agent is removed. This can happen when the agent is scheduled for maintenance. NOTE: It's possible that an agent might become active once it has been removed, i.e. if the master has gc'ed its list of known "dead" agents. See MESOS-5965 for context.
Used in:
Forwarded by the master when a framework becomes known to it. This can happen when a new framework registers with the master.
Used in:
Forwarded by the master when a framework is removed. This can happen when a framework is explicitly teardown by the operator or if it fails to reregister with the master within the failover timeout.
Used in:
Forwarded by the master when a framework reregisters with the master upon a disconnection (network error) or upon a master failover.
Used in:
First event received when a client subscribes.
Used in:
Snapshot of the entire cluster state. Further updates to the cluster state are sent as separate events on the stream.
This value will be set if the master is sending heartbeats to subscribers. See the comment above on 'HEARTBEAT' for more details.
Forwarded by the master when a task becomes known to it. This can happen when a new task is launched by the scheduler or when the task becomes known to the master upon an agent (re-)registration after a failover.
Used in:
Forwarded by the master when an existing task transitions to a new state.
Used in:
This is the status of the task corresponding to the last status update acknowledged by the scheduler.
This is the latest state of the task according to the agent, which can be more recent than `status` above but intermediate state changes may be skipped if they happen faster than the scheduler can acknowledge them.
Used in:
See `Subscribed` below.
See `TaskAdded` below.
See `TaskUpdated` below.
See `AgentAdded` below.
See `AgentRemoved` below.
See `FrameworkAdded` below.
See `FrameworkUpdated` below.
See `FrameworkRemoved` below.
Periodic message sent by the master to the subscriber according to 'Subscribed.heartbeat_interval_seconds'. If the subscriber does not receive any events (including heartbeats) for an extended period of time (e.g., 5 x heartbeat_interval_seconds), it is likely that the connection is lost or there is a network partition. In that case, the subscriber should close the existing subscription connection and resubscribe using a backoff strategy.
* Synchronous responses for all calls (except Call::SUBSCRIBE) made to the v1 master API.
Used in:
,Registered agents.
Agents which are recovered from registry but not reregistered yet.
Used in:
, ,Total resources (including oversubscribed resources) the agent provides.
Used in:
Lists information about all the executors known to the master at the current time. Note that there might be executors unknown to the master running on partitioned or unsubscribed agents.
Used in:
,As of Mesos 1.3.0, this field is deprecated and will always be empty. TODO(neilc): Remove this field in Mesos 2.0.
Used in:
Contains the flag configuration of the master.
Used in:
Information about all the frameworks known to the master at the current time. Note that there might be frameworks unknown to the master running on partitioned or unsubscribed agents.
Used in:
,Frameworks that have subscribed with the master. Note that this includes frameworks that are disconnected and in the process of re-subscribing.
Frameworks that have been teared down.
This field previously contained frameworks that previously subscribed but haven't yet re-subscribed after a master failover. As of Mesos 1.2, this field will always be empty; recovered frameworks are now reported in the `frameworks` list with the `recovered` field set to true. TODO(neilc): Remove this field in Mesos 2.0.
Used in:
, ,If true, this framework was previously subscribed but hasn't yet re-subscribed after a master failover. Recovered frameworks are only reported if one or more agents running a task or executor for the framework have reregistered after master failover.
`healthy` would be true if the master is healthy. Delayed responses are also indicative of the poor health of the master.
Used in:
Contains the logging level of the master.
Used in:
Contains the cluster's maintenance schedule.
Used in:
Contains the cluster's maintenance status.
Used in:
Contains the master's information.
Used in:
Contains a snapshot of the current metrics.
Used in:
Lists information about all operations known to the master at the current time.
Used in:
Contains the cluster's configured quotas.
Used in:
Provides information about every role that is on the role whitelist (if enabled), has one or more registered frameworks or has a non-default weight or quota.
Used in:
Contains full state of the master i.e. information about the tasks, agents, frameworks and executors running in the cluster.
Used in:
,Lists information about all the tasks known to the master at the current time. Note that there might be tasks unknown to the master running on partitioned or unsubscribed agents.
Used in:
,Tasks that are enqueued on the master waiting (e.g., authorizing) to be launched.
Tasks that have been forwarded to the agent for launch. This includes tasks that are staging or running; it also includes tasks that have reached a terminal state but the terminal status update has not yet been acknowledged by the scheduler.
Tasks that were running on agents that have become partitioned from the master. If/when the agent is no longer partitioned, tasks running on that agent will no longer be unreachable (they will either be running or completed). Note that the master only stores a limited number of unreachable tasks; information about unreachable tasks is also not preserved across master failover.
Tasks that have reached terminal state and have all their updates acknowledged by the scheduler.
As of Mesos 1.3.0, this field is deprecated and will always be empty. TODO(neilc): Remove this field in Mesos 2.0.
Contains the version information of the master.
Used in:
Provides the weight information about every role.
Used in:
Contains the file listing(similar to `ls -l`) for a directory.
Used in:
Contains the file data.
Used in:
The size of file (in bytes).
Each of the responses of type `FOO` corresponds to `Foo` message below.
Used in:
See 'GetHealth' below.
See 'GetFlags' below.
See 'GetVersion' below.
See 'GetMetrics' below.
See 'GetLoggingLevel' below.
See 'ReadFile' below.
See 'GetExecutors' below.
See 'GetOperations' below.
See 'GetTasks' below.
See 'GetRoles' below.
See 'GetWeights' below.
See 'GetMaster' below.
See 'GetMaintenanceStatus' below.
See 'GetMaintenanceSchedule' below.