That worked, but first I had to destroy marathon's state in zookeeper, as
it just kept trying to deploy apps that I was trying to destroy, and no
amount of cancelling deployments and scaling down apps worked.
After that, I had to kill all of the docker processes that were still being
supervised by
Sorry for that, here is the direct link:
http://mail-archives.apache.org/mod_mbox/mesos-user/201410.mbox/%3CCALnA0DwbqJdEm3at7SonsXmCwxnN3%3DCUrwgoPBHXJDoOFyJjig%40mail.gmail.com%3E
On Thu, Oct 23, 2014 at 10:49 AM, Nils De Moor
wrote:
> I had the same issue as you did, here is how I fixed it:
>
I had the same issue as you did, here is how I fixed it:
http://mail-archives.apache.org/mod_mbox/mesos-user/201410.mbox/browser
On Thu, Oct 23, 2014 at 1:42 AM, Connor Doyle wrote:
> Hi Eduardo,
>
> There is a known defect in Mesos that matches your description:
> https://issues.apache.org/jira
Hi Eduardo,
There is a known defect in Mesos that matches your description:
https://issues.apache.org/jira/browse/MESOS-1915
https://issues.apache.org/jira/browse/MESOS-1884
A fix will be included in the next release.
https://reviews.apache.org/r/26486
You see the killTask because the default --
Hi,
I've started experimenting with mesos using the docker containerizer, and
running a simple example got into a very strange state.
I have mesos-0.20.1, marathon-0.7 setup on EC2, using Amazon Linux:
Linux 3.14.20-20.44.amzn1.x86_64 #1 SMP Mon Oct 6 22:52:46 UTC 2014
x86_64 x86_64 x86_64 GNU/
5 matches
Mail list logo