Given regional bare metal Mesos clusters on multiple continents, are there
any known issues running some of the agents over the WAN? Is anyone else
doing it, or is this a terrible idea that I should tell management no on?
A few specifics:
1. Are there any known limitations or configuration gotcha
Jeff,
regarding 3: we are investigating this:
https://issues.apache.org/jira/browse/MESOS-3548
On Thu, Mar 31, 2016 at 3:56 AM, Jeff Schroeder
wrote:
> Given regional bare metal Mesos clusters on multiple continents, are there
> any known issues running some of the agents over the WAN? Is anyon
Interesting. Thanks Alex. Is anyone actively working on this at Mesosphere
or the community that wants to chat about it?
On Thursday, March 31, 2016, Alex Rukletsov wrote:
> Jeff,
>
> regarding 3: we are investigating this:
> https://issues.apache.org/jira/browse/MESOS-3548
>
> On Thu, Mar 31, 2
On Wed, Mar 30, 2016 at 6:56 PM, Jeff Schroeder
wrote:
> Given regional bare metal Mesos clusters on multiple continents, are there
> any known issues running some of the agents over the WAN? Is anyone else
> doing it, or is this a terrible idea that I should tell management no on?
>
> A few spec
This is great info Evan, especially coming from a production experience.
Thanks for sharing it !
On Thu, Mar 31, 2016 at 1:49 PM, Evan Krall wrote:
> On Wed, Mar 30, 2016 at 6:56 PM, Jeff Schroeder <
> jeffschroe...@computer.org> wrote:
>
>> Given regional bare metal Mesos clusters on multiple c
I would recommend looking at what Yelp did with their PaaSTA project. They
have an interesting approach to the multi-region orchestration.
On Thursday, March 31, 2016, Evan Krall wrote:
> On Wed, Mar 30, 2016 at 6:56 PM, Jeff Schroeder <
> jeffschroe...@computer.org
> > wrote:
>
>> Given regional bare metal Mesos clusters on multiple continents, are
>> there any known issues running some of the agents over the WAN? Is anyone
>> else
With Marathon, if you use "command" health checks, the checks are run by
the agents, so they continue to operate during a partition. As far as I can
tell, Marathon doesn't consider delayed healthcheck messages as failures.
Be aware that if you use the Docker executor, your health checks run within
8 matches
Mail list logo