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
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!
+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
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
>
+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
I'd really like to pull in the fix for:
https://issues.apache.org/jira/browse/MESOS-4106
This has been a long standing bug that makes the health checking not
function correctly some of the time. While it is rare in CI, it appeared in
a colleague's cluster for about a third of the tasks he was
Hi friends,
we had noticed some discrepancies between the V0 API and the V1 API,
hence we had to create a new release candidate even after the voting of
0.26.0-rc3 had officially ended. Sorry for that!
Please vote on releasing the following candidate as Apache Mesos 0.26.0.
The CHANGELOG for
7 matches
Mail list logo