when you have multihomed tasks, having
> two or more network adapters, eth0, eth1 etc
>
>
>
>
> -Original Message-
> From: Alex Evonosky [mailto:alex.evono...@gmail.com]
> Sent: maandag 27 juli 2020 14:36
> To: user@mesos.apache.org
> Subject: Re: fyi: meso
thank you.
We have been running mesos-dns for years now without any issues. The
docker apps spin up on marathon and automatically gets picked up by
mesos-dns...
This is our config.json:
{
"zk": "zk://10.10.10.51:2181,10.10.10.52:2181,10.10.10.53:2181/mesos",
"masters":
congratulations!
On Mon, Mar 12, 2018 at 1:16 PM, Meng Zhu wrote:
> Congrats Chun! Well deserved!
>
> On Mon, Mar 12, 2018 at 10:09 AM, Zhitao Li wrote:
>
>> Congrats, Chun!
>>
>> On Sun, Mar 11, 2018 at 11:47 PM, Gilbert Song
gt;>> Hi Alex,
>>>
>>> looks like you've restarted Marathon during election. Try to backup
>>> ZooKeeper data and then go to exhibitor / ZooKeeper CLI and remove flag
>>> from Marathon namespace:
>>>
>>> /state/migration-in-progress
&g
; According to https://github.com/mesosphere/marathon/pull/5662 the flag
> should be removed upon unsuccessful migration. Which version of Marathon do
> you run?
>
> Tomas
>
> On 22 November 2017 at 08:21, Alex Evonosky <alex.evono...@gmail.com>
> wrote:
>
>> Hello
Hello group-
Long time Mesos user and first time post about an issue. I have been
running mesos 1.4.0 for a while without any issues. The other day, Ubuntu
upgraded mesos to 1.4.1, which seemed to go ok, however, I reloaded one
master node to verify it can come back up after the upgrade and now
6 matches
Mail list logo