FWIW:
We're using registrator[1] to register with Consul, consul-haproxy[2]
to generate the haproxy config, and have written a simple rest-client
for Consul for use inside our Java apps to find their dependencies via
Consul. Previously, we were using Marathon, a custom haproxy
generator script, a
Have anyone experience TASK_LOST status for storm tasks on mesos.
I checked the stderr. Everything seems normal.
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0917 00:21:36.164840 4831 fetcher.cpp:76] Fetching URI 'hdfs://
192.168.123.27/storm-mesos-0.9.2-incubating.tgz'
I091
Can you show us the the slave log and more of the master log?
There should be a TASK_LOST somewhere within them.
On Wed, Sep 17, 2014 at 10:43 AM, Luyi Wang wrote:
> Have anyone experience TASK_LOST status for storm tasks on mesos.
>
>
> I checked the stderr. Everything seems normal.
> WARNING:
Here is the slave log.
I0917 00:16:45.759867 10209 slave.cpp:3057] Current usage 43.77%. Max
allowed age: 3.235877672809236days
I0917 00:17:31.145267 10212 slave.cpp:1011] Got assigned task
dev10-cdh5-03.int.dev10.smcl.pure-breeze.com-31000 for framework
20140915-230424-326871232-5050-13574-
I
It looks like the executor exited while holding a RUNNING task. Do you have
the executor logs handy? You can find them in the mesos webui or in the
sandbox location of this executor.
On Wed, Sep 17, 2014 at 2:32 PM, Luyi Wang wrote:
> Here is the slave log.
>
> I0917 00:16:45.759867 10209 slave.
Hey Vinod,
On the most part I have indeed observed this to be the case. However every
now and then the tasks are being launched out of order. Here's a slave log
https://gist.github.com/tarnfeld/7a275e2ddffdc4da9e2f.
You can see the slave is assigned the tasks in order, *Task_Tracker_10* first
the
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.20.1.
0.20.1 includes the following:
Minor bug fixes for docker integration, network isolation, etc.
The CHANGELOG for the release is avail
Looked at the code in Slave::runTask() and indeed there is a bug that
doesn't guarantee the order of task delivery to an executor. Mind filing a
ticket?
On Wed, Sep 17, 2014 at 6:22 PM, Tom Arnfeld wrote:
> Hey Vinod,
>
> On the most part I have indeed observed this to be the case. However every
Thanks for taking a look, created a ticket
https://issues.apache.org/jira/browse/MESOS-1812
On 18 September 2014 02:30, Vinod Kone wrote:
> Looked at the code in Slave::runTask() and indeed there is a bug that
> doesn't guarantee the order of task delivery to an executor. Mind filing a
> ticket?
Update: The vote is open until Mon Sep 22 10:00:00 PDT 2014 and passes if a
majority of at least 3 +1 PMC votes are cast.
On Wed, Sep 17, 2014 at 6:27 PM, Adam Bordelon wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.20.1.
>
>
> 0.20.1 includes the followi
+1 (binding)
make check passes on CentOS 5.5 w/ gcc 4.8.2.
On Wed, Sep 17, 2014 at 7:42 PM, Adam Bordelon wrote:
> Update: The vote is open until Mon Sep 22 10:00:00 PDT 2014 and passes if
> a majority of at least 3 +1 PMC votes are cast.
>
> On Wed, Sep 17, 2014 at 6:27 PM, Adam Bordelon wr
-1
The docker test failed when I removed the image, and found a problem from
the docker pull implementation.
I've created a reviewboard for a fix: https://reviews.apache.org/r/25758
Will like to get this fixed before releasing it.
Tim
On Wed, Sep 17, 2014 at 9:10 PM, Vinod Kone wrote:
> +1 (b
12 matches
Mail list logo
