You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Michael Park <mp...@apache.org> on 2017/05/25 09:20:29 UTC
[VOTE] Release Apache Mesos 1.3.0 (rc3)
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.3.0.
1.3.0 includes the following:
--------------------------------------------------------------------------------
- Multi-role framework support
- Executor authentication support
- Allow frameworks to modify their roles.
The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.3.0-rc3
--------------------------------------------------------------------------------
The candidate for Mesos 1.3.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz
The tag to be voted on is 1.3.0-rc3:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc3
The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz.md5
The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz.asc
The PGP key used to sign the release is here:
https://dist.apache.org/repos/dist/release/mesos/KEYS
The JAR is up in Maven in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1198
Please vote on releasing this package as Apache Mesos 1.3.0!
The vote is open until Tue May 30 11:59:59 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.
[ ] +1 Release this package as Apache Mesos 1.3.0
[ ] -1 Do not release this package because ...
Thanks,
MPark & Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Neil Conway <ne...@gmail.com>.
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone <vi...@apache.org> wrote:
> Failed test: OneWayPartitionTest.MasterToSlave
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
I was able to reproduce this locally, and confirmed that it is a flaky
test. Fix here:
https://reviews.apache.org/r/59685/
I don't think this requires spinning a new 1.3.0 RC.
Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Gastón Kleiman <ga...@mesosphere.io>.
On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com> wrote:
> On Tue, May 30, 2017 at 2:36 PM, Vinod Kone <vi...@apache.org> wrote:
> > Ran on ASF CI.
> >
> > Found following issues.
> >
> > Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-
> Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
>
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>
Nope, I haven't seen this before.
It looks like the executor wasn't launched or something went wrong at a
very early stage of the executor's launch.
This is what the logs from a successful run look like:
I0530 20:19:52.679759 11282 launcher.cpp:140] Forked child with pid '11304'
>> for container '703bded9-43de-4950-986f-0eaec7bbe664'
>
> I0530 20:19:52.692080 11268 fetcher.cpp:324] Starting to fetch URIs for
>> container: 703bded9-43de-4950-986f-0eaec7bbe664, directory:
>> /tmp/CommandExecutorCheckTest_CommandCheckDeliveredAndReconciled_fqE44y/slaves/7c74b451-3e64-4c95-8570-ad3b5b60962b-S0/frameworks/7c74b451-3e64-4c95-8570-ad3b5b60962b-0000/executors/55b387b7-c1f1-47d5-9f19-2d676cd4ef2e/runs/703bded9-43de-4950-986f-0eaec7bbe664
>
> I0530 20:19:53.517201 11268 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:53.517283 11268 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:53.517318 11268 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:53.517367 11268 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 654478ns
>
> I0530 20:19:54.518506 11277 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:54.518584 11277 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:54.518616 11277 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:54.518662 11277 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 568919ns
>
> I0530 20:19:55.520282 11276 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:55.520364 11276 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:55.520409 11276 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:55.520463 11276 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 621097ns
>
> I0530 20:19:56.521884 11271 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:56.521966 11271 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:56.522001 11271 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:56.522047 11271 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 597601ns
>
> I0530 20:19:57.523320 11267 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:57.523398 11267 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:57.523432 11267 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:57.523478 11267 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 573802ns
>
> I0530 20:19:57.641808 11358 exec.cpp:162] Version: 1.4.0
>
> I0530 20:19:57.648437 11268 slave.cpp:3809] Got registration for executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000 from executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650589 11279 slave.cpp:2526] Sending queued task
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' to executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000 at executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650804 11356 exec.cpp:237] Executor registered on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0
>
> Received SUBSCRIBED event
>
> Subscribed executor on gru1.hw.ca1.mesosphere.com
>
> Received LAUNCH event
>
> Starting task 55b387b7-c1f1-47d5-9f19-2d676cd4ef2e
>
> Running '/home/gaston/mesos-custom/build/src/mesos-containerizer launch
>> <POSSIBLY-SENSITIVE-DATA>'
>
> Forked command at 11361
>
> I0530 20:19:57.672251 11273 slave.cpp:4279] Handling status update
>> TASK_RUNNING (UUID: b2e0d7b6-0f15-41d6-ae59-7c915a639672) for task
>> 55b387b7-c1f1-47d5-9f19-2d676cd4ef2e of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000 from executor(1)@
>> 192.99.40.208:43797
>
>
The line saying "Forked command at <pid>" is logged by the command executor
before creating a checker, since it is missing from these logs, I believe
that the failure is not related to checks.
-Gastón
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Gastón Kleiman <ga...@mesosphere.io>.
On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com> wrote:
> On Tue, May 30, 2017 at 2:36 PM, Vinod Kone <vi...@apache.org> wrote:
> > Ran on ASF CI.
> >
> > Found following issues.
> >
> > Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-
> Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
>
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>
Nope, I haven't seen this before.
It looks like the executor wasn't launched or something went wrong at a
very early stage of the executor's launch.
This is what the logs from a successful run look like:
I0530 20:19:52.679759 11282 launcher.cpp:140] Forked child with pid '11304'
>> for container '703bded9-43de-4950-986f-0eaec7bbe664'
>
> I0530 20:19:52.692080 11268 fetcher.cpp:324] Starting to fetch URIs for
>> container: 703bded9-43de-4950-986f-0eaec7bbe664, directory:
>> /tmp/CommandExecutorCheckTest_CommandCheckDeliveredAndReconciled_fqE44y/slaves/7c74b451-3e64-4c95-8570-ad3b5b60962b-S0/frameworks/7c74b451-3e64-4c95-8570-ad3b5b60962b-0000/executors/55b387b7-c1f1-47d5-9f19-2d676cd4ef2e/runs/703bded9-43de-4950-986f-0eaec7bbe664
>
> I0530 20:19:53.517201 11268 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:53.517283 11268 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:53.517318 11268 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:53.517367 11268 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 654478ns
>
> I0530 20:19:54.518506 11277 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:54.518584 11277 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:54.518616 11277 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:54.518662 11277 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 568919ns
>
> I0530 20:19:55.520282 11276 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:55.520364 11276 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:55.520409 11276 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:55.520463 11276 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 621097ns
>
> I0530 20:19:56.521884 11271 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:56.521966 11271 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:56.522001 11271 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:56.522047 11271 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 597601ns
>
> I0530 20:19:57.523320 11267 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000
>
> I0530 20:19:57.523398 11267 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:57.523432 11267 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:57.523478 11267 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 573802ns
>
> I0530 20:19:57.641808 11358 exec.cpp:162] Version: 1.4.0
>
> I0530 20:19:57.648437 11268 slave.cpp:3809] Got registration for executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000 from executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650589 11279 slave.cpp:2526] Sending queued task
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' to executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000 at executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650804 11356 exec.cpp:237] Executor registered on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0
>
> Received SUBSCRIBED event
>
> Subscribed executor on gru1.hw.ca1.mesosphere.com
>
> Received LAUNCH event
>
> Starting task 55b387b7-c1f1-47d5-9f19-2d676cd4ef2e
>
> Running '/home/gaston/mesos-custom/build/src/mesos-containerizer launch
>> <POSSIBLY-SENSITIVE-DATA>'
>
> Forked command at 11361
>
> I0530 20:19:57.672251 11273 slave.cpp:4279] Handling status update
>> TASK_RUNNING (UUID: b2e0d7b6-0f15-41d6-ae59-7c915a639672) for task
>> 55b387b7-c1f1-47d5-9f19-2d676cd4ef2e of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-0000 from executor(1)@
>> 192.99.40.208:43797
>
>
The line saying "Forked command at <pid>" is logged by the command executor
before creating a checker, since it is missing from these logs, I believe
that the failure is not related to checks.
-Gastón
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Benjamin Mahler <bm...@apache.org>.
Thanks Yan!
On Fri, Jun 2, 2017 at 10:45 AM, Yan Xu <ya...@jxu.me> wrote:
> +1 (binding)
>
> Ran it in a test cluster.
>
> ---
> Jiang Yan Xu <ya...@jxu.me> | @xujyan <https://twitter.com/xujyan>
>
> On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler <bm...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> Looks like ExamplesTest.DynamicReservationFramework is flaky,
>> unfortunately
>> wasn't able to get the logs for a failed run.
>>
>> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bm...@apache.org>
>> wrote:
>>
>> > Not a blocker, but noticed the parallel test runner isn't bundled in the
>> > release, if you configure with '--enable-parallel-test-execution':
>> >
>> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
>> > --sequential=*ROOT_* ./stout-tests
>> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-
>> runner.py:
>> > No such file or directory
>> >
>> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org>
>> wrote:
>> >
>> >> Thanks for the triage.
>> >>
>> >> +1 (binding)
>> >>
>> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
>> >> wrote:
>> >>
>> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
>> >>> wrote:
>> >>> > Attached is the test log for this failure. From a quick look, seems
>> as
>> >>> > though the agent starts to launch the task, including forking the
>> >>> > child process, but no subsequent task status updates or error
>> messages
>> >>> > are observed. Gaston, have you seen this before?
>> >>> >
>> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>> >>> this.
>> >>>
>> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> >>> enough information in the logs to understand what is going on here,
>> >>> although it certainly seems weird that apparently the executor doesn't
>> >>> start.
>> >>>
>> >>> I think this doesn't justify blocking the release, but we should watch
>> >>> to see if the problem recurs.
>> >>>
>> >>> Neil
>> >>>
>> >>
>> >>
>> >
>>
>
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Benjamin Mahler <bm...@apache.org>.
Thanks Yan!
On Fri, Jun 2, 2017 at 10:45 AM, Yan Xu <ya...@jxu.me> wrote:
> +1 (binding)
>
> Ran it in a test cluster.
>
> ---
> Jiang Yan Xu <ya...@jxu.me> | @xujyan <https://twitter.com/xujyan>
>
> On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler <bm...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> Looks like ExamplesTest.DynamicReservationFramework is flaky,
>> unfortunately
>> wasn't able to get the logs for a failed run.
>>
>> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bm...@apache.org>
>> wrote:
>>
>> > Not a blocker, but noticed the parallel test runner isn't bundled in the
>> > release, if you configure with '--enable-parallel-test-execution':
>> >
>> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
>> > --sequential=*ROOT_* ./stout-tests
>> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-
>> runner.py:
>> > No such file or directory
>> >
>> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org>
>> wrote:
>> >
>> >> Thanks for the triage.
>> >>
>> >> +1 (binding)
>> >>
>> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
>> >> wrote:
>> >>
>> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
>> >>> wrote:
>> >>> > Attached is the test log for this failure. From a quick look, seems
>> as
>> >>> > though the agent starts to launch the task, including forking the
>> >>> > child process, but no subsequent task status updates or error
>> messages
>> >>> > are observed. Gaston, have you seen this before?
>> >>> >
>> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>> >>> this.
>> >>>
>> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> >>> enough information in the logs to understand what is going on here,
>> >>> although it certainly seems weird that apparently the executor doesn't
>> >>> start.
>> >>>
>> >>> I think this doesn't justify blocking the release, but we should watch
>> >>> to see if the problem recurs.
>> >>>
>> >>> Neil
>> >>>
>> >>
>> >>
>> >
>>
>
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Yan Xu <ya...@jxu.me>.
+1 (binding)
Ran it in a test cluster.
---
Jiang Yan Xu <ya...@jxu.me> | @xujyan <https://twitter.com/xujyan>
On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler <bm...@apache.org> wrote:
> +1 (binding)
>
> Looks like ExamplesTest.DynamicReservationFramework is flaky,
> unfortunately
> wasn't able to get the logs for a failed run.
>
> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bm...@apache.org>
> wrote:
>
> > Not a blocker, but noticed the parallel test runner isn't bundled in the
> > release, if you configure with '--enable-parallel-test-execution':
> >
> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
> > --sequential=*ROOT_* ./stout-tests
> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-
> gtest-runner.py:
> > No such file or directory
> >
> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org>
> wrote:
> >
> >> Thanks for the triage.
> >>
> >> +1 (binding)
> >>
> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
> >> wrote:
> >>
> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
> >>> wrote:
> >>> > Attached is the test log for this failure. From a quick look, seems
> as
> >>> > though the agent starts to launch the task, including forking the
> >>> > child process, but no subsequent task status updates or error
> messages
> >>> > are observed. Gaston, have you seen this before?
> >>> >
> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
> >>> this.
> >>>
> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
> >>> enough information in the logs to understand what is going on here,
> >>> although it certainly seems weird that apparently the executor doesn't
> >>> start.
> >>>
> >>> I think this doesn't justify blocking the release, but we should watch
> >>> to see if the problem recurs.
> >>>
> >>> Neil
> >>>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Yan Xu <ya...@jxu.me>.
+1 (binding)
Ran it in a test cluster.
---
Jiang Yan Xu <ya...@jxu.me> | @xujyan <https://twitter.com/xujyan>
On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler <bm...@apache.org> wrote:
> +1 (binding)
>
> Looks like ExamplesTest.DynamicReservationFramework is flaky,
> unfortunately
> wasn't able to get the logs for a failed run.
>
> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bm...@apache.org>
> wrote:
>
> > Not a blocker, but noticed the parallel test runner isn't bundled in the
> > release, if you configure with '--enable-parallel-test-execution':
> >
> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
> > --sequential=*ROOT_* ./stout-tests
> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-
> gtest-runner.py:
> > No such file or directory
> >
> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org>
> wrote:
> >
> >> Thanks for the triage.
> >>
> >> +1 (binding)
> >>
> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
> >> wrote:
> >>
> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
> >>> wrote:
> >>> > Attached is the test log for this failure. From a quick look, seems
> as
> >>> > though the agent starts to launch the task, including forking the
> >>> > child process, but no subsequent task status updates or error
> messages
> >>> > are observed. Gaston, have you seen this before?
> >>> >
> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
> >>> this.
> >>>
> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
> >>> enough information in the logs to understand what is going on here,
> >>> although it certainly seems weird that apparently the executor doesn't
> >>> start.
> >>>
> >>> I think this doesn't justify blocking the release, but we should watch
> >>> to see if the problem recurs.
> >>>
> >>> Neil
> >>>
> >>
> >>
> >
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Benjamin Mahler <bm...@apache.org>.
+1 (binding)
Looks like ExamplesTest.DynamicReservationFramework is flaky, unfortunately
wasn't able to get the logs for a failed run.
On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bm...@apache.org> wrote:
> Not a blocker, but noticed the parallel test runner isn't bundled in the
> release, if you configure with '--enable-parallel-test-execution':
>
> /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
> --sequential=*ROOT_* ./stout-tests
> /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py:
> No such file or directory
>
> On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org> wrote:
>
>> Thanks for the triage.
>>
>> +1 (binding)
>>
>> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
>> wrote:
>>
>>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
>>> wrote:
>>> > Attached is the test log for this failure. From a quick look, seems as
>>> > though the agent starts to launch the task, including forking the
>>> > child process, but no subsequent task status updates or error messages
>>> > are observed. Gaston, have you seen this before?
>>> >
>>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>>> this.
>>>
>>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>>> enough information in the logs to understand what is going on here,
>>> although it certainly seems weird that apparently the executor doesn't
>>> start.
>>>
>>> I think this doesn't justify blocking the release, but we should watch
>>> to see if the problem recurs.
>>>
>>> Neil
>>>
>>
>>
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Benjamin Mahler <bm...@apache.org>.
+1 (binding)
Looks like ExamplesTest.DynamicReservationFramework is flaky, unfortunately
wasn't able to get the logs for a failed run.
On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler <bm...@apache.org> wrote:
> Not a blocker, but noticed the parallel test runner isn't bundled in the
> release, if you configure with '--enable-parallel-test-execution':
>
> /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
> --sequential=*ROOT_* ./stout-tests
> /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py:
> No such file or directory
>
> On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org> wrote:
>
>> Thanks for the triage.
>>
>> +1 (binding)
>>
>> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
>> wrote:
>>
>>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
>>> wrote:
>>> > Attached is the test log for this failure. From a quick look, seems as
>>> > though the agent starts to launch the task, including forking the
>>> > child process, but no subsequent task status updates or error messages
>>> > are observed. Gaston, have you seen this before?
>>> >
>>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>>> this.
>>>
>>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>>> enough information in the logs to understand what is going on here,
>>> although it certainly seems weird that apparently the executor doesn't
>>> start.
>>>
>>> I think this doesn't justify blocking the release, but we should watch
>>> to see if the problem recurs.
>>>
>>> Neil
>>>
>>
>>
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Benjamin Mahler <bm...@apache.org>.
Not a blocker, but noticed the parallel test runner isn't bundled in the
release, if you configure with '--enable-parallel-test-execution':
/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
--sequential=*ROOT_* ./stout-tests
/bin/sh:
/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py: No such
file or directory
On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org> wrote:
> Thanks for the triage.
>
> +1 (binding)
>
> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
> wrote:
>
>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
>> wrote:
>> > Attached is the test log for this failure. From a quick look, seems as
>> > though the agent starts to launch the task, including forking the
>> > child process, but no subsequent task status updates or error messages
>> > are observed. Gaston, have you seen this before?
>> >
>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>>
>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> enough information in the logs to understand what is going on here,
>> although it certainly seems weird that apparently the executor doesn't
>> start.
>>
>> I think this doesn't justify blocking the release, but we should watch
>> to see if the problem recurs.
>>
>> Neil
>>
>
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Benjamin Mahler <bm...@apache.org>.
Not a blocker, but noticed the parallel test runner isn't bundled in the
release, if you configure with '--enable-parallel-test-execution':
/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
--sequential=*ROOT_* ./stout-tests
/bin/sh:
/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py: No such
file or directory
On Wed, May 31, 2017 at 1:48 PM, Vinod Kone <vi...@apache.org> wrote:
> Thanks for the triage.
>
> +1 (binding)
>
> On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com>
> wrote:
>
>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
>> wrote:
>> > Attached is the test log for this failure. From a quick look, seems as
>> > though the agent starts to launch the task, including forking the
>> > child process, but no subsequent task status updates or error messages
>> > are observed. Gaston, have you seen this before?
>> >
>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>>
>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> enough information in the logs to understand what is going on here,
>> although it certainly seems weird that apparently the executor doesn't
>> start.
>>
>> I think this doesn't justify blocking the release, but we should watch
>> to see if the problem recurs.
>>
>> Neil
>>
>
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Vinod Kone <vi...@apache.org>.
Thanks for the triage.
+1 (binding)
On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com> wrote:
> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
> wrote:
> > Attached is the test log for this failure. From a quick look, seems as
> > though the agent starts to launch the task, including forking the
> > child process, but no subsequent task status updates or error messages
> > are observed. Gaston, have you seen this before?
> >
> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>
> I wasn't able to repro this failure. Per Gaston's email, there isn't
> enough information in the logs to understand what is going on here,
> although it certainly seems weird that apparently the executor doesn't
> start.
>
> I think this doesn't justify blocking the release, but we should watch
> to see if the problem recurs.
>
> Neil
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Vinod Kone <vi...@apache.org>.
Thanks for the triage.
+1 (binding)
On Wed, May 31, 2017 at 1:33 PM, Neil Conway <ne...@gmail.com> wrote:
> On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com>
> wrote:
> > Attached is the test log for this failure. From a quick look, seems as
> > though the agent starts to launch the task, including forking the
> > child process, but no subsequent task status updates or error messages
> > are observed. Gaston, have you seen this before?
> >
> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>
> I wasn't able to repro this failure. Per Gaston's email, there isn't
> enough information in the logs to understand what is going on here,
> although it certainly seems weird that apparently the executor doesn't
> start.
>
> I think this doesn't justify blocking the release, but we should watch
> to see if the problem recurs.
>
> Neil
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Neil Conway <ne...@gmail.com>.
On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com> wrote:
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
I wasn't able to repro this failure. Per Gaston's email, there isn't
enough information in the logs to understand what is going on here,
although it certainly seems weird that apparently the executor doesn't
start.
I think this doesn't justify blocking the release, but we should watch
to see if the problem recurs.
Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Neil Conway <ne...@gmail.com>.
On Tue, May 30, 2017 at 3:43 PM, Neil Conway <ne...@gmail.com> wrote:
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
I wasn't able to repro this failure. Per Gaston's email, there isn't
enough information in the logs to understand what is going on here,
although it certainly seems weird that apparently the executor doesn't
start.
I think this doesn't justify blocking the release, but we should watch
to see if the problem recurs.
Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Neil Conway <ne...@gmail.com>.
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone <vi...@apache.org> wrote:
> Ran on ASF CI.
>
> Found following issues.
>
> Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Attached is the test log for this failure. From a quick look, seems as
though the agent starts to launch the task, including forking the
child process, but no subsequent task status updates or error messages
are observed. Gaston, have you seen this before?
I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
> Failed test: OneWayPartitionTest.MasterToSlave
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Looking into this now.
Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Neil Conway <ne...@gmail.com>.
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone <vi...@apache.org> wrote:
> Ran on ASF CI.
>
> Found following issues.
>
> Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Attached is the test log for this failure. From a quick look, seems as
though the agent starts to launch the task, including forking the
child process, but no subsequent task status updates or error messages
are observed. Gaston, have you seen this before?
I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
> Failed test: OneWayPartitionTest.MasterToSlave
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Looking into this now.
Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Neil Conway <ne...@gmail.com>.
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone <vi...@apache.org> wrote:
> Failed test: OneWayPartitionTest.MasterToSlave
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
I was able to reproduce this locally, and confirmed that it is a flaky
test. Fix here:
https://reviews.apache.org/r/59685/
I don't think this requires spinning a new 1.3.0 RC.
Neil
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Vinod Kone <vi...@apache.org>.
Ran on ASF CI.
Found following issues.
Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Failed test: OneWayPartitionTest.MasterToSlave
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Can you confirm if these are known or new issues?
Thanks,
On Thu, May 25, 2017 at 2:20 AM, Michael Park <mp...@apache.org> wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.3.0.
>
>
> 1.3.0 includes the following:
> ------------------------------------------------------------
> --------------------
> - Multi-role framework support
> - Executor authentication support
> - Allow frameworks to modify their roles.
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
> lain;f=CHANGELOG;hb=1.3.0-rc3
> ------------------------------------------------------------
> --------------------
>
> The candidate for Mesos 1.3.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz
>
> The tag to be voted on is 1.3.0-rc3:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc3
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos
> -1.3.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos
> -1.3.0.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1198
>
> Please vote on releasing this package as Apache Mesos 1.3.0!
>
> The vote is open until Tue May 30 11:59:59 PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.3.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark & Neil
>
Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)
Posted by Vinod Kone <vi...@apache.org>.
Ran on ASF CI.
Found following issues.
Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Failed test: OneWayPartitionTest.MasterToSlave
<https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
Can you confirm if these are known or new issues?
Thanks,
On Thu, May 25, 2017 at 2:20 AM, Michael Park <mp...@apache.org> wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.3.0.
>
>
> 1.3.0 includes the following:
> ------------------------------------------------------------
> --------------------
> - Multi-role framework support
> - Executor authentication support
> - Allow frameworks to modify their roles.
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
> lain;f=CHANGELOG;hb=1.3.0-rc3
> ------------------------------------------------------------
> --------------------
>
> The candidate for Mesos 1.3.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz
>
> The tag to be voted on is 1.3.0-rc3:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc3
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos
> -1.3.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos
> -1.3.0.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1198
>
> Please vote on releasing this package as Apache Mesos 1.3.0!
>
> The vote is open until Tue May 30 11:59:59 PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.3.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark & Neil
>