Hello everyone,
We are working on adding support for agent lifecycle management [1] that
will provide a feedback mechanism for frameworks in case of agent node
failures. The existing agent lost [2] signal is not sufficient for
frameworks to ascertain that a given agent node isn't coming back.
Her
+1 (non-binding)
Ran `sudo make check` on CentOS 7 with Docker 1.12.1. The only test failure
was: ProvisionerDockerPullerTest.ROOT_INTERNET_CURL_Whiteout
While I haven't had a chance to look deeply into this, it seems that the
whiteout handling was not correct at the time of 1.0, and these changes
Dear framework owners and users,
We are working on upgrading the protobuf library in Mesos to 3.2.0 in
https://issues.apache.org/jira/browse/MESOS-7228, to overcome some protobuf
limitation on message size as well as preparing for further improvement. We
aim to release this with the upcoming Mesos
Commented on the ticket.
On Tue, Jan 17, 2017 at 12:27 PM, Tomek Janiszewski
wrote:
> Created issue for this: https://issues.apache.org/jira/browse/MESOS-6933
>
> pon., 16 sty 2017 o 17:13 użytkownik Tomek Janiszewski
> napisał:
>
>> I looks like it's supported because executor prints grace per
4 matches
Mail list logo