2:14 +0100, haosdent <haosd...@gmail.com>, wrote:
> Is it caused by your container riemann-elasticsearch could not start
> successfully?
>
> > On Fri, Jan 13, 2017 at 9:10 AM, Giulio Eulisse <giulio.euli...@gmail.com>
> > wrote:
> > &
siders "unknown").
>
> As a quick workaround, try setting this flag to false:
> https://github.com/apache/mesos/blob/1.1.x/src/slave/flags.cpp#L590-L596
>
> > On Thu, Jan 12, 2017 at 4:41 PM, Giulio Eulisse <giulio.euli...@gmail.com>
> > wrote:
> > > MMm...
not recover successfully.
>
> > On Jan 13, 2017 8:43 AM, "Giulio Eulisse" <giulio.euli...@gmail.com> wrote:
> > > MMm... it seems to die after a long sequence of forks, and mesos itself
> > > seems to be issuing the sigkill. I wonder if it's trying to do some
>
.
On 13 Jan 2017, 01:23 +0100, Giulio Eulisse <giulio.euli...@gmail.com>, wrote:
> Ciao,
>
> the only thing I could find is by running a parallel `docker events`
>
> ```
> 2017-01-13T01:18:20.766593692+01:00 network connect
> 32441cb5f42b009580e104a8360e544beec7120bb6fff800f16
to "SIGKILL"?
>
> > On Fri, Jan 13, 2017 at 8:00 AM, Giulio Eulisse <giulio.euli...@gmail.com>
> > wrote:
> > > Hi,
> > > I’ve a setup where I run mesos in docker which works perfectly when I use
> > > 0.28.2. I now migrated to 1.0.1 (but it’s the sam
Hi,
I’ve a setup where I run mesos in docker which works perfectly when I use
0.28.2. I now migrated to 1.0.1 (but it’s the same with 1.1.0 and 1.0.0)
and it seems to receive a sigkill right after saying:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0112 23:22:09.889120
tp://mesos.apache.org/documentation/latest/executor-http-api/
>
> If you find anything missing there, let us know.
>
> Also, we are working on Operator HTTP API documentation and hopefully
> could get it out soon.
>
> cheers,
> /Jay
>
>
> - Original message -
&
Dear all,
I've started writing a simple framework using node.js and the HTTP
Scheduler API. I've managed to subscribe to the event stream, parse
messages and decline offers quite easily, however I'm having a bit of
trouble accepting the offers and launching tasks, since I cannot find any
complete
Ciao,
I filed:
https://issues.apache.org/jira/browse/MESOS-4543
about not being able to start a mesos slave in docker since 0.25 (including
0.26, did not test master). Has anyone seen the same problem?
--
Ciao,
Giulio
this so the the pids are visible between containers.
Tyson
On May 21, 2015, at 6:04 AM, Giulio Eulisse
giulio.euli...@cern.chmailto:giulio.euli...@cern.ch wrote:
Hi,
I've a problem which can be reduced to running:
mesos-execute --name=foo --command=uname -a hostname
--master=leader.mesos:5050
through perf or strace what docker rm is
blocked on?
Tim
On Mon, Mar 23, 2015 at 10:12 AM, Giulio Eulisse
giulio.euli...@cern.ch
wrote:
I suspect my problem is that docker rm takes forever in my case.
I'm not
running docker in docker though.
On 23 Mar 2015, at 18:01, haosdent wrote:
Are your
I suspect my problem is that docker rm takes forever in my case. I'm
not running docker in docker though.
On 23 Mar 2015, at 18:01, haosdent wrote:
Are your issue relevant to this?
https://issues.apache.org/jira/browse/MESOS-2115
On Tue, Mar 24, 2015 at 12:52 AM, Giulio Eulisse
giulio.euli
On Mon, Mar 23, 2015 at 10:12 AM, Giulio Eulisse
giulio.euli...@cern.ch
wrote:
I suspect my problem is that docker rm takes forever in my case.
I'm not
running docker in docker though.
On 23 Mar 2015, at 18:01, haosdent wrote:
Are your issue relevant to this?
https://issues.apache.org/jira
Hi,
is there any best practices / recommendation when updating from mesos
0.19 to mesos 0.20?
--
Ciao,
Giulio
14 matches
Mail list logo
