Re: [VOTE] Release Apache Mesos 1.4.0 (rc3)

2017-08-28 Thread Benjamin Mahler
-1 due to https://issues.apache.org/jira/browse/MESOS-7921 Thanks for reporting this Yan, it unfortunately went unnoticed despite CI failures since Aug 3rd. On Mon, Aug 28, 2017 at 12:29 PM, Yan Xu wrote: > Also the libprocess refactor seems to have stability issues: >

Re: TaskStatus.uuid for idempotent status handling

2017-08-28 Thread Benjamin Mahler
Yes, the UUID is how you would check for a duplicate due to re-transmission. These duplicates still need to be acknowledged. Ben On Mon, Aug 28, 2017 at 9:59 AM, Christoph Heer wrote: > Hi, > > as described in Mesos' documentation [1], a framework scheduler should >

Re: [VOTE] Release Apache Mesos 1.4.0 (rc3)

2017-08-28 Thread tommy xiao
-1 2017-08-29 3:29 GMT+08:00 Yan Xu : > Also the libprocess refactor seems to have stability issues: > https://issues.apache.org/jira/browse/MESOS-7921 > > CI failures this crash caused: > https://lists.apache.org/list.html?bui...@mesos.apache.org: >

Re: [VOTE] Release Apache Mesos 1.4.0 (rc3)

2017-08-28 Thread Yan Xu
Also the libprocess refactor seems to have stability issues: https://issues.apache.org/jira/browse/MESOS-7921 CI failures this crash caused: https://lists.apache.org/list.html?bui...@mesos.apache.org:lte=1M:process%3A%3AEventQueue%3A%3AConsumer%3A%3Aempty%28%29%20 --- Jiang Yan Xu

Re: [VOTE] Release Apache Mesos 1.4.0 (rc3)

2017-08-28 Thread Michael Park
-1 I found MESOS-7922 , which is an issue around the communication between old masters and new agents. Currently, the new agent re-registers with the tasks and executors in the new format. The new master conditionally upgrades the resources

[VOTE] Release Apache Mesos 1.4.0 (rc3)

2017-08-28 Thread Kapil Arya
Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.0. 1.4.0 includes the following: * Ability to recover the agent ID after a host reboot. * File-based and image-pull secrets. * Linux

TaskStatus.uuid for idempotent status handling

2017-08-28 Thread Christoph Heer
Hi, as described in Mesos' documentation [1], a framework scheduler should handle status updates idempotent. Would it be sufficient to store the uuid of the status update and ignore retransmissions with the same uuid? Based on Mesos master and agent logs the uuid is stable across

Re: [VOTE] Release Apache Mesos 1.4.0 (rc2)

2017-08-28 Thread Kapil Arya
Hi All, Due to a discrepancy in the CHANGELOG, we are retracting this release candidate and will put out a new release candidate for voting in a little while. Best, Anand and Kapil On Mon, Aug 28, 2017 at 12:44 PM, Kapil Arya wrote: > Hi all, > > Please vote on releasing

[VOTE] Release Apache Mesos 1.4.0 (rc2)

2017-08-28 Thread Kapil Arya
Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.0. 1.4.0 includes the following: * Ability to recover the agent ID after a host reboot. * File-based and image-pull secrets. *