Skip to content

Commit

Permalink
Documented that Mesos 1.2.1 don't allow old agents to register.
Browse files Browse the repository at this point in the history
  • Loading branch information
neilconway committed May 11, 2017
1 parent 5917215 commit 7a0cc55
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 0 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@ Release Notes - Mesos - Version 1.2.1
-------------------------------------------
* This is a bug fix release.

**NOTE**: In Mesos 1.2.1, the master will no longer allow 0.x agents to
register. Interoperability between 1.1+ masters and 0.x agents has never
been supported; however, it was not explicitly disallowed, either.
Starting with this release of Mesos, registration attempts by 0.x Mesos
agents will be ignored.

All Issues:
** Bug
* [MESOS-1987] - Add support for SemVer build and prerelease labels to stout.
Expand Down
6 changes: 6 additions & 0 deletions docs/upgrades.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,9 @@ We categorize the changes as follows:
1.2.x
</td>
<td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
<ul style="padding-left:10px;">
<li>R <a href="#1-2-1-disallow-old-agents">Prevent registration by old Mesos agents</a></li>
</ul>
</td>
<td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags-->
<ul style="padding-left:10px;">
Expand Down Expand Up @@ -240,6 +243,9 @@ We categorize the changes as follows:

## Upgrading from 1.1.x to 1.2.x ##

<a name="1-2-1-disallow-old-agents"></a>
* In Mesos 1.2.1, the master will no longer allow 0.x agents to register. Interoperability between 1.1+ masters and 0.x agents has never been supported; however, it was not explicitly disallowed, either. Starting with Mesos 1.2.1, registration attempts by 0.x agents will be ignored. **NOTE:** This applies only when upgrading to Mesos 1.2.1. Mesos 1.2.0 does not implement this behavior.

<a name="1-2-x-heartbeat-flag"></a>
* New Agent flag http_heartbeat_interval: This flag sets a heartbeat interval for messages to be sent over persistent connections made against the agent HTTP API. Currently, this only applies to the LAUNCH_NESTED_CONTAINER_SESSION and ATTACH_CONTAINER_OUTPUT calls. (default: 30secs)

Expand Down

0 comments on commit 7a0cc55

Please sign in to comment.