Hi all,
We're trying to set up Mesos with SSL. We've compiled Mesos with SSL
support and deployed it to the right boxes.
Unfortunately, after setting up all the correct environmental variables, we
get the following error:
I0315 17:48:30.54186520 libevent_ssl_socket.cpp:1105] Could not
>
Hi Zhitao,
Since this is something that could potentially be handled by the executor
and/or framework, I was wondering if you could speak to the advantages of
making this a TaskInfo primitive vs having the executor (or even the
framework) handle it.
-Renan
On Fri, Mar 23, 2018 at 9:19 AM,
Hi all,
We've been noticing connections slowing down between our elected master
and other components in the cluster the like the agents, frameworks,
executor, etc.
From a high level view, it looks like the master is too busy doing
other tasks to reply to messages and we've seen ACKs from
provements to the
serializing made in 1.7.x.
Thanks again for your time Ben!
-Renan
On Sat, Nov 7, 2020 at 10:17 PM Renan DelValle <mailto:re...@apache.org>> wrote:
Hi all,
We've been noticing connections slowing down between our elected
master
and other compon
Renaming the topic because apparently we need to have this discussion again.
First I'd like to thank Charles-François Natali for his patience and
recent contributions.
Second, I'd like say I agree with everything they have said regarding
the state of project. The project can't even begin to
Some perspective from someone who went through something similar with
Apache Aurora:
It's not as simple as electing new committers. It takes time to develop
the trust needed to add new members to the PMC, and that's the most
important aspect of keeping the project going under Apache (my
6 matches
Mail list logo