Thanks Alex.
About the context, we use spark on mesos and marathon to launch some
elastisearch,
I kill each leader one-by-one.
By the way as I said, we are on a config Mesos-Master on ubuntu 12, and
mesos-slave on ubuntu 14, to reproduce this comportement.
When I deploy only on Ubuntu 14 mast
+1 (non-binding)
Tested on Debian 8 the following configurations:
```
$ configure && make -j8 check
$ configure && make -j8 distcheck
$ configure && sudo make -j8 check
$ configure && sudo make-j8 distcheck
$ configure --enable-ssl --enable-libevent && make -j8 check
$ configure --enable-ssl -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/09/2015 03:41 PM, Joao Ribeiro wrote:
> Hi Oliver,
>
> GoDocker looks very promising. I have been looking for a a framework
to substitute AWS Lambda for batch jobs scheduling based on docker for
flexibility. That said, I would like to know y
I think that whereas this would clearly be a desirable bug fix to have, it is
not a blocker:
- Not a regression. This problem has been around for a long time, since 0.20
AFAIK.
- There is a simple workaround.
Bernd
> On Dec 10, 2015, at 3:05 AM, Benjamin Mahler
> wrote:
>
> I'd really like t
+1 (non-binding)
Tested on OS X, Fedora 23, and CentOS 7.1 with and without SSL.
`sudo ./bin/mesos-tests.sh` was fine, apart from known (non blocker) issues.
On Thu, Dec 10, 2015 at 1:37 PM, Bernd Mathiske wrote:
> I think that whereas this would clearly be a desirable bug fix to have, it
> is
Just a general FYI, you can tune logging settings by using the GLOG_ prefix
to environment variables. For example GLOG_v=9 turns up the verbosity
level. This works if you're running a java framework with the native java
library. Unfortunately, I haven't found a way to plug GLOG --> SLF4J
That's a really handy tip, thanks for sharing!
As for GLOG --> SLF4J (or any other Java logging framework), I don't think
there is an option available because the native library logs to stderr
directly.
On Thu, Dec 10, 2015 at 9:06 AM, Charles Allen <
charles.al...@metamarkets.com> wrote:
> Just
What is the workaround?
On Thu, Dec 10, 2015 at 4:37 AM, Bernd Mathiske wrote:
> I think that whereas this would clearly be a desirable bug fix to have, it
> is not a blocker:
> - Not a regression. This problem has been around for a long time, since
> 0.20 AFAIK.
> - There is a simple workaround
On Thu, Dec 10, 2015 at 11:12 AM, Zameer Manji wrote:
> the native library logs to stderr directly.
>
By default the library logs to stderr. But you can set Mesos/GLOG env
variables (e.g., MESOS_LOG_DIR) to make it write to a file instead.
To be clear, I'm a binding -1 without this fix pulled in unless folks can
convince me otherwise. :)
Are we sure that folks are even using the consecutive failure health check
feature successfully? When a colleague showed me how he ran into this bug,
it was happening with a pretty high frequency! T
On Dec 10, 2015, at 11:22 AM, Vinod Kone wrote:
>
> On Thu, Dec 10, 2015 at 11:12 AM, Zameer Manji wrote:
> the native library logs to stderr directly.
>
> By default the library logs to stderr. But you can set Mesos/GLOG env
> variables (e.g., MESOS_LOG_DIR) to make it write to a file inste
Hi friends,
we did unfortunately, once again run into an issue that needed immediate
attention (see vote on rc4), hence we have to ask for another round of testing
and voting of this newest release-candidate.
The issue leading to this new release candidate was
https://issues.apache.org/jira/br
Hi everyone,
The allocator API [1] is going to change in the forthcoming 0.26
release [2]. Custom allocators will need to implement several new API
methods. Further changes to the allocator API are being contemplated
for the 0.27 release [3].
If you have built a custom allocator, please speak up!
13 matches
Mail list logo
