Hi all,
I'm please to announce that mesos_exporter 1.1.0 has been released. This is a
minor release with collection of bug fixes and minor features.
https://github.com/mesos/mesos_exporter/releases/tag/v1.1.0
Many thanks to Mesosphere, who kindly contributed the code to the Mesos
community,
Hi,
I would like to make a feature request to include maintenance state of the
agent as a part of response of Operator HTTP API Get_Agents call.
Currently, the Get_Agents HTTP response looks like
> {
> "type": "GET_AGENTS",
> "get_agents": {
> "agents": [
> {
> "active":
I'm a bit concerned about the recovery logic and backward compatibility:
The changes we're making shouldn't affect existing users,
and we should try hard to avoid any future backward compatibility problem.
Say if there is already some custom framework using task ID 'Hello%3AWorld',
then if we
Thanks Andy! Responses inlined below.
> No: As the only character we've run into a problem with is `:`
> (MESOS-9109), it might not be worth it to generalize this to solve a bunch
> of problems that we haven't encountered.
>
>
It's true that I'm not aware of other scenarios where
Hi,
If you are not using Mesos CNI integration, please ignore this email.
Recently, we discovered a few bugs related to our CNI integration when
there are lots of containers (200+) on a single agent box. Please see the
following tickets for details.
MESOS-9125
5 matches
Mail list logo
