[jira] [Updated] (MESOS-3488) /sys/fs/cgroup/memory/mesos missing after running a while
[ https://issues.apache.org/jira/browse/MESOS-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengwei Yang updated MESOS-3488: - Summary: /sys/fs/cgroup/memory/mesos missing after running a while (was: /sys/fs/cgroup/memory/mesos) > /sys/fs/cgroup/memory/mesos missing after running a while > - > > Key: MESOS-3488 > URL: https://issues.apache.org/jira/browse/MESOS-3488 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.21.0 > Environment: mesos 0.21.0 on CentOS 7.1 >Reporter: Chengwei Yang > > I setup mesos 0.21.0 on CentOS 7.1 with mesos-0.21.0 rpm downloaded from > mesosphere. > at first, it works fine, jobs are finished correctly, however, after running > a while, all task goes to LOST. > And there is nothing in **sandbox** and I see below from mesos-slave.ERROR > ``` > E0922 14:02:31.329264 8336 slave.cpp:2787] Container > '865c9a1c-3abe-4263-921e-8d0be2f0a56d' for executor > '21bf1400-6456-45e5-8f28-fe5ade7e7bfd' of framework > '20150401-105258-3755085578-5050-14676-' failed to start: Failed to > prepare isolator: Failed to create directory > '/sys/fs/cgroup/memory/mesos/865c9a1c-3abe-4263-921e-8d0be2f0a56d': No such > file or directory > ``` > And I checked that /sys/fs/cgroup/cpu/mesos does exist while > /sys/fs/cgroup/memory/mesos is missing. > Since at first mesos works fine (and I checked source code, that if it create > /sys/fs/cgroup/memory/mesos failed at mesos-slave startup, it will log that > error), so I'm curious when/which removed /sys/fs/cgroup/memory/mesos. > Has anyone saw this issue before? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3488) /sys/fs/cgroup/memory/mesos
[ https://issues.apache.org/jira/browse/MESOS-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902059#comment-14902059 ] Chengwei Yang commented on MESOS-3488: -- BTW, mesos 0.21.0 on centos 6.4 works fine, haven't see this issue before. > /sys/fs/cgroup/memory/mesos > --- > > Key: MESOS-3488 > URL: https://issues.apache.org/jira/browse/MESOS-3488 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.21.0 > Environment: mesos 0.21.0 on CentOS 7.1 >Reporter: Chengwei Yang > > I setup mesos 0.21.0 on CentOS 7.1 with mesos-0.21.0 rpm downloaded from > mesosphere. > at first, it works fine, jobs are finished correctly, however, after running > a while, all task goes to LOST. > And there is nothing in **sandbox** and I see below from mesos-slave.ERROR > ``` > E0922 14:02:31.329264 8336 slave.cpp:2787] Container > '865c9a1c-3abe-4263-921e-8d0be2f0a56d' for executor > '21bf1400-6456-45e5-8f28-fe5ade7e7bfd' of framework > '20150401-105258-3755085578-5050-14676-' failed to start: Failed to > prepare isolator: Failed to create directory > '/sys/fs/cgroup/memory/mesos/865c9a1c-3abe-4263-921e-8d0be2f0a56d': No such > file or directory > ``` > And I checked that /sys/fs/cgroup/cpu/mesos does exist while > /sys/fs/cgroup/memory/mesos is missing. > Since at first mesos works fine (and I checked source code, that if it create > /sys/fs/cgroup/memory/mesos failed at mesos-slave startup, it will log that > error), so I'm curious when/which removed /sys/fs/cgroup/memory/mesos. > Has anyone saw this issue before? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3488) /sys/fs/cgroup/memory/mesos
Chengwei Yang created MESOS-3488: Summary: /sys/fs/cgroup/memory/mesos Key: MESOS-3488 URL: https://issues.apache.org/jira/browse/MESOS-3488 Project: Mesos Issue Type: Bug Affects Versions: 0.21.0 Environment: mesos 0.21.0 on CentOS 7.1 Reporter: Chengwei Yang I setup mesos 0.21.0 on CentOS 7.1 with mesos-0.21.0 rpm downloaded from mesosphere. at first, it works fine, jobs are finished correctly, however, after running a while, all task goes to LOST. And there is nothing in **sandbox** and I see below from mesos-slave.ERROR ``` E0922 14:02:31.329264 8336 slave.cpp:2787] Container '865c9a1c-3abe-4263-921e-8d0be2f0a56d' for executor '21bf1400-6456-45e5-8f28-fe5ade7e7bfd' of framework '20150401-105258-3755085578-5050-14676-' failed to start: Failed to prepare isolator: Failed to create directory '/sys/fs/cgroup/memory/mesos/865c9a1c-3abe-4263-921e-8d0be2f0a56d': No such file or directory ``` And I checked that /sys/fs/cgroup/cpu/mesos does exist while /sys/fs/cgroup/memory/mesos is missing. Since at first mesos works fine (and I checked source code, that if it create /sys/fs/cgroup/memory/mesos failed at mesos-slave startup, it will log that error), so I'm curious when/which removed /sys/fs/cgroup/memory/mesos. Has anyone saw this issue before? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3487) Running libprocess tests in a loop leads to unbounded memory growth.
[
https://issues.apache.org/jira/browse/MESOS-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-3487:
---
Description:
Was doing some repeat testing on a patch to check for flakiness and noticed
that the libprocess tests appear to have a leak that leads to unbounded memory
growth.
I checked the stout tests as well, they appear ok.
Notice the large RSS for the libprocess tests:
{noformat}
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
55133 root 20 0 479m 9.9m 6860 S 56.8 0.0 0:02.36 tests
16410 root 20 0 575m 152m 6864 S 60.1 0.2 6:09.70 tests
61363 root 20 0 606m 304m 6948 R 74.7 0.4 15:50.11 tests
32836 root 20 0 116m 9032 5580 S 88.3 0.0 3:46.32 stout-tests
{noformat}
Commands to reproduce:
{noformat}
$ sudo ./3rdparty/libprocess/tests --gtest_repeat=-1 --gtest_break_on_failure
$ sudo ./3rdparty/libprocess/3rdparty/stout-tests --gtest_repeat=-1
--gtest_break_on_failure
{noformat}
was:
Was doing some repeat testing on a patch to check for flakiness and noticed
that the libprocess tests appear to have a leak that leads to unbounded memory
growth.
I checked the stout tests as well, they appear ok.
Notice the large RSS for the libprocess tests:
{noformat}
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
55133 root 20 0 479m 9.9m 6860 S 56.8 0.0 0:02.36 tests
16410 root 20 0 575m 152m 6864 S 60.1 0.2 6:09.70 tests
61363 root 20 0 606m 304m 6948 R 74.7 0.4 15:50.11 tests
32836 root 20 0 116m 9032 5580 S 88.3 0.0 3:46.32 stout-tests
{noformat}
> Running libprocess tests in a loop leads to unbounded memory growth.
>
>
> Key: MESOS-3487
> URL: https://issues.apache.org/jira/browse/MESOS-3487
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
>Reporter: Benjamin Mahler
> Labels: newbie
>
> Was doing some repeat testing on a patch to check for flakiness and noticed
> that the libprocess tests appear to have a leak that leads to unbounded
> memory growth.
> I checked the stout tests as well, they appear ok.
> Notice the large RSS for the libprocess tests:
> {noformat}
> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
> 55133 root 20 0 479m 9.9m 6860 S 56.8 0.0 0:02.36 tests
> 16410 root 20 0 575m 152m 6864 S 60.1 0.2 6:09.70 tests
> 61363 root 20 0 606m 304m 6948 R 74.7 0.4 15:50.11 tests
> 32836 root 20 0 116m 9032 5580 S 88.3 0.0 3:46.32 stout-tests
> {noformat}
> Commands to reproduce:
> {noformat}
> $ sudo ./3rdparty/libprocess/tests --gtest_repeat=-1 --gtest_break_on_failure
> $ sudo ./3rdparty/libprocess/3rdparty/stout-tests --gtest_repeat=-1
> --gtest_break_on_failure
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-3487) Running libprocess tests in a loop leads to unbounded memory growth.
Benjamin Mahler created MESOS-3487:
--
Summary: Running libprocess tests in a loop leads to unbounded
memory growth.
Key: MESOS-3487
URL: https://issues.apache.org/jira/browse/MESOS-3487
Project: Mesos
Issue Type: Bug
Components: libprocess
Reporter: Benjamin Mahler
Was doing some repeat testing on a patch to check for flakiness and noticed
that the libprocess tests appear to have a leak that leads to unbounded memory
growth.
I checked the stout tests as well, they appear ok.
Notice the large RSS for the libprocess tests:
{noformat}
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
55133 root 20 0 479m 9.9m 6860 S 56.8 0.0 0:02.36 tests
16410 root 20 0 575m 152m 6864 S 60.1 0.2 6:09.70 tests
61363 root 20 0 606m 304m 6948 R 74.7 0.4 15:50.11 tests
32836 root 20 0 116m 9032 5580 S 88.3 0.0 3:46.32 stout-tests
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3468) Improve apply_reviews.sh script to apply chain of reviews
[ https://issues.apache.org/jira/browse/MESOS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901947#comment-14901947 ] Vinod Kone commented on MESOS-3468: --- Cool. Do post a review. One additional thing the script could do is to mark the reviews as submitted, but that functionality should ideally be a pre push git hook. > Improve apply_reviews.sh script to apply chain of reviews > - > > Key: MESOS-3468 > URL: https://issues.apache.org/jira/browse/MESOS-3468 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Artem Harutyunyan > > Currently the support/apply-review.sh script allows an user (typically > committer) to apply a single review on top the HEAD. Since Mesos contributors > typically submit a chain of reviews for a given issue it makes sense for the > script to apply the whole chain recursively. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3468) Improve apply_reviews.sh script to apply chain of reviews
[ https://issues.apache.org/jira/browse/MESOS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901926#comment-14901926 ] Artem Harutyunyan commented on MESOS-3468: -- Hey [~vinodkone], A while ago I put together a script that does exactly this. You can take a look at it here https://github.com/artemharutyunyan/mesos/commit/66b13c22dbbf5533228e825b904de234424b4a7c. It actually uses apply-review.sh underneath and supports a dry-run mode. Did you have something like this in mind? It's actually useful in it's current form (at least for me), but if you think there are features missing I'd be happy to add them and post a review. Cheers, Artem. > Improve apply_reviews.sh script to apply chain of reviews > - > > Key: MESOS-3468 > URL: https://issues.apache.org/jira/browse/MESOS-3468 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Artem Harutyunyan > > Currently the support/apply-review.sh script allows an user (typically > committer) to apply a single review on top the HEAD. Since Mesos contributors > typically submit a chain of reviews for a given issue it makes sense for the > script to apply the whole chain recursively. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3282) Web UI no longer shows Tasks information
[ https://issues.apache.org/jira/browse/MESOS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901904#comment-14901904 ] haosdent commented on MESOS-3282: - If you really need it. You could download the patch from https://reviews.apache.org/r/38056/diff.raw And use "patch -p1 < rb38056.patch" to apply the patch. Make it committed need some times I think. > Web UI no longer shows Tasks information > > > Key: MESOS-3282 > URL: https://issues.apache.org/jira/browse/MESOS-3282 > Project: Mesos > Issue Type: Bug > Components: webui >Affects Versions: 0.23.0 >Reporter: Diogo Gomes >Assignee: haosdent > Attachments: task_infomartions.png > > > After update Mesos to 0.23 the Tasks box no longer shows info. Reading the > code, seems like it depends of state.json endpoint. In 0.22.1, it's possible > to see data like "failed_tasks" and"finished_tasks" and this is not present > anymore in 0.23.0 state.json, as is required in > https://github.com/apache/mesos/blob/a0811310c82ee25644fc9a6362313ce3619e46d9/src/webui/master/static/js/controllers.js#L126 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3282) Web UI no longer shows Tasks information
[ https://issues.apache.org/jira/browse/MESOS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901872#comment-14901872 ] Jeremy Olexa commented on MESOS-3282: - I understand that, hasodent. Do you know how we can suggest to get it committed or looked at? > Web UI no longer shows Tasks information > > > Key: MESOS-3282 > URL: https://issues.apache.org/jira/browse/MESOS-3282 > Project: Mesos > Issue Type: Bug > Components: webui >Affects Versions: 0.23.0 >Reporter: Diogo Gomes >Assignee: haosdent > Attachments: task_infomartions.png > > > After update Mesos to 0.23 the Tasks box no longer shows info. Reading the > code, seems like it depends of state.json endpoint. In 0.22.1, it's possible > to see data like "failed_tasks" and"finished_tasks" and this is not present > anymore in 0.23.0 state.json, as is required in > https://github.com/apache/mesos/blob/a0811310c82ee25644fc9a6362313ce3619e46d9/src/webui/master/static/js/controllers.js#L126 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3220) Offer ability to kill tasks from the API
[ https://issues.apache.org/jira/browse/MESOS-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901834#comment-14901834 ] Jian Qiu commented on MESOS-3220: - +1 for this API, and I have the same concern with [~vinodkone]: Can the task be killed in a more planned way like maintenance? Maybe this should be an API that schedule the task killing with a timer. So framework can be notified and kill task actively. If framework does not kill the taks, Mesos can enforce killing it after the timer expires. > Offer ability to kill tasks from the API > > > Key: MESOS-3220 > URL: https://issues.apache.org/jira/browse/MESOS-3220 > Project: Mesos > Issue Type: Improvement > Components: python api >Reporter: Sunil Shah >Assignee: Marco Massenzio >Priority: Blocker > Labels: mesosphere > > We are investigating adding a `dcos task kill` command to our DCOS (and > Mesos) command line interface. Currently the ability to kill tasks is only > offered via the scheduler API so it would be useful to have some ability to > kill tasks directly. > This is a blocker for the DCOS CLI! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901787#comment-14901787
]
chenqiang edited comment on MESOS-3079 at 9/22/15 2:09 AM:
---
The issue is fixed by instead of local loopback ip 127.0.0.1 with
ex.
$ ./bin/mesos-master.sh --ip=10.210.175.16 --work_dir=/var/lib/mesos
was (Author: chenqiang):
The issue is fixed by instead of local loopback ip 127.0.0.1 with
ex.
$ ./bin/mesos-master.sh --ip= --work_dir=/var/lib/mesos
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ]
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901787#comment-14901787
]
chenqiang commented on MESOS-3079:
--
The issue is fixed by instead of local loopback ip 127.0.0.1 with
ex.
$ ./bin/mesos-master.sh --ip= --work_dir=/var/lib/mesos
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::M
[jira] [Commented] (MESOS-3282) Web UI no longer shows Tasks information
[ https://issues.apache.org/jira/browse/MESOS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901785#comment-14901785 ] haosdent commented on MESOS-3282: - Because it is still not committed, I think it could not include in a bug fix release. > Web UI no longer shows Tasks information > > > Key: MESOS-3282 > URL: https://issues.apache.org/jira/browse/MESOS-3282 > Project: Mesos > Issue Type: Bug > Components: webui >Affects Versions: 0.23.0 >Reporter: Diogo Gomes >Assignee: haosdent > Attachments: task_infomartions.png > > > After update Mesos to 0.23 the Tasks box no longer shows info. Reading the > code, seems like it depends of state.json endpoint. In 0.22.1, it's possible > to see data like "failed_tasks" and"finished_tasks" and this is not present > anymore in 0.23.0 state.json, as is required in > https://github.com/apache/mesos/blob/a0811310c82ee25644fc9a6362313ce3619e46d9/src/webui/master/static/js/controllers.js#L126 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3486) Use DROP_PROTOBUF instead of DROP_MESSAGE in tests
Neil Conway created MESOS-3486: -- Summary: Use DROP_PROTOBUF instead of DROP_MESSAGE in tests Key: MESOS-3486 URL: https://issues.apache.org/jira/browse/MESOS-3486 Project: Mesos Issue Type: Improvement Reporter: Neil Conway Priority: Trivial The tests use DROP_MESSAGE(), DROP_MESSAGES(), and FUTURE_MESSAGE() in various places where it would be more clear and concise to use DROP_PROTOBUF(), DROP_PROTOBUFS(), and FUTURE_PROTOBUF() instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3282) Web UI no longer shows Tasks information
[ https://issues.apache.org/jira/browse/MESOS-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901777#comment-14901777 ] Jeremy Olexa commented on MESOS-3282: - Hi hasodent, thanks for working on this. Do you know how to get this included in a bug fix release? > Web UI no longer shows Tasks information > > > Key: MESOS-3282 > URL: https://issues.apache.org/jira/browse/MESOS-3282 > Project: Mesos > Issue Type: Bug > Components: webui >Affects Versions: 0.23.0 >Reporter: Diogo Gomes >Assignee: haosdent > Attachments: task_infomartions.png > > > After update Mesos to 0.23 the Tasks box no longer shows info. Reading the > code, seems like it depends of state.json endpoint. In 0.22.1, it's possible > to see data like "failed_tasks" and"finished_tasks" and this is not present > anymore in 0.23.0 state.json, as is required in > https://github.com/apache/mesos/blob/a0811310c82ee25644fc9a6362313ce3619e46d9/src/webui/master/static/js/controllers.js#L126 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2722) Create access to the Mesos "state abstraction" that does not require linking with libmesos
[ https://issues.apache.org/jira/browse/MESOS-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901746#comment-14901746 ] Neil Conway commented on MESOS-2722: Related issue; arguably a dup, although 2916 is a "story" and this is an "improvement". > Create access to the Mesos "state abstraction" that does not require linking > with libmesos > -- > > Key: MESOS-2722 > URL: https://issues.apache.org/jira/browse/MESOS-2722 > Project: Mesos > Issue Type: Improvement > Components: general >Reporter: Bernd Mathiske > Labels: features > > See "src/state/state.hpp" and "src/java/src/org/apache/mesos/state/*.java" > for what the "state abstraction" is. > With the new HTTP API (see MESOS-2288, MESOS-2289), there will be no need to > link to libmesos to a framework for it to communicate with a Mesos master. > However, if a framework uses the Mesos "state abstraction", either directly > in C++ or through other language bindings (e.g., Java), it still needs to > link with libmesos. So, in order to achieve libmesos-free frameworks that can > leverage all APIs Mesos has to offer, we need a different way to access the > "state abstraction". > --- > One approach is to provide an HTTP API for state queries that get routed > through the Mesos master, which relays them by making calls into libmesos. > Details TBD, including how separate this will be from the general HTTP API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2986) Docker version output is not compatible with Mesos
[ https://issues.apache.org/jira/browse/MESOS-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-2986: -- Fix Version/s: 0.23.1 > Docker version output is not compatible with Mesos > -- > > Key: MESOS-2986 > URL: https://issues.apache.org/jira/browse/MESOS-2986 > Project: Mesos > Issue Type: Bug > Components: docker >Reporter: Isabel Jimenez >Assignee: haosdent > Labels: mesosphere > Fix For: 0.23.0, 0.25.0, 0.24.1, 0.23.1 > > Attachments: MESOS-2986_0_22_1.patch > > > We currently use docker version to get Docker version, in Docker master > branch and soon in Docker 1.8 [1] the output for this command changes. The > solution for now will be to use the unchanged docker --version output, in the > long term we should consider stop using the cli and use the API instead. > [1] https://github.com/docker/docker/pull/14047 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3136) COMMAND health checks with Marathon 0.10.0 are broken
[ https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-3136: -- Fix Version/s: 0.23.1 > COMMAND health checks with Marathon 0.10.0 are broken > - > > Key: MESOS-3136 > URL: https://issues.apache.org/jira/browse/MESOS-3136 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.23.0 >Reporter: Dr. Stefan Schimanski >Assignee: haosdent >Priority: Critical > Fix For: 0.25.0, 0.24.1, 0.23.1 > > Attachments: MESOS-3136_0_23_0.patch, MESOS-3136_0_24_0.patch > > > When deploying Mesos 0.23rc4 with latest Marathon 0.10.0 RC3 command health > check stop working. Rolling back to Mesos 0.22.1 fixes the problem. > Containerizer is Docker. > All packages are from official Mesosphere Ubuntu 14.04 sources. > The issue must be analyzed further. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3485) Make hook execution order deterministic
Felix Abecassis created MESOS-3485:
--
Summary: Make hook execution order deterministic
Key: MESOS-3485
URL: https://issues.apache.org/jira/browse/MESOS-3485
Project: Mesos
Issue Type: Improvement
Components: modules
Reporter: Felix Abecassis
Currently, when using multiple hooks of the same type, the execution order is
implementation-defined.
This is because in src/hook/manager.cpp, the list of available hooks is stored
in a {{hashmap}}. A hashmap is probably unnecessary for this
task since the number of hooks should remain reasonable. A data structure
preserving ordering should be used instead to allow the user to predict the
execution order of the hooks. I suggest that the execution order should be the
order in which hooks are specified with {{--hooks}} when starting an
agent/master.
This will be useful when combining multiple hooks after MESOS-3366 is done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3037) Add a SUPPRESS call to the scheduler
[ https://issues.apache.org/jira/browse/MESOS-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901620#comment-14901620 ] Vinod Kone commented on MESOS-3037: --- commit 499f724fa479a781293613abcacbbeaf5f54cba1 Author: Guangya Liu Date: Mon Sep 21 16:32:59 2015 -0700 Added changelog for 0.25.0 release. This is a WIP CHANGLOG and only including one item of "add a suppress call to the scheduler", it should be updated in future to add more features in 0.25.0. Review: https://reviews.apache.org/r/38573 > Add a SUPPRESS call to the scheduler > > > Key: MESOS-3037 > URL: https://issues.apache.org/jira/browse/MESOS-3037 > Project: Mesos > Issue Type: Improvement >Affects Versions: 0.25.0 >Reporter: Vinod Kone >Assignee: Guangya Liu > Labels: September23th > Fix For: 0.25.0 > > > SUPPRESS call is the complement to the current REVIVE call i.e., it will > inform Mesos to stop sending offers to the framework. > For the scheduler driver to send only Call messages (MESOS-2913), > DeactivateFrameworkMessage needs to be converted to Call(s). We can implement > this by having the driver send a SUPPRESS call followed by a DECLINE call for > outstanding offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3476) Refactor Status Update method on Slave to handle HTTP based Executors
[
https://issues.apache.org/jira/browse/MESOS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isabel Jimenez reassigned MESOS-3476:
-
Assignee: Isabel Jimenez (was: Anand Mazumdar)
> Refactor Status Update method on Slave to handle HTTP based Executors
> -
>
> Key: MESOS-3476
> URL: https://issues.apache.org/jira/browse/MESOS-3476
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Isabel Jimenez
> Labels: mesosphere
>
> Currently, receiving a status update sent from slave to itself , {{runTask}}
> , {{killTask}} and status updates from executors are handled by the
> {{Slave::statusUpdate}} method on Slave. The signature of the method is
> {{void Slave::statusUpdate(StatusUpdate update, const UPID& pid)}}.
> We need to create another overload of it that can also handle HTTP based
> executors which the previous PID based function can also call into. The
> signature of the new function could be:
> {{void Slave::statusUpdate(StatusUpdate update, Executor* executor)}}
> The HTTP Executor would also call into this new function via
> {{src/slave/http.cpp}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3466) Add metrics for filesystem isolation and image provisioning.
[
https://issues.apache.org/jira/browse/MESOS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901610#comment-14901610
]
Yan Xu commented on MESOS-3466:
---
Given that the containerizer already has `container_destroy_errors` counter.
Here we should just add the errors that are masked by the provisioner and
backend.
Hence the following:
{noformat:title=}
containerizer/mesos/filesystem/linux/containers_new_rootfs
containerizer/mesos/provisioner/unmount_container_busy_errors
containerizer/mesos/provisioner/bind/unmount_rootfs_busy_errors
{noformat}
[~jieyu] Naming alright?
> Add metrics for filesystem isolation and image provisioning.
>
>
> Key: MESOS-3466
> URL: https://issues.apache.org/jira/browse/MESOS-3466
> Project: Mesos
> Issue Type: Task
>Reporter: Jie Yu
>Assignee: Yan Xu
> Labels: twitter
>
> We need to know about:
> 1) Errors encountered while provisioning root filesystems
> 2) Errors encountered while cleaning up root filesystems
> 3) Number of containers changing root filesystem
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2906) Slave : Synchronous Validation for Calls
[
https://issues.apache.org/jira/browse/MESOS-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isabel Jimenez updated MESOS-2906:
--
Sprint: Mesosphere Sprint 19
> Slave : Synchronous Validation for Calls
>
>
> Key: MESOS-2906
> URL: https://issues.apache.org/jira/browse/MESOS-2906
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Isabel Jimenez
> Labels: HTTP, mesosphere
>
> /call endpoint on the slave will return a 202 accepted code but has to do
> some basic validations before. In case of invalidation it will return a
> {{BadRequest}} back to the client.
> - We need to create the required infrastructure to validate the request and
> then process it similar to {{src/master/validation.cpp}} in the {{namespace
> scheduler}} i.e. check if the protobuf is properly initialized, has the
> required attributes set pertaining to the call message etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3183) Documentation images do not load
[
https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901580#comment-14901580
]
Joseph Wu edited comment on MESOS-3183 at 9/21/15 11:03 PM:
There are two problems:
* The website itself does not have the images. For this, we need to patch the
[website's generation file(s)|https://svn.apache.org/repos/asf/mesos/site/].
See attached {{rake.patch}}.
* The links will point to the incorrect image URL if there is a {{/}} at the
end of the page URL.
Fix: https://reviews.apache.org/r/38570/
was (Author: kaysoky):
This problem isn't limited to the Fetcher Cache. See:
* [External
Containerizer|http://mesos.apache.org/documentation/latest/external-containerizer/]
* [Fetcher Cache
Internals|http://mesos.apache.org/documentation/latest/fetcher-cache-internals/]
* [Maintenance|http://mesos.apache.org/documentation/latest/maintenance/]
*
[Oversubscription|http://mesos.apache.org/documentation/latest/oversubscription/]
There are two problems:
* The website itself does not have the images. For this, we need to patch the
[website's generation file(s)|https://svn.apache.org/repos/asf/mesos/site/].
See attached {{rake.patch}}.
* The links will point to the incorrect image URL if there is a {{/}} at the
end of the page URL.
Fix: https://reviews.apache.org/r/38570/
> Documentation images do not load
>
>
> Key: MESOS-3183
> URL: https://issues.apache.org/jira/browse/MESOS-3183
> Project: Mesos
> Issue Type: Documentation
> Components: documentation
>Affects Versions: 0.23.0
>Reporter: James Mulcahy
>Assignee: Joseph Wu
>Priority: Minor
> Attachments: rake.patch
>
>
> Any images which are referenced from the generated docs ({{docs/*.md}}) do
> not show up on the website. For example:
> * [External
> Containerizer|http://mesos.apache.org/documentation/latest/external-containerizer/]
> * [Fetcher Cache
> Internals|http://mesos.apache.org/documentation/latest/fetcher-cache-internals/]
> * [Maintenance|http://mesos.apache.org/documentation/latest/maintenance/]
> *
> [Oversubscription|http://mesos.apache.org/documentation/latest/oversubscription/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3183) Documentation images do not load
[
https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-3183:
-
Description:
Any images which are referenced from the generated docs ({{docs/*.md}}) do not
show up on the website. For example:
* [External
Containerizer|http://mesos.apache.org/documentation/latest/external-containerizer/]
* [Fetcher Cache
Internals|http://mesos.apache.org/documentation/latest/fetcher-cache-internals/]
* [Maintenance|http://mesos.apache.org/documentation/latest/maintenance/]
*
[Oversubscription|http://mesos.apache.org/documentation/latest/oversubscription/]
was:
The images on the Fetcher Cache Internals page do not load.
http://mesos.apache.org/documentation/fetcher-cache-internals/
> Documentation images do not load
>
>
> Key: MESOS-3183
> URL: https://issues.apache.org/jira/browse/MESOS-3183
> Project: Mesos
> Issue Type: Documentation
> Components: documentation
>Affects Versions: 0.23.0
>Reporter: James Mulcahy
>Assignee: Joseph Wu
>Priority: Minor
> Attachments: rake.patch
>
>
> Any images which are referenced from the generated docs ({{docs/*.md}}) do
> not show up on the website. For example:
> * [External
> Containerizer|http://mesos.apache.org/documentation/latest/external-containerizer/]
> * [Fetcher Cache
> Internals|http://mesos.apache.org/documentation/latest/fetcher-cache-internals/]
> * [Maintenance|http://mesos.apache.org/documentation/latest/maintenance/]
> *
> [Oversubscription|http://mesos.apache.org/documentation/latest/oversubscription/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3183) Documentation images do not load
[ https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu updated MESOS-3183: - Summary: Documentation images do not load (was: Fetcher Cache Internals documentation images do not load) > Documentation images do not load > > > Key: MESOS-3183 > URL: https://issues.apache.org/jira/browse/MESOS-3183 > Project: Mesos > Issue Type: Documentation > Components: documentation >Affects Versions: 0.23.0 >Reporter: James Mulcahy >Assignee: Joseph Wu >Priority: Minor > Attachments: rake.patch > > > The images on the Fetcher Cache Internals page do not load. > http://mesos.apache.org/documentation/fetcher-cache-internals/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3183) Fetcher Cache Internals documentation images do not load
[ https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu updated MESOS-3183: - Attachment: rake.patch > Fetcher Cache Internals documentation images do not load > > > Key: MESOS-3183 > URL: https://issues.apache.org/jira/browse/MESOS-3183 > Project: Mesos > Issue Type: Documentation > Components: documentation >Affects Versions: 0.23.0 >Reporter: James Mulcahy >Assignee: Joseph Wu >Priority: Minor > Attachments: rake.patch > > > The images on the Fetcher Cache Internals page do not load. > http://mesos.apache.org/documentation/fetcher-cache-internals/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3183) Fetcher Cache Internals documentation images do not load
[
https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901580#comment-14901580
]
Joseph Wu commented on MESOS-3183:
--
This problem isn't limited to the Fetcher Cache. See:
* [External
Containerizer|http://mesos.apache.org/documentation/latest/external-containerizer/]
* [Fetcher Cache
Internals|http://mesos.apache.org/documentation/latest/fetcher-cache-internals/]
* [Maintenance|http://mesos.apache.org/documentation/latest/maintenance/]
*
[Oversubscription|http://mesos.apache.org/documentation/latest/oversubscription/]
There are two problems:
* The website itself does not have the images. For this, we need to patch the
[website's generation file(s)|https://svn.apache.org/repos/asf/mesos/site/].
See attached {{rake.patch}}.
* The links will point to the incorrect image URL if there is a {{/}} at the
end of the page URL.
Fix: https://reviews.apache.org/r/38570/
> Fetcher Cache Internals documentation images do not load
>
>
> Key: MESOS-3183
> URL: https://issues.apache.org/jira/browse/MESOS-3183
> Project: Mesos
> Issue Type: Documentation
> Components: documentation
>Affects Versions: 0.23.0
>Reporter: James Mulcahy
>Assignee: Joseph Wu
>Priority: Minor
>
> The images on the Fetcher Cache Internals page do not load.
> http://mesos.apache.org/documentation/fetcher-cache-internals/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-3183) Fetcher Cache Internals documentation images do not load
[ https://issues.apache.org/jira/browse/MESOS-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu reassigned MESOS-3183: Assignee: Joseph Wu > Fetcher Cache Internals documentation images do not load > > > Key: MESOS-3183 > URL: https://issues.apache.org/jira/browse/MESOS-3183 > Project: Mesos > Issue Type: Documentation > Components: documentation >Affects Versions: 0.23.0 >Reporter: James Mulcahy >Assignee: Joseph Wu >Priority: Minor > > The images on the Fetcher Cache Internals page do not load. > http://mesos.apache.org/documentation/fetcher-cache-internals/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3468) Improve apply_reviews.sh script to apply chain of reviews
[ https://issues.apache.org/jira/browse/MESOS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu updated MESOS-3468: - Assignee: Artem Harutyunyan > Improve apply_reviews.sh script to apply chain of reviews > - > > Key: MESOS-3468 > URL: https://issues.apache.org/jira/browse/MESOS-3468 > Project: Mesos > Issue Type: Improvement >Reporter: Vinod Kone >Assignee: Artem Harutyunyan > > Currently the support/apply-review.sh script allows an user (typically > committer) to apply a single review on top the HEAD. Since Mesos contributors > typically submit a chain of reviews for a given issue it makes sense for the > script to apply the whole chain recursively. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3405) Add JSON::protobuf for google::protobuf::RepeatedPtrField.
[
https://issues.apache.org/jira/browse/MESOS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901566#comment-14901566
]
Joseph Wu commented on MESOS-3405:
--
Note: With this change, you can also remove this test helper:
https://github.com/apache/mesos/blob/master/src/tests/master_maintenance_tests.cpp#L93-L104
> Add JSON::protobuf for google::protobuf::RepeatedPtrField.
> --
>
> Key: MESOS-3405
> URL: https://issues.apache.org/jira/browse/MESOS-3405
> Project: Mesos
> Issue Type: Task
> Components: stout
>Reporter: Michael Park
>Assignee: Klaus Ma
>
> Currently, {{stout/protobuf.hpp}} provides a {{JSON::Protobuf}} utility which
> converts a {{google::protobuf::Message}} into a {{JSON::Object}}.
> We should add the support for {{google::protobuf::RepeatedPtrField}} by
> introducing overloaded functions.
> {code}
> namespace JSON {
> Object protobuf(const google::protobuf::Message& message)
> {
> Object object;
> /* Move the body of JSON::Protobuf constructor here. */
> return object;
> }
> template
> Array protobuf(const google::protobuf::RepeatedPtrField& repeated)
> {
> static_assert(std::is_convertible::value,
> "T must be a google::protobuf::Message");
> JSON::Array array;
> array.values.reserve(repeated.size());
> foreach (const T& elem, repeated) {
> array.values.push_back(JSON::Protobuf(elem));
> }
> return array;
> }
> }
> {code}
> The new {{RepeatedPtrField}} version can be used in at least the following
> places:
> * {{src/common/http.cpp}}
> * {{src/master/http.cpp}}
> * {{src/slave/containerizer/mesos/containerizer.cpp}}
> * {{src/tests/reservation_endpoints_tests.cpp}}
> * {{src/tests/resources_tests.cpp}}: {{ResourcesTest.ParsingFromJSON}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2226) HookTest.VerifySlaveLaunchExecutorHook is flaky
[
https://issues.apache.org/jira/browse/MESOS-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901552#comment-14901552
]
Niklas Quarfot Nielsen commented on MESOS-2226:
---
https://reviews.apache.org/r/38574/
> HookTest.VerifySlaveLaunchExecutorHook is flaky
> ---
>
> Key: MESOS-2226
> URL: https://issues.apache.org/jira/browse/MESOS-2226
> Project: Mesos
> Issue Type: Bug
> Components: test
>Affects Versions: 0.22.0
>Reporter: Vinod Kone
>Assignee: Kapil Arya
> Labels: flaky, flaky-test, mesosphere
>
> Observed this on internal CI
> {code}
> [ RUN ] HookTest.VerifySlaveLaunchExecutorHook
> Using temporary directory '/tmp/HookTest_VerifySlaveLaunchExecutorHook_GjBgME'
> I0114 18:51:34.659353 4720 leveldb.cpp:176] Opened db in 1.255951ms
> I0114 18:51:34.662112 4720 leveldb.cpp:183] Compacted db in 596090ns
> I0114 18:51:34.662364 4720 leveldb.cpp:198] Created db iterator in 177877ns
> I0114 18:51:34.662719 4720 leveldb.cpp:204] Seeked to beginning of db in
> 19709ns
> I0114 18:51:34.663010 4720 leveldb.cpp:273] Iterated through 0 keys in the
> db in 18208ns
> I0114 18:51:34.663312 4720 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0114 18:51:34.664266 4735 recover.cpp:449] Starting replica recovery
> I0114 18:51:34.664908 4735 recover.cpp:475] Replica is in EMPTY status
> I0114 18:51:34.667842 4734 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I0114 18:51:34.669117 4735 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I0114 18:51:34.677913 4735 recover.cpp:566] Updating replica status to
> STARTING
> I0114 18:51:34.683157 4735 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 137939ns
> I0114 18:51:34.683507 4735 replica.cpp:323] Persisted replica status to
> STARTING
> I0114 18:51:34.684013 4735 recover.cpp:475] Replica is in STARTING status
> I0114 18:51:34.685554 4738 replica.cpp:641] Replica in STARTING status
> received a broadcasted recover request
> I0114 18:51:34.696512 4736 recover.cpp:195] Received a recover response from
> a replica in STARTING status
> I0114 18:51:34.700552 4735 recover.cpp:566] Updating replica status to VOTING
> I0114 18:51:34.701128 4735 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 115624ns
> I0114 18:51:34.701478 4735 replica.cpp:323] Persisted replica status to
> VOTING
> I0114 18:51:34.701817 4735 recover.cpp:580] Successfully joined the Paxos
> group
> I0114 18:51:34.702569 4735 recover.cpp:464] Recover process terminated
> I0114 18:51:34.716439 4736 master.cpp:262] Master
> 20150114-185134-2272962752-57018-4720 (fedora-19) started on
> 192.168.122.135:57018
> I0114 18:51:34.716913 4736 master.cpp:308] Master only allowing
> authenticated frameworks to register
> I0114 18:51:34.717136 4736 master.cpp:313] Master only allowing
> authenticated slaves to register
> I0114 18:51:34.717488 4736 credentials.hpp:36] Loading credentials for
> authentication from
> '/tmp/HookTest_VerifySlaveLaunchExecutorHook_GjBgME/credentials'
> I0114 18:51:34.718077 4736 master.cpp:357] Authorization enabled
> I0114 18:51:34.719238 4738 whitelist_watcher.cpp:65] No whitelist given
> I0114 18:51:34.719755 4737 hierarchical_allocator_process.hpp:285]
> Initialized hierarchical allocator process
> I0114 18:51:34.722584 4736 master.cpp:1219] The newly elected leader is
> master@192.168.122.135:57018 with id 20150114-185134-2272962752-57018-4720
> I0114 18:51:34.722865 4736 master.cpp:1232] Elected as the leading master!
> I0114 18:51:34.723310 4736 master.cpp:1050] Recovering from registrar
> I0114 18:51:34.723760 4734 registrar.cpp:313] Recovering registrar
> I0114 18:51:34.725229 4740 log.cpp:660] Attempting to start the writer
> I0114 18:51:34.727893 4739 replica.cpp:477] Replica received implicit
> promise request with proposal 1
> I0114 18:51:34.728425 4739 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 114781ns
> I0114 18:51:34.728662 4739 replica.cpp:345] Persisted promised to 1
> I0114 18:51:34.731271 4741 coordinator.cpp:230] Coordinator attemping to
> fill missing position
> I0114 18:51:34.733223 4734 replica.cpp:378] Replica received explicit
> promise request for position 0 with proposal 2
> I0114 18:51:34.734076 4734 leveldb.cpp:343] Persisting action (8 bytes) to
> leveldb took 87441ns
> I0114 18:51:34.734441 4734 replica.cpp:679] Persisted action at 0
> I0114 18:51:34.740272 4739 replica.cpp:511] Replica received write request
> for position 0
> I0114 18:51:34.740910 4739 leveldb.cpp:438] Reading position from leveldb
> took 59846ns
> I0114 18:51:34.741672 4739 leveldb.cpp:343] Persisting action (14
[jira] [Updated] (MESOS-2995) Standardize use of Path
[ https://issues.apache.org/jira/browse/MESOS-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu updated MESOS-2995: - Assignee: (was: Joseph Wu) > Standardize use of Path > > > Key: MESOS-2995 > URL: https://issues.apache.org/jira/browse/MESOS-2995 > Project: Mesos > Issue Type: Improvement > Components: stout >Reporter: Joseph Wu >Priority: Minor > Labels: mesosphere, newbie, stout > > As per the discussion in MESOS-2965, the use of the Path object should be > standardized: > * Functions which effectively use Paths (as strings) should instead take > Paths. > * Functions which modify and return Paths (as strings) should instead return > Paths. > * Extraneous uses of Path.value should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2930) Allow the Resource Estimator to express over-allocation of revocable resources.
[ https://issues.apache.org/jira/browse/MESOS-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901503#comment-14901503 ] Benjamin Mahler commented on MESOS-2930: My understanding was that we already have to do some sharing of information across the estimator and qos controller to make good estimates. Is that not the case? It seems necessary already to share information in order to build a good combination of estimator + qos controller. How does serenity solve this? > Allow the Resource Estimator to express over-allocation of revocable > resources. > --- > > Key: MESOS-2930 > URL: https://issues.apache.org/jira/browse/MESOS-2930 > Project: Mesos > Issue Type: Improvement > Components: slave >Reporter: Benjamin Mahler >Assignee: Klaus Ma > > Currently the resource estimator returns the amount of oversubscription > resources that are available, since resources cannot be negative, this allows > the resource estimator to express the following: > (1) Return empty resources: We are fully allocated for oversubscription > resources. > (2) Return non-empty resources: We are under-allocated for oversubscription > resources. In other words, some are available. > However, there is an additional situation that we cannot express: > (3) Analogous to returning non-empty "negative" resources: We are > over-allocated for oversubscription resources. Do not re-offer any of the > over-allocated oversubscription resources that are recovered. > Without (3), the slave can only shrink the total pool of oversubscription > resources by returning (1) as resources are recovered, until the pool is > shrunk to the desired size. However, this approach is only best-effort, it's > possible for a framework to launch more tasks in the window of time (15 > seconds by default) that the slave polls the estimator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3474) ExamplesTest.{TestFramework, JavaFramework, PythonFramework} failed on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901497#comment-14901497
]
Jie Yu commented on MESOS-3474:
---
commit 57361f10ccf1e026dbb691e67277cb0cb71c8ea6
Author: haosdent huang
Date: Mon Sep 21 14:27:34 2015 -0700
Allocated the stack used by clone dynamically.
This is to address the issue when running multiple slaves during tests.
The glibc 'clone' will modify the stack passed to it, therefore we
cannot use a shared stack.
Review: https://reviews.apache.org/r/38535
> ExamplesTest.{TestFramework, JavaFramework, PythonFramework} failed on CentOS
> 6
> ---
>
> Key: MESOS-3474
> URL: https://issues.apache.org/jira/browse/MESOS-3474
> Project: Mesos
> Issue Type: Bug
>Reporter: haosdent
>Assignee: haosdent
>
> When use linux_launcher.cpp, ExamplesTest.{TestFramework, JavaFramework,
> PythonFramework} failed.
> {code}
> I0920 11:19:04.093004 9939 containerizer.cpp:625] Starting container
> 'a6c38fef-56c1-4cd7-a99c-252315651500' for executor 'default' of framework
> '198942f1-00fe-47aa-b61f-6906bece2250-'[105/1921]
> I0920 11:19:04.098449 9945 linux_launcher.cpp:189] Cloning child process
> with flags =
> I0920 11:19:04.098449 9946 linux_launcher.cpp:189] Cloning child process
> with flags =
> I0920 11:19:04.098453 9943 linux_launcher.cpp:189] Cloning child process
> with flags =
> ABORT: (../../src/slave/containerizer/linux_launcher.cpp:215): Failed to
> synchronize with parent*** Aborted at 1442719144 (unix time) try "date -d
> @1442719144" if you are using GNU date ***
> ABORT: (../../src/slave/containerizer/linux_launcher.cpp:215): Failed to
> synchronize with parent*** Aborted at 1442719144 (unix time) try "date -d
> @1442719144" if you are using GNU date ***
> PC: @ 0x3e3b832625 (unknown)
> *** SIGABRT (@0x26ec) received by PID 9964 (TID 0x7fcf576d6700) from PID
> 9964; stack trace: ***
> @ 0x3e3c00f710 (unknown)
> @ 0x3e3b832625 (unknown)
> PC: @ 0x3e3b832625 (unknown)
> *** SIGABRT (@0x26eb) received by PID 9963 (TID 0x7fcf558d3700) from PID
> 9963; stack trace: ***
> @ 0x3e3b833e05 (unknown)
> @ 0x3e3c00f710 (unknown)
> @ 0x429c4f _Abort()
> @ 0x3e3b832625 (unknown)
> @ 0x3e3b833e05 (unknown)
> @ 0x429c4f _Abort()
> @ 0x7fcf5e12f6bb mesos::internal::slave::childSetup()
> @ 0x7fcf5e12f6bb mesos::internal::slave::childSetup()
> @ 0x7fcf5e13749e
> _ZNSt5_BindIFPFiPiRK6OptionISt8functionIFivS0_S5_EE6__callIiIEILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e13749e
> _ZNSt5_BindIFPFiPiRK6OptionISt8functionIFivS0_S5_EE6__callIiIEILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e135f0e std::_Bind<>::operator()<>()
> @ 0x7fcf5e135f0e std::_Bind<>::operator()<>()
> @ 0x7fcf5e134e1a std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5e134e1a std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5e5d32fd process::childMain()
> @ 0x7fcf5e5d32fd process::childMain()
> @ 0x7fcf5e5d8808
> _ZNSt5_BindIFPFiRKSsPPcRKN7process10Subprocess2IOES8_S8_S3_RK6OptionISt8functionIFivEEEPiSG_SG_ESsS3_S6_S6_S6_S3_SD_SG_SG_SG_EE6__callIiIEILm0ELm1ELm2ELm3ELm4ELm5ELm6ELm7ELm8ELm
> 9T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e5d8808
> _ZNSt5_BindIFPFiRKSsPPcRKN7process10Subprocess2IOES8_S8_S3_RK6OptionISt8functionIFivEEEPiSG_SG_ESsS3_S6_S6_S6_S3_SD_SG_SG_SG_EE6__callIiIEILm0ELm1ELm2ELm3ELm4ELm5ELm6ELm7ELm8ELm
> 9T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e5d7dfc std::_Bind<>::operator()<>()
> @ 0x7fcf5e5d7dfc std::_Bind<>::operator()<>()
> @ 0x7fcf5e5d730c std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5e5d730c std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5e12f503 mesos::internal::slave::childMain()
> @ 0x7fcf5e12f503 mesos::internal::slave::childMain()
> @ 0x3e3b8e88fd (unknown)
> @ 0x3e3b8e88fd (unknown)
> I0920 11:19:05.007531 9939 containerizer.cpp:1264] Executor for container
> '93444030-9db9-404c-9448-54b49f174d02' has exited
> I0920 11:19:05.007587 9939 containerizer.cpp:1077] Destroying container
> '93444030-9db9-404c-9448-54b49f174d02'
> I0920 11:19:05.011742 9940 cgroups.cpp:2433] Freezing cgroup
> /cgroup/freezer/mesos/93444030-9db9-404c-9448-54b49f174d02
> {code}
--
This message was sent by Atlassian J
[jira] [Updated] (MESOS-3484) Master failed to shutdown: failed on fd: Transport endpoint is not connected.
[ https://issues.apache.org/jira/browse/MESOS-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Zhang updated MESOS-3484: - Summary: Master failed to shutdown: failed on fd: Transport endpoint is not connected. (was: Master Failed to Shutdown failed on fd: Transport endpoint is not connected.) > Master failed to shutdown: failed on fd: Transport endpoint is not connected. > - > > Key: MESOS-3484 > URL: https://issues.apache.org/jira/browse/MESOS-3484 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.24.0 >Reporter: Chi Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3484) Master Failed to Shutdown failed on fd: Transport endpoint is not connected.
[
https://issues.apache.org/jira/browse/MESOS-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901447#comment-14901447
]
Chi Zhang commented on MESOS-3484:
--
The below was seen in Twitter production in the master log, but unfortunately,
the surrounding log doesn't provide relevant information.
{code}
E0921 18:00:08.238836 9568 socket.hpp:173] Shutdown failed on fd=53721:
Transport endpoint is not connected [107]
{code}
> Master Failed to Shutdown failed on fd: Transport endpoint is not connected.
>
>
> Key: MESOS-3484
> URL: https://issues.apache.org/jira/browse/MESOS-3484
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.24.0
>Reporter: Chi Zhang
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3484) Master Failed to Shutdown failed on fd: Transport endpoint is not connected.
[ https://issues.apache.org/jira/browse/MESOS-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Zhang updated MESOS-3484: - Summary: Master Failed to Shutdown failed on fd: Transport endpoint is not connected. (was: Master: E0921 18:00:08.238836 9568 socket.hpp:173] Shutdown failed on fd=53721: Transport endpoint is not connected [107]) > Master Failed to Shutdown failed on fd: Transport endpoint is not connected. > > > Key: MESOS-3484 > URL: https://issues.apache.org/jira/browse/MESOS-3484 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.24.0 >Reporter: Chi Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3459) Change /machine/up and /machine/down endpoints to take an array
[
https://issues.apache.org/jira/browse/MESOS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-3459:
-
Story Points: 1
> Change /machine/up and /machine/down endpoints to take an array
> ---
>
> Key: MESOS-3459
> URL: https://issues.apache.org/jira/browse/MESOS-3459
> Project: Mesos
> Issue Type: Task
> Components: master
>Reporter: Joseph Wu
>Assignee: Joseph Wu
> Labels: mesosphere
>
> With [MESOS-3312] committed, the {{/machine/up}} and {{/machine/down}}
> endpoints should also take an input as an array.
> It is important to change this before maintenance primitives are released:
> https://reviews.apache.org/r/38011/
> Also, a minor change to the error message from these endpoints:
> https://reviews.apache.org/r/37969/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3458) Segfault when accepting or declining inverse offers
[ https://issues.apache.org/jira/browse/MESOS-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu updated MESOS-3458: - Story Points: 1 > Segfault when accepting or declining inverse offers > --- > > Key: MESOS-3458 > URL: https://issues.apache.org/jira/browse/MESOS-3458 > Project: Mesos > Issue Type: Bug > Components: master >Reporter: Joseph Wu >Assignee: Joseph Wu >Priority: Blocker > Labels: mesosphere > > Discovered while writing a test for filters (in regards to inverse offers). > Fix here: https://reviews.apache.org/r/38470/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3474) ExamplesTest.{TestFramework, JavaFramework, PythonFramework} failed on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901278#comment-14901278
]
Kapil Arya commented on MESOS-3474:
---
Hey [~haosd...@gmail.com]: Can you set 0.25.0 as the target release for this
patch so that we can get it in?
> ExamplesTest.{TestFramework, JavaFramework, PythonFramework} failed on CentOS
> 6
> ---
>
> Key: MESOS-3474
> URL: https://issues.apache.org/jira/browse/MESOS-3474
> Project: Mesos
> Issue Type: Bug
>Reporter: haosdent
>Assignee: haosdent
>
> When use linux_launcher.cpp, ExamplesTest.{TestFramework, JavaFramework,
> PythonFramework} failed.
> {code}
> I0920 11:19:04.093004 9939 containerizer.cpp:625] Starting container
> 'a6c38fef-56c1-4cd7-a99c-252315651500' for executor 'default' of framework
> '198942f1-00fe-47aa-b61f-6906bece2250-'[105/1921]
> I0920 11:19:04.098449 9945 linux_launcher.cpp:189] Cloning child process
> with flags =
> I0920 11:19:04.098449 9946 linux_launcher.cpp:189] Cloning child process
> with flags =
> I0920 11:19:04.098453 9943 linux_launcher.cpp:189] Cloning child process
> with flags =
> ABORT: (../../src/slave/containerizer/linux_launcher.cpp:215): Failed to
> synchronize with parent*** Aborted at 1442719144 (unix time) try "date -d
> @1442719144" if you are using GNU date ***
> ABORT: (../../src/slave/containerizer/linux_launcher.cpp:215): Failed to
> synchronize with parent*** Aborted at 1442719144 (unix time) try "date -d
> @1442719144" if you are using GNU date ***
> PC: @ 0x3e3b832625 (unknown)
> *** SIGABRT (@0x26ec) received by PID 9964 (TID 0x7fcf576d6700) from PID
> 9964; stack trace: ***
> @ 0x3e3c00f710 (unknown)
> @ 0x3e3b832625 (unknown)
> PC: @ 0x3e3b832625 (unknown)
> *** SIGABRT (@0x26eb) received by PID 9963 (TID 0x7fcf558d3700) from PID
> 9963; stack trace: ***
> @ 0x3e3b833e05 (unknown)
> @ 0x3e3c00f710 (unknown)
> @ 0x429c4f _Abort()
> @ 0x3e3b832625 (unknown)
> @ 0x3e3b833e05 (unknown)
> @ 0x429c4f _Abort()
> @ 0x7fcf5e12f6bb mesos::internal::slave::childSetup()
> @ 0x7fcf5e12f6bb mesos::internal::slave::childSetup()
> @ 0x7fcf5e13749e
> _ZNSt5_BindIFPFiPiRK6OptionISt8functionIFivS0_S5_EE6__callIiIEILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e13749e
> _ZNSt5_BindIFPFiPiRK6OptionISt8functionIFivS0_S5_EE6__callIiIEILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e135f0e std::_Bind<>::operator()<>()
> @ 0x7fcf5e135f0e std::_Bind<>::operator()<>()
> @ 0x7fcf5e134e1a std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5e134e1a std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5e5d32fd process::childMain()
> @ 0x7fcf5e5d32fd process::childMain()
> @ 0x7fcf5e5d8808
> _ZNSt5_BindIFPFiRKSsPPcRKN7process10Subprocess2IOES8_S8_S3_RK6OptionISt8functionIFivEEEPiSG_SG_ESsS3_S6_S6_S6_S3_SD_SG_SG_SG_EE6__callIiIEILm0ELm1ELm2ELm3ELm4ELm5ELm6ELm7ELm8ELm
> 9T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e5d8808
> _ZNSt5_BindIFPFiRKSsPPcRKN7process10Subprocess2IOES8_S8_S3_RK6OptionISt8functionIFivEEEPiSG_SG_ESsS3_S6_S6_S6_S3_SD_SG_SG_SG_EE6__callIiIEILm0ELm1ELm2ELm3ELm4ELm5ELm6ELm7ELm8ELm
> 9T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e5d7dfc std::_Bind<>::operator()<>()
> @ 0x7fcf5e5d7dfc std::_Bind<>::operator()<>()
> @ 0x7fcf5e5d730c std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5e5d730c std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5e12f503 mesos::internal::slave::childMain()
> @ 0x7fcf5e12f503 mesos::internal::slave::childMain()
> @ 0x3e3b8e88fd (unknown)
> @ 0x3e3b8e88fd (unknown)
> I0920 11:19:05.007531 9939 containerizer.cpp:1264] Executor for container
> '93444030-9db9-404c-9448-54b49f174d02' has exited
> I0920 11:19:05.007587 9939 containerizer.cpp:1077] Destroying container
> '93444030-9db9-404c-9448-54b49f174d02'
> I0920 11:19:05.011742 9940 cgroups.cpp:2433] Freezing cgroup
> /cgroup/freezer/mesos/93444030-9db9-404c-9448-54b49f174d02
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3474) ExamplesTest.{TestFramework, JavaFramework, PythonFramework} failed on CentOS 6
[
https://issues.apache.org/jira/browse/MESOS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapil Arya updated MESOS-3474:
--
Target Version/s: 0.25.0
> ExamplesTest.{TestFramework, JavaFramework, PythonFramework} failed on CentOS
> 6
> ---
>
> Key: MESOS-3474
> URL: https://issues.apache.org/jira/browse/MESOS-3474
> Project: Mesos
> Issue Type: Bug
>Reporter: haosdent
>Assignee: haosdent
>
> When use linux_launcher.cpp, ExamplesTest.{TestFramework, JavaFramework,
> PythonFramework} failed.
> {code}
> I0920 11:19:04.093004 9939 containerizer.cpp:625] Starting container
> 'a6c38fef-56c1-4cd7-a99c-252315651500' for executor 'default' of framework
> '198942f1-00fe-47aa-b61f-6906bece2250-'[105/1921]
> I0920 11:19:04.098449 9945 linux_launcher.cpp:189] Cloning child process
> with flags =
> I0920 11:19:04.098449 9946 linux_launcher.cpp:189] Cloning child process
> with flags =
> I0920 11:19:04.098453 9943 linux_launcher.cpp:189] Cloning child process
> with flags =
> ABORT: (../../src/slave/containerizer/linux_launcher.cpp:215): Failed to
> synchronize with parent*** Aborted at 1442719144 (unix time) try "date -d
> @1442719144" if you are using GNU date ***
> ABORT: (../../src/slave/containerizer/linux_launcher.cpp:215): Failed to
> synchronize with parent*** Aborted at 1442719144 (unix time) try "date -d
> @1442719144" if you are using GNU date ***
> PC: @ 0x3e3b832625 (unknown)
> *** SIGABRT (@0x26ec) received by PID 9964 (TID 0x7fcf576d6700) from PID
> 9964; stack trace: ***
> @ 0x3e3c00f710 (unknown)
> @ 0x3e3b832625 (unknown)
> PC: @ 0x3e3b832625 (unknown)
> *** SIGABRT (@0x26eb) received by PID 9963 (TID 0x7fcf558d3700) from PID
> 9963; stack trace: ***
> @ 0x3e3b833e05 (unknown)
> @ 0x3e3c00f710 (unknown)
> @ 0x429c4f _Abort()
> @ 0x3e3b832625 (unknown)
> @ 0x3e3b833e05 (unknown)
> @ 0x429c4f _Abort()
> @ 0x7fcf5e12f6bb mesos::internal::slave::childSetup()
> @ 0x7fcf5e12f6bb mesos::internal::slave::childSetup()
> @ 0x7fcf5e13749e
> _ZNSt5_BindIFPFiPiRK6OptionISt8functionIFivS0_S5_EE6__callIiIEILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e13749e
> _ZNSt5_BindIFPFiPiRK6OptionISt8functionIFivS0_S5_EE6__callIiIEILm0ELm1T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e135f0e std::_Bind<>::operator()<>()
> @ 0x7fcf5e135f0e std::_Bind<>::operator()<>()
> @ 0x7fcf5e134e1a std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5e134e1a std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5e5d32fd process::childMain()
> @ 0x7fcf5e5d32fd process::childMain()
> @ 0x7fcf5e5d8808
> _ZNSt5_BindIFPFiRKSsPPcRKN7process10Subprocess2IOES8_S8_S3_RK6OptionISt8functionIFivEEEPiSG_SG_ESsS3_S6_S6_S6_S3_SD_SG_SG_SG_EE6__callIiIEILm0ELm1ELm2ELm3ELm4ELm5ELm6ELm7ELm8ELm
> 9T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e5d8808
> _ZNSt5_BindIFPFiRKSsPPcRKN7process10Subprocess2IOES8_S8_S3_RK6OptionISt8functionIFivEEEPiSG_SG_ESsS3_S6_S6_S6_S3_SD_SG_SG_SG_EE6__callIiIEILm0ELm1ELm2ELm3ELm4ELm5ELm6ELm7ELm8ELm
> 9T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x7fcf5e5d7dfc std::_Bind<>::operator()<>()
> @ 0x7fcf5e5d7dfc std::_Bind<>::operator()<>()
> @ 0x7fcf5e5d730c std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5e5d730c std::_Function_handler<>::_M_invoke()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5def852c std::function<>::operator()()
> @ 0x7fcf5e12f503 mesos::internal::slave::childMain()
> @ 0x7fcf5e12f503 mesos::internal::slave::childMain()
> @ 0x3e3b8e88fd (unknown)
> @ 0x3e3b8e88fd (unknown)
> I0920 11:19:05.007531 9939 containerizer.cpp:1264] Executor for container
> '93444030-9db9-404c-9448-54b49f174d02' has exited
> I0920 11:19:05.007587 9939 containerizer.cpp:1077] Destroying container
> '93444030-9db9-404c-9448-54b49f174d02'
> I0920 11:19:05.011742 9940 cgroups.cpp:2433] Freezing cgroup
> /cgroup/freezer/mesos/93444030-9db9-404c-9448-54b49f174d02
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3037) Add a SUPPRESS call to the scheduler
[ https://issues.apache.org/jira/browse/MESOS-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901248#comment-14901248 ] Vinod Kone commented on MESOS-3037: --- commit a2e740d36550b1bf7f6fe9ad3ec0242a7f9d7a74 Author: Guangya Liu Date: Mon Sep 21 12:10:20 2015 -0700 Changed function quiesce() to suppress(). Review: https://reviews.apache.org/r/38519 commit 9d15cd3eb9243abf07947b266a43791ce8d11d1e Author: Guangya Liu Date: Mon Sep 21 12:09:19 2015 -0700 libprocess: Renamed suppress macro to SUPPRESS. The macro suppress conflicts with suppress() for a call in master. This patch updates macro suppress to SUPPRESS to resolve the conflict. Review: https://reviews.apache.org/r/38544 commit 10ac36a15dad689bfc60741a8389aea2b55a8760 Author: Guangya Liu Date: Mon Sep 21 12:04:29 2015 -0700 Changed quiesceOffers to SuppressOffers. Review: https://reviews.apache.org/r/38516 commit 705d6b57cf75373051fb7428aca00861fcca0b7b Author: Guangya Liu Date: Mon Sep 21 12:03:55 2015 -0700 Updated QUIESCE to SUPPRESS in Mesos Call. Review: https://reviews.apache.org/r/38514 > Add a SUPPRESS call to the scheduler > > > Key: MESOS-3037 > URL: https://issues.apache.org/jira/browse/MESOS-3037 > Project: Mesos > Issue Type: Improvement >Affects Versions: 0.25.0 >Reporter: Vinod Kone >Assignee: Guangya Liu > Labels: September23th > Fix For: 0.25.0 > > > SUPPRESS call is the complement to the current REVIVE call i.e., it will > inform Mesos to stop sending offers to the framework. > For the scheduler driver to send only Call messages (MESOS-2913), > DeactivateFrameworkMessage needs to be converted to Call(s). We can implement > this by having the driver send a SUPPRESS call followed by a DECLINE call for > outstanding offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2916) Expose State API via HTTP
[ https://issues.apache.org/jira/browse/MESOS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901222#comment-14901222 ] Adam B commented on MESOS-2916: --- For reference: https://github.com/apache/mesos/blob/0.24.0/src/state/state.hpp > Expose State API via HTTP > - > > Key: MESOS-2916 > URL: https://issues.apache.org/jira/browse/MESOS-2916 > Project: Mesos > Issue Type: Story >Reporter: Tomás Senart > Labels: http > > The State API is a useful service for frameworks to use. It would make sense > to have it available via the public HTTP API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3484) Master: E0921 18:00:08.238836 9568 socket.hpp:173] Shutdown failed on fd=53721: Transport endpoint is not connected [107]
[ https://issues.apache.org/jira/browse/MESOS-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Zhang updated MESOS-3484: - Affects Version/s: 0.24.0 > Master: E0921 18:00:08.238836 9568 socket.hpp:173] Shutdown failed on > fd=53721: Transport endpoint is not connected [107] > -- > > Key: MESOS-3484 > URL: https://issues.apache.org/jira/browse/MESOS-3484 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.24.0 >Reporter: Chi Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3484) Master: E0921 18:00:08.238836 9568 socket.hpp:173] Shutdown failed on fd=53721: Transport endpoint is not connected [107]
Chi Zhang created MESOS-3484: Summary: Master: E0921 18:00:08.238836 9568 socket.hpp:173] Shutdown failed on fd=53721: Transport endpoint is not connected [107] Key: MESOS-3484 URL: https://issues.apache.org/jira/browse/MESOS-3484 Project: Mesos Issue Type: Bug Reporter: Chi Zhang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3366) Allow resources/attributes discovery
[ https://issues.apache.org/jira/browse/MESOS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901147#comment-14901147 ] Felix Abecassis commented on MESOS-3366: I managed to create the 3rd patch using the post-reviews.py script: https://reviews.apache.org/r/38564/ Very similar to the initial patch, and is even reusing the same test (this could be changed). > Allow resources/attributes discovery > > > Key: MESOS-3366 > URL: https://issues.apache.org/jira/browse/MESOS-3366 > Project: Mesos > Issue Type: Improvement > Components: slave >Reporter: Felix Abecassis > > In heterogeneous clusters, tasks sometimes have strong constraints on the > type of hardware they need to execute on. The current solution is to use > custom resources and attributes on the agents. Detecting non-standard > resources/attributes requires wrapping the "mesos-slave" binary behind a > script and use custom code to probe the agent. Unfortunately, this approach > doesn't allow composition. The solution would be to provide a hook/module > mechanism to allow users to use custom code performing resources/attributes > discovery. > Please review the detailed document below: > https://docs.google.com/document/d/15OkebDezFxzeyLsyQoU0upB0eoVECAlzEkeg0HQAX9w > Feel free to express comments/concerns by annotating the document or by > replying to this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[
https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu reassigned MESOS-3483:
-
Assignee: Jie Yu
> LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
>
>
> Key: MESOS-3483
> URL: https://issues.apache.org/jira/browse/MESOS-3483
> Project: Mesos
> Issue Type: Bug
>Reporter: Jie Yu
>Assignee: Jie Yu
>
> So that when a user task is forked, it does not hold extra references to the
> sandbox mount and provisioner bind backend mounts. If we don't do that, we
> could get the following error message when cleaning up bind backend mount
> points and sandbox mount points.
> {noformat}
> E0921 17:35:57.268159 47010 bind.cpp:182] Failed to remove rootfs mount point
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a/backends/bind/rootfses/30f7e5e2-55d0-4d4d-a662-f8aad0d56b33':
> Device or resource busy
> E0921 17:35:57.268349 47010 provisioner.cpp:403] Failed to remove the
> provisioned container directory at
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a':
> Device or resource busy
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[
https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-3483:
--
Story Points: 2
> LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
>
>
> Key: MESOS-3483
> URL: https://issues.apache.org/jira/browse/MESOS-3483
> Project: Mesos
> Issue Type: Bug
>Reporter: Jie Yu
>Assignee: Jie Yu
>
> So that when a user task is forked, it does not hold extra references to the
> sandbox mount and provisioner bind backend mounts. If we don't do that, we
> could get the following error message when cleaning up bind backend mount
> points and sandbox mount points.
> {noformat}
> E0921 17:35:57.268159 47010 bind.cpp:182] Failed to remove rootfs mount point
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a/backends/bind/rootfses/30f7e5e2-55d0-4d4d-a662-f8aad0d56b33':
> Device or resource busy
> E0921 17:35:57.268349 47010 provisioner.cpp:403] Failed to remove the
> provisioned container directory at
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a':
> Device or resource busy
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3466) Add metrics for filesystem isolation and image provisioning.
[ https://issues.apache.org/jira/browse/MESOS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Xu updated MESOS-3466: -- Sprint: Twitter Mesos Q3 Sprint 5 > Add metrics for filesystem isolation and image provisioning. > > > Key: MESOS-3466 > URL: https://issues.apache.org/jira/browse/MESOS-3466 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Yan Xu > Labels: twitter > > We need to know about: > 1) Errors encountered while provisioning root filesystems > 2) Errors encountered while cleaning up root filesystems > 3) Number of containers changing root filesystem > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3466) Add metrics for filesystem isolation and image provisioning.
[ https://issues.apache.org/jira/browse/MESOS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Xu updated MESOS-3466: -- Labels: twitter (was: ) > Add metrics for filesystem isolation and image provisioning. > > > Key: MESOS-3466 > URL: https://issues.apache.org/jira/browse/MESOS-3466 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Yan Xu > Labels: twitter > > We need to know about: > 1) Errors encountered while provisioning root filesystems > 2) Errors encountered while cleaning up root filesystems > 3) Number of containers changing root filesystem > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3466) Add metrics for filesystem isolation and image provisioning.
[ https://issues.apache.org/jira/browse/MESOS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Xu reassigned MESOS-3466: - Assignee: Yan Xu > Add metrics for filesystem isolation and image provisioning. > > > Key: MESOS-3466 > URL: https://issues.apache.org/jira/browse/MESOS-3466 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Yan Xu > > We need to know about: > 1) Errors encountered while provisioning root filesystems > 2) Errors encountered while cleaning up root filesystems > 3) Number of containers changing root filesystem > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[
https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901125#comment-14901125
]
haosdent commented on MESOS-3483:
-
Could use http://asciiflow.com/ :-)
> LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
>
>
> Key: MESOS-3483
> URL: https://issues.apache.org/jira/browse/MESOS-3483
> Project: Mesos
> Issue Type: Bug
>Reporter: Jie Yu
>
> So that when a user task is forked, it does not hold extra references to the
> sandbox mount and provisioner bind backend mounts. If we don't do that, we
> could get the following error message when cleaning up bind backend mount
> points and sandbox mount points.
> {noformat}
> E0921 17:35:57.268159 47010 bind.cpp:182] Failed to remove rootfs mount point
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a/backends/bind/rootfses/30f7e5e2-55d0-4d4d-a662-f8aad0d56b33':
> Device or resource busy
> E0921 17:35:57.268349 47010 provisioner.cpp:403] Failed to remove the
> provisioned container directory at
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a':
> Device or resource busy
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[
https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901124#comment-14901124
]
Jie Yu commented on MESOS-3483:
---
Fixed.
> LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
>
>
> Key: MESOS-3483
> URL: https://issues.apache.org/jira/browse/MESOS-3483
> Project: Mesos
> Issue Type: Bug
>Reporter: Jie Yu
>
> So that when a user task is forked, it does not hold extra references to the
> sandbox mount and provisioner bind backend mounts. If we don't do that, we
> could get the following error message when cleaning up bind backend mount
> points and sandbox mount points.
> {noformat}
> E0921 17:35:57.268159 47010 bind.cpp:182] Failed to remove rootfs mount point
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a/backends/bind/rootfses/30f7e5e2-55d0-4d4d-a662-f8aad0d56b33':
> Device or resource busy
> E0921 17:35:57.268349 47010 provisioner.cpp:403] Failed to remove the
> provisioned container directory at
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a':
> Device or resource busy
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[
https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-3483:
--
Description:
So that when a user task is forked, it does not hold extra references to the
sandbox mount and provisioner bind backend mounts. If we don't do that, we
could get the following error message when cleaning up bind backend mount
points and sandbox mount points.
{noformat}
E0921 17:35:57.268159 47010 bind.cpp:182] Failed to remove rootfs mount point
'/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a/backends/bind/rootfses/30f7e5e2-55d0-4d4d-a662-f8aad0d56b33':
Device or resource busy
E0921 17:35:57.268349 47010 provisioner.cpp:403] Failed to remove the
provisioned container directory at
'/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a':
Device or resource busy
{noformat}
was:So that when a user task is forked, it does not hold extra references to
the sandbox mount and provisioner bind backend mounts. If we don't do that, we
could get the following error message when cleaning up bind backend mount
points and sandbox mount points.
> LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
>
>
> Key: MESOS-3483
> URL: https://issues.apache.org/jira/browse/MESOS-3483
> Project: Mesos
> Issue Type: Bug
>Reporter: Jie Yu
>
> So that when a user task is forked, it does not hold extra references to the
> sandbox mount and provisioner bind backend mounts. If we don't do that, we
> could get the following error message when cleaning up bind backend mount
> points and sandbox mount points.
> {noformat}
> E0921 17:35:57.268159 47010 bind.cpp:182] Failed to remove rootfs mount point
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a/backends/bind/rootfses/30f7e5e2-55d0-4d4d-a662-f8aad0d56b33':
> Device or resource busy
> E0921 17:35:57.268349 47010 provisioner.cpp:403] Failed to remove the
> provisioned container directory at
> '/var/lib/mesos/provisioner/containers/07eb6660-25ff-4e83-8b2f-06955567e04a':
> Device or resource busy
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[ https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901122#comment-14901122 ] haosdent commented on MESOS-3483: - Seems the description is not complete? > LinuxFilesystemIsolator should make the slave's work_dir a shared mount. > > > Key: MESOS-3483 > URL: https://issues.apache.org/jira/browse/MESOS-3483 > Project: Mesos > Issue Type: Bug >Reporter: Jie Yu > > So that when a user task is forked, it does not hold extra references to the > sandbox mount and provisioner bind backend mounts. If we don't do that, we > could get the following error message when cleaning up bind backend mount > points and sandbox mount points. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
[ https://issues.apache.org/jira/browse/MESOS-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901112#comment-14901112 ] Yan Xu commented on MESOS-3483: --- It would probably make sense to draw a propagation (vfsmount peer group) graph in linux.cpp for posterity as it's becoming harder to grasp for people who didn't work on this. > LinuxFilesystemIsolator should make the slave's work_dir a shared mount. > > > Key: MESOS-3483 > URL: https://issues.apache.org/jira/browse/MESOS-3483 > Project: Mesos > Issue Type: Bug >Reporter: Jie Yu > > So that when a user task is forked, it does not hold extra references to the > sandbox mount and provisioner bind backend mounts. If we don't do that, we > could get the following error message when cleaning up bind backend mount > points and sandbox mount points. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3483) LinuxFilesystemIsolator should make the slave's work_dir a shared mount.
Jie Yu created MESOS-3483: - Summary: LinuxFilesystemIsolator should make the slave's work_dir a shared mount. Key: MESOS-3483 URL: https://issues.apache.org/jira/browse/MESOS-3483 Project: Mesos Issue Type: Bug Reporter: Jie Yu So that when a user task is forked, it does not hold extra references to the sandbox mount and provisioner bind backend mounts. If we don't do that, we could get the following error message when cleaning up bind backend mount points and sandbox mount points. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3481) Add const accessor to Master flags
[ https://issues.apache.org/jira/browse/MESOS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu updated MESOS-3481: - Assignee: (was: Joseph Wu) > Add const accessor to Master flags > -- > > Key: MESOS-3481 > URL: https://issues.apache.org/jira/browse/MESOS-3481 > Project: Mesos > Issue Type: Task >Reporter: Joseph Wu >Priority: Trivial > Labels: mesosphere, newbie > > It would make sense to have an accessor to the master's flags, especially for > tests. > For example, see [this > test|https://github.com/apache/mesos/blob/2876b8c918814347dd56f6f87d461e414a90650a/src/tests/master_maintenance_tests.cpp#L1231-L1235]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2845) Command tasks lead to a mixing of revocable / non-revocable cpus and memory within the container.
[
https://issues.apache.org/jira/browse/MESOS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901034#comment-14901034
]
Ian Downes commented on MESOS-2845:
---
How is the proposed {{CommandLineExecutor}} different to the current
{{CommandExecutor}}?
> Command tasks lead to a mixing of revocable / non-revocable cpus and memory
> within the container.
> -
>
> Key: MESOS-2845
> URL: https://issues.apache.org/jira/browse/MESOS-2845
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Benjamin Mahler
>Assignee: Klaus Ma
> Labels: twitter
>
> Due to the hack
> [here|https://github.com/apache/mesos/blob/9a5788801e7fc95fce99749a23803fc52c67c0ce/src/slave/slave.cpp#L3101],
> where we add a small set of resources into the command executor:
> {code}
> ExecutorInfo Slave::getExecutorInfo(
> const FrameworkID& frameworkId,
> const TaskInfo& task)
> {
> if (task.has_command()) {
> ...
> // XXX: These are always non-revocable.
> // Add an allowance for the command executor. This does lead to a
> // small overcommit of resources.
> executor.mutable_resources()->MergeFrom(
> Resources::parse(
> "cpus:" + stringify(DEFAULT_EXECUTOR_CPUS) + ";" +
> "mem:" + stringify(DEFAULT_EXECUTOR_MEM.megabytes())).get());
> }
> ...
> }
> {code}
> The obvious extension here would be to make these revocable, but would be
> great to remove this hack entirely.
> Seems to originate in [r/22251|https://reviews.apache.org/r/22251/] from
> MESOS-1417.
> FYI [~idownes] [~jieyu]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3482) Compile fails with -Duser.home option set.
[
https://issues.apache.org/jira/browse/MESOS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900981#comment-14900981
]
haosdent commented on MESOS-3482:
-
According this link,
http://stackoverflow.com/questions/11683715/suppressing-the-picked-up-java-options-message
and
http://cr.openjdk.java.net/~gbenson/zero-11-hotspot/hotspot/src/share/vm/runtime/arguments.cpp.html
Seems when current user is not root and set up _JAVA_OPTIONS, would print this
error.
{code}
2489 if (os::getenv(name, buffer, sizeof(buffer)) &&
2490 !os::have_special_privileges()) {
2491 JavaVMOption options[N_MAX_OPTIONS]; // Construct option array
2492 jio_fprintf(defaultStream::error_stream(),
2493 "Picked up %s: %s\n", name, buffer);
{code}
> Compile fails with -Duser.home option set.
> --
>
> Key: MESOS-3482
> URL: https://issues.apache.org/jira/browse/MESOS-3482
> Project: Mesos
> Issue Type: Bug
> Components: build
>Affects Versions: 0.24.0
> Environment: OS X 10.11, MacBook Pro Mid-2012, Clang-700.0.72
>Reporter: Dominyk Tiller
> Labels: build
>
> Apologies in advance; I'm not sure if this is technically your bug or a bug
> with the upstream javadoc plugin.
> I'm trying to sandbox the Mesos installation so the downloaded
> plugins/jars/etc needed by Maven for installation aren't retained after the
> build, as otherwise they get dumped in "$HOME/.m2". To achieve this I've
> exported:
> {noformat}
> _JAVA_OPTIONS=-Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
> {noformat}
> This causes the following build failure:
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 02:48 min
> [INFO] Finished at: 2015-09-21T15:24:14+01:00
> [INFO] Final Memory: 29M/242M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:jar
> (build-and-attach-javadocs) on project mesos: MavenReportException: Error
> while creating archive:
> [ERROR] Exit code: 1 - Picked up _JAVA_OPTIONS:
> -Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
> [ERROR] javadoc: error - No packages or classes specified.
> [ERROR]
> [ERROR] Command line was:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/javadoc
> @options
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/src/java/target/apidocs'
> dir.
> {noformat}
> Can confirm without setting that variable, the build is fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3422) MasterSlaveReconciliationTest.ReconcileLostTask test is flaky
[
https://issues.apache.org/jira/browse/MESOS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900956#comment-14900956
]
Paul Brett commented on MESOS-3422:
---
Tested HEAD on Centos6 (original reporting platform) with no errors.
{code}
[--] 1 test from MasterSlaveReconciliationTest
[ RUN ] MasterSlaveReconciliationTest.ReconcileLostTask
Using temporary directory
'/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI'
I0921 16:38:36.016902 51925 leveldb.cpp:176] Opened db in 73.30966ms
I0921 16:38:36.023943 51925 leveldb.cpp:183] Compacted db in 6.963667ms
I0921 16:38:36.024034 51925 leveldb.cpp:198] Created db iterator in 48856ns
I0921 16:38:36.024061 51925 leveldb.cpp:204] Seeked to beginning of db in 3684ns
I0921 16:38:36.024077 51925 leveldb.cpp:273] Iterated through 0 keys in the db
in 337ns
I0921 16:38:36.024189 51925 replica.cpp:744] Replica recovered with log
positions 0 -> 0 with 1 holes and 0 unlearned
I0921 16:38:36.025542 51935 recover.cpp:449] Starting replica recovery
I0921 16:38:36.026080 51935 recover.cpp:475] Replica is in EMPTY status
I0921 16:38:36.028053 51930 master.cpp:380] Master
20150921-163836-2081170186-40941-51925 (smfd-aki-27-sr1.devel.twitter.com)
started on 10.35.12.124:40941
I0921 16:38:36.028286 51934 replica.cpp:641] Replica in EMPTY status received a
broadcasted recover request
I0921 16:38:36.028094 51930 master.cpp:382] Flags at startup: --acls=""
--allocation_interval="1secs" --allocator="HierarchicalDRF"
--authenticate="true" --authenticate_slaves="true" --authenticators="crammd5"
--authorizers="local"
--credentials="/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/credentials"
--framework_sorter="drf" --help="false" --initialize_driver_logging="true"
--log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
--max_slave_ping_timeouts="5" --quiet="false"
--recovery_slave_removal_limit="100%" --registry="replicated_log"
--registry_fetch_timeout="1mins" --registry_store_timeout="25secs"
--registry_strict="true" --root_submissions="true"
--slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
--user_sorter="drf" --version="false"
--webui_dir="/usr/local/share/mesos/webui"
--work_dir="/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/master"
--zk_session_timeout="10secs"
I0921 16:38:36.029104 51930 master.cpp:427] Master only allowing authenticated
frameworks to register
I0921 16:38:36.029132 51930 master.cpp:432] Master only allowing authenticated
slaves to register
I0921 16:38:36.029155 51930 credentials.hpp:37] Loading credentials for
authentication from
'/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/credentials'
I0921 16:38:36.029250 51936 recover.cpp:195] Received a recover response from a
replica in EMPTY status
I0921 16:38:36.029738 51930 master.cpp:471] Using default 'crammd5'
authenticator
I0921 16:38:36.029908 51930 authenticator.cpp:512] Initializing server SASL
I0921 16:38:36.029947 51940 recover.cpp:566] Updating replica status to STARTING
I0921 16:38:36.030782 51930 master.cpp:508] Authorization enabled
I0921 16:38:36.036074 51926 master.cpp:1607] The newly elected leader is
master@10.35.12.124:40941 with id 20150921-163836-2081170186-40941-51925
I0921 16:38:36.036110 51926 master.cpp:1620] Elected as the leading master!
I0921 16:38:36.036145 51926 master.cpp:1380] Recovering from registrar
I0921 16:38:36.036335 51930 registrar.cpp:309] Recovering registrar
I0921 16:38:36.067191 51938 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 36.988836ms
I0921 16:38:36.067246 51938 replica.cpp:323] Persisted replica status to
STARTING
I0921 16:38:36.067517 51938 recover.cpp:475] Replica is in STARTING status
I0921 16:38:36.068230 51936 replica.cpp:641] Replica in STARTING status
received a broadcasted recover request
I0921 16:38:36.068429 51928 recover.cpp:195] Received a recover response from a
replica in STARTING status
I0921 16:38:36.068729 51927 recover.cpp:566] Updating replica status to VOTING
I0921 16:38:36.074915 51940 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 6.095154ms
I0921 16:38:36.074942 51940 replica.cpp:323] Persisted replica status to VOTING
I0921 16:38:36.075021 51936 recover.cpp:580] Successfully joined the Paxos group
I0921 16:38:36.075228 51936 recover.cpp:464] Recover process terminated
I0921 16:38:36.075657 51926 log.cpp:661] Attempting to start the writer
I0921 16:38:36.077828 51927 replica.cpp:477] Replica received implicit promise
request with proposal 1
I0921 16:38:36.091645 51927 leveld
[jira] [Commented] (MESOS-3422) MasterSlaveReconciliationTest.ReconcileLostTask test is flaky
[
https://issues.apache.org/jira/browse/MESOS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900955#comment-14900955
]
Paul Brett commented on MESOS-3422:
---
Tested HEAD on Centos6 (original reporting platform) with no errors.
{code}
[--] 1 test from MasterSlaveReconciliationTest
[ RUN ] MasterSlaveReconciliationTest.ReconcileLostTask
Using temporary directory
'/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI'
I0921 16:38:36.016902 51925 leveldb.cpp:176] Opened db in 73.30966ms
I0921 16:38:36.023943 51925 leveldb.cpp:183] Compacted db in 6.963667ms
I0921 16:38:36.024034 51925 leveldb.cpp:198] Created db iterator in 48856ns
I0921 16:38:36.024061 51925 leveldb.cpp:204] Seeked to beginning of db in 3684ns
I0921 16:38:36.024077 51925 leveldb.cpp:273] Iterated through 0 keys in the db
in 337ns
I0921 16:38:36.024189 51925 replica.cpp:744] Replica recovered with log
positions 0 -> 0 with 1 holes and 0 unlearned
I0921 16:38:36.025542 51935 recover.cpp:449] Starting replica recovery
I0921 16:38:36.026080 51935 recover.cpp:475] Replica is in EMPTY status
I0921 16:38:36.028053 51930 master.cpp:380] Master
20150921-163836-2081170186-40941-51925 (smfd-aki-27-sr1.devel.twitter.com)
started on 10.35.12.124:40941
I0921 16:38:36.028286 51934 replica.cpp:641] Replica in EMPTY status received a
broadcasted recover request
I0921 16:38:36.028094 51930 master.cpp:382] Flags at startup: --acls=""
--allocation_interval="1secs" --allocator="HierarchicalDRF"
--authenticate="true" --authenticate_slaves="true" --authenticators="crammd5"
--authorizers="local"
--credentials="/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/credentials"
--framework_sorter="drf" --help="false" --initialize_driver_logging="true"
--log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
--max_slave_ping_timeouts="5" --quiet="false"
--recovery_slave_removal_limit="100%" --registry="replicated_log"
--registry_fetch_timeout="1mins" --registry_store_timeout="25secs"
--registry_strict="true" --root_submissions="true"
--slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
--user_sorter="drf" --version="false"
--webui_dir="/usr/local/share/mesos/webui"
--work_dir="/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/master"
--zk_session_timeout="10secs"
I0921 16:38:36.029104 51930 master.cpp:427] Master only allowing authenticated
frameworks to register
I0921 16:38:36.029132 51930 master.cpp:432] Master only allowing authenticated
slaves to register
I0921 16:38:36.029155 51930 credentials.hpp:37] Loading credentials for
authentication from
'/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/credentials'
I0921 16:38:36.029250 51936 recover.cpp:195] Received a recover response from a
replica in EMPTY status
I0921 16:38:36.029738 51930 master.cpp:471] Using default 'crammd5'
authenticator
I0921 16:38:36.029908 51930 authenticator.cpp:512] Initializing server SASL
I0921 16:38:36.029947 51940 recover.cpp:566] Updating replica status to STARTING
I0921 16:38:36.030782 51930 master.cpp:508] Authorization enabled
I0921 16:38:36.036074 51926 master.cpp:1607] The newly elected leader is
master@10.35.12.124:40941 with id 20150921-163836-2081170186-40941-51925
I0921 16:38:36.036110 51926 master.cpp:1620] Elected as the leading master!
I0921 16:38:36.036145 51926 master.cpp:1380] Recovering from registrar
I0921 16:38:36.036335 51930 registrar.cpp:309] Recovering registrar
I0921 16:38:36.067191 51938 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 36.988836ms
I0921 16:38:36.067246 51938 replica.cpp:323] Persisted replica status to
STARTING
I0921 16:38:36.067517 51938 recover.cpp:475] Replica is in STARTING status
I0921 16:38:36.068230 51936 replica.cpp:641] Replica in STARTING status
received a broadcasted recover request
I0921 16:38:36.068429 51928 recover.cpp:195] Received a recover response from a
replica in STARTING status
I0921 16:38:36.068729 51927 recover.cpp:566] Updating replica status to VOTING
I0921 16:38:36.074915 51940 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 6.095154ms
I0921 16:38:36.074942 51940 replica.cpp:323] Persisted replica status to VOTING
I0921 16:38:36.075021 51936 recover.cpp:580] Successfully joined the Paxos group
I0921 16:38:36.075228 51936 recover.cpp:464] Recover process terminated
I0921 16:38:36.075657 51926 log.cpp:661] Attempting to start the writer
I0921 16:38:36.077828 51927 replica.cpp:477] Replica received implicit promise
request with proposal 1
I0921 16:38:36.091645 51927 leveld
[jira] [Commented] (MESOS-3422) MasterSlaveReconciliationTest.ReconcileLostTask test is flaky
[
https://issues.apache.org/jira/browse/MESOS-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900954#comment-14900954
]
Paul Brett commented on MESOS-3422:
---
Tested HEAD on Centos6 (original reporting platform) with no errors.
{code}
[--] 1 test from MasterSlaveReconciliationTest
[ RUN ] MasterSlaveReconciliationTest.ReconcileLostTask
Using temporary directory
'/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI'
I0921 16:38:36.016902 51925 leveldb.cpp:176] Opened db in 73.30966ms
I0921 16:38:36.023943 51925 leveldb.cpp:183] Compacted db in 6.963667ms
I0921 16:38:36.024034 51925 leveldb.cpp:198] Created db iterator in 48856ns
I0921 16:38:36.024061 51925 leveldb.cpp:204] Seeked to beginning of db in 3684ns
I0921 16:38:36.024077 51925 leveldb.cpp:273] Iterated through 0 keys in the db
in 337ns
I0921 16:38:36.024189 51925 replica.cpp:744] Replica recovered with log
positions 0 -> 0 with 1 holes and 0 unlearned
I0921 16:38:36.025542 51935 recover.cpp:449] Starting replica recovery
I0921 16:38:36.026080 51935 recover.cpp:475] Replica is in EMPTY status
I0921 16:38:36.028053 51930 master.cpp:380] Master
20150921-163836-2081170186-40941-51925 (smfd-aki-27-sr1.devel.twitter.com)
started on 10.35.12.124:40941
I0921 16:38:36.028286 51934 replica.cpp:641] Replica in EMPTY status received a
broadcasted recover request
I0921 16:38:36.028094 51930 master.cpp:382] Flags at startup: --acls=""
--allocation_interval="1secs" --allocator="HierarchicalDRF"
--authenticate="true" --authenticate_slaves="true" --authenticators="crammd5"
--authorizers="local"
--credentials="/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/credentials"
--framework_sorter="drf" --help="false" --initialize_driver_logging="true"
--log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
--max_slave_ping_timeouts="5" --quiet="false"
--recovery_slave_removal_limit="100%" --registry="replicated_log"
--registry_fetch_timeout="1mins" --registry_store_timeout="25secs"
--registry_strict="true" --root_submissions="true"
--slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
--user_sorter="drf" --version="false"
--webui_dir="/usr/local/share/mesos/webui"
--work_dir="/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/master"
--zk_session_timeout="10secs"
I0921 16:38:36.029104 51930 master.cpp:427] Master only allowing authenticated
frameworks to register
I0921 16:38:36.029132 51930 master.cpp:432] Master only allowing authenticated
slaves to register
I0921 16:38:36.029155 51930 credentials.hpp:37] Loading credentials for
authentication from
'/tmp/MasterSlaveReconciliationTest_ReconcileLostTask_i61HPI/credentials'
I0921 16:38:36.029250 51936 recover.cpp:195] Received a recover response from a
replica in EMPTY status
I0921 16:38:36.029738 51930 master.cpp:471] Using default 'crammd5'
authenticator
I0921 16:38:36.029908 51930 authenticator.cpp:512] Initializing server SASL
I0921 16:38:36.029947 51940 recover.cpp:566] Updating replica status to STARTING
I0921 16:38:36.030782 51930 master.cpp:508] Authorization enabled
I0921 16:38:36.036074 51926 master.cpp:1607] The newly elected leader is
master@10.35.12.124:40941 with id 20150921-163836-2081170186-40941-51925
I0921 16:38:36.036110 51926 master.cpp:1620] Elected as the leading master!
I0921 16:38:36.036145 51926 master.cpp:1380] Recovering from registrar
I0921 16:38:36.036335 51930 registrar.cpp:309] Recovering registrar
I0921 16:38:36.067191 51938 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 36.988836ms
I0921 16:38:36.067246 51938 replica.cpp:323] Persisted replica status to
STARTING
I0921 16:38:36.067517 51938 recover.cpp:475] Replica is in STARTING status
I0921 16:38:36.068230 51936 replica.cpp:641] Replica in STARTING status
received a broadcasted recover request
I0921 16:38:36.068429 51928 recover.cpp:195] Received a recover response from a
replica in STARTING status
I0921 16:38:36.068729 51927 recover.cpp:566] Updating replica status to VOTING
I0921 16:38:36.074915 51940 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 6.095154ms
I0921 16:38:36.074942 51940 replica.cpp:323] Persisted replica status to VOTING
I0921 16:38:36.075021 51936 recover.cpp:580] Successfully joined the Paxos group
I0921 16:38:36.075228 51936 recover.cpp:464] Recover process terminated
I0921 16:38:36.075657 51926 log.cpp:661] Attempting to start the writer
I0921 16:38:36.077828 51927 replica.cpp:477] Replica received implicit promise
request with proposal 1
I0921 16:38:36.091645 51927 leveld
[jira] [Created] (MESOS-3482) Compile fails with -Duser.home option set.
Dominyk Tiller created MESOS-3482:
-
Summary: Compile fails with -Duser.home option set.
Key: MESOS-3482
URL: https://issues.apache.org/jira/browse/MESOS-3482
Project: Mesos
Issue Type: Bug
Components: build
Affects Versions: 0.24.0
Environment: OS X 10.11, MacBook Pro Mid-2012, Clang-700.0.72
Reporter: Dominyk Tiller
Apologies in advance; I'm not sure if this is technically your bug or a bug
with the upstream javadoc plugin.
I'm trying to sandbox the Mesos installation so the downloaded plugins/jars/etc
needed by Maven for installation aren't retained after the build, as otherwise
they get dumped in "$HOME/.m2". To achieve this I've exported:
{noformat}
_JAVA_OPTIONS=-Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
{noformat}
This causes the following build failure:
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 02:48 min
[INFO] Finished at: 2015-09-21T15:24:14+01:00
[INFO] Final Memory: 29M/242M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.8.1:jar
(build-and-attach-javadocs) on project mesos: MavenReportException: Error while
creating archive:
[ERROR] Exit code: 1 - Picked up _JAVA_OPTIONS:
-Duser.home=/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/.brew_home
[ERROR] javadoc: error - No packages or classes specified.
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/javadoc
@options
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/private/tmp/mesos20150921-21602-19h9jrr/mesos-0.24.0/src/java/target/apidocs'
dir.
{noformat}
Can confirm without setting that variable, the build is fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3280) Master fails to access replicated log after network partition
[ https://issues.apache.org/jira/browse/MESOS-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900930#comment-14900930 ] Neil Conway commented on MESOS-3280: I've been looking into this. Current status: * There definitely seems to be a bug in the auto-initialization logic of the replicated log implementation. I'm working to get a deterministic test case and a proposed fix. * The auto-init bug actually doesn't have anything to do with network partitions: you can reproduce it by just starting three Mesos masters at the same time, although it depends on hitting a schedule of network messages. This is the cause of "Master fails to fetch the replicated log even before the network partition" issues noted above and in the Chronos ticket. * As far as I can tell, Mesos behaves does not behave incorrectly during/after a network partition. Some of the "Recovery failed: Failed to recover registrar" errors that occur _after_ the partition has been healed seem to arise because the Jepsen scripts don't promptly restart a master that exits when it loses leadership. * There is definitely some room for improvement in how we handle losing leadership: for example, because it is expected behavior, we shouldn't print a stack trace. It also seems like if the current leader is in the majority partition after a network partition, it still views this as a "leadership change" event and exits, even though that should be avoidable. TBD whether that behavior should be improved. > Master fails to access replicated log after network partition > - > > Key: MESOS-3280 > URL: https://issues.apache.org/jira/browse/MESOS-3280 > Project: Mesos > Issue Type: Bug > Components: master, replicated log >Affects Versions: 0.23.0 > Environment: Zookeeper version 3.4.5--1 >Reporter: Bernd Mathiske >Assignee: Neil Conway > Labels: mesosphere > > In a 5 node cluster with 3 masters and 2 slaves, and ZK on each node, when a > network partition is forced, all the masters apparently lose access to their > replicated log. The leading master halts. Unknown reasons, but presumably > related to replicated log access. The others fail to recover from the > replicated log. Unknown reasons. This could have to do with ZK setup, but it > might also be a Mesos bug. > This was observed in a Chronos test drive scenario described in detail here: > https://github.com/mesos/chronos/issues/511 > With setup instructions here: > https://github.com/mesos/chronos/issues/508 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3481) Add const accessor to Master flags
Joseph Wu created MESOS-3481: Summary: Add const accessor to Master flags Key: MESOS-3481 URL: https://issues.apache.org/jira/browse/MESOS-3481 Project: Mesos Issue Type: Task Reporter: Joseph Wu Assignee: Joseph Wu Priority: Trivial It would make sense to have an accessor to the master's flags, especially for tests. For example, see [this test|https://github.com/apache/mesos/blob/2876b8c918814347dd56f6f87d461e414a90650a/src/tests/master_maintenance_tests.cpp#L1231-L1235]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3476) Refactor Status Update method on Slave to handle HTTP based Executors
[
https://issues.apache.org/jira/browse/MESOS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-3476:
--
Issue Type: Task (was: Bug)
> Refactor Status Update method on Slave to handle HTTP based Executors
> -
>
> Key: MESOS-3476
> URL: https://issues.apache.org/jira/browse/MESOS-3476
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
>
> Currently, receiving a status update sent from slave to itself , {{runTask}}
> , {{killTask}} and status updates from executors are handled by the
> {{Slave::statusUpdate}} method on Slave. The signature of the method is
> {{void Slave::statusUpdate(StatusUpdate update, const UPID& pid)}}.
> We need to create another overload of it that can also handle HTTP based
> executors which the previous PID based function can also call into. The
> signature of the new function could be:
> {{void Slave::statusUpdate(StatusUpdate update, Executor* executor)}}
> The HTTP Executor would also call into this new function via
> {{src/slave/http.cpp}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-3480) Refactor Executor struct in Slave to handle HTTP based executors
Anand Mazumdar created MESOS-3480:
-
Summary: Refactor Executor struct in Slave to handle HTTP based
executors
Key: MESOS-3480
URL: https://issues.apache.org/jira/browse/MESOS-3480
Project: Mesos
Issue Type: Task
Reporter: Anand Mazumdar
Assignee: Anand Mazumdar
Fix For: 0.26.0
Currently, the {{struct Executor}} in slave only supports executors connected
via message passing (driver). We should refactor it to add support for HTTP
based Executors similar to what was done for the Scheduler API {{struct
Framework}} in {{src/master/master.hpp}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900650#comment-14900650
]
chenqiang commented on MESOS-3079:
--
I re-depolyed in CentOS 6.4, mesos-0.21.0, g++ 4.4.7.
Everything is OK, but also got the same issue that can not access via
http::5050 what's wrong??
I run the mesos in following steps:
1. login with putty, go to the mesos build dir, run:
$ ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
2. open another putty, run:
./bin/mesos-slave.sh --master=127.0.0.1:5050
3. # Visit the mesos web page.
$ http://127.0.0.1:5050 (failed to access..., my god, what's wrong...)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContain
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900602#comment-14900602
]
chenqiang commented on MESOS-3079:
--
yes, got the right response, typo error maste->master.
curl http://127.0.0.1:5050/master/state.json
[root@chenqiang-master-dev001-shgq ~]# curl
http://127.0.0.1:5050/master/state.j son
{"activated_slaves":1,"build_date":"2015-09-21
11:53:53","build_time":1442807633
,"build_user":"root","completed_frameworks":[],"deactivated_slaves":0,"elected_t
ime":1442824269.81597,"flags":{"allocation_interval":"1secs","allocator":"Hierar
chicalDRF","authenticate":"false","authenticate_slaves":"false","authenticators"
:"crammd5","framework_sorter":"drf","help":"false","initialize_driver_logging":"
true","ip":"127.0.0.1","log_auto_initialize":"true","logbufsecs":"0","logging_le
vel":"INFO","max_slave_ping_timeouts":"5","port":"5050","quiet":"false","recover
y_slave_removal_limit":"100%","registry":"replicated_log","registry_fetch_timeou
t":"1mins","registry_store_timeout":"5secs","registry_strict":"false","root_subm
issions":"true","slave_ping_timeout":"15secs","slave_reregister_timeout":"10mins
","user_sorter":"drf","version":"false","webui_dir":"\/home\/chenqiang\/download
s\/mesos-0.23.0\/build\/..\/src\/webui","work_dir":"\/var\/lib\/mesos","zk_sessi
on_timeout":"10secs"},"frameworks":[],"hostname":"localhost","id":"20150921-1631
09-16777343-5050-4289","leader":"master@127.0.0.1:5050","orphan_tasks":[],"pid":
"master@127.0.0.1:5050","slaves":[{"active":true,"attributes":{},"hostname":"che
nqiang-master-dev001-shgq.qiyi.virtual","id":"20150921-130346-16777343-5050-2307
4-S0","offered_resources":{"cpus":0,"disk":0,"mem":0},"pid":"slave(1)@10.221.75.
130:5051","registered_time":1442824286.47122,"reregistered_time":1442824286.4722
9,"reserved_resources":{},"resources":{"cpus":4,"disk":31036,"mem":6845,"ports":
"[31000-32000]"},"unreserved_resources":{"cpus":4,"disk":31036,"mem":6845,"ports
":"[31000-32000]"},"used_resources":{"cpus":0,"disk":0,"mem":0}}],"start_time":1
442824269.80855,"unregistered_frameworks":[],"version":"0.23.0"}[root@chenqiang-
[root@chenqiang-master-dev001-shgq ~]#
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900595#comment-14900595
]
chenqiang commented on MESOS-3079:
--
It returned with nothing...
What' state json playload should be got? thanks.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTes
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900591#comment-14900591
]
haosdent commented on MESOS-3079:
-
You aslo could curl http://127.0.0.1:5050/maste/state.json successfully?
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Par
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900572#comment-14900572
]
chenqiang commented on MESOS-3079:
--
selinux also closed.
[root@chenqiang-master-dev001-shgq yum.repos.d]# setenforce 0
[root@chenqiang-master-dev001-shgq yum.repos.d]# getenforce
Permissive
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900566#comment-14900566
]
chenqiang commented on MESOS-3079:
--
[root@chenqiang-master-dev001-shgq ~]# curl http://127.0.0.1:5050/help -i
HTTP/1.1 200 OK
Date: Mon, 21 Sep 2015 12:14:15 GMT
Content-Type: text/x-markdown
Content-Length: 409
## HELP
> [/__processes__][__processes__]
> [/files][files]
> [/logging][logging]
> [/master][master]
> [/metrics][metrics]
> [/profiler][profiler]
> [/registrar(1)][registrar(1)]
> [/system][system]
[__processes__]: help/__processes__
[files]: help/files
[logging]: help/logging
[master]: help/master
[metrics]: help/metrics
[profiler]: help/profiler
[registrar(1)]: help/registrar(1)
[system]: help/system
[root@chenqiang-master-dev001-shgq ~]# netstat -tlanp | grep 5050
tcp0 0 127.0.0.1:5050 0.0.0.0:*
LISTEN 4289/lt-mesos-maste
tcp0 0 127.0.0.1:5050 127.0.0.1:40460
ESTABLISHED 4289/lt-mesos-maste
tcp0 0 127.0.0.1:40460 127.0.0.1:5050
ESTABLISHED 4315/lt-mesos-slave
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.G
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900563#comment-14900563
]
haosdent commented on MESOS-3079:
-
Could you "curl http://127.0.0.1:5050/help"; success? And also use netstat to
make sure mesos-master is listened on 5050.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosCo
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900517#comment-14900517
]
chenqiang commented on MESOS-3079:
--
no, can't too.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> mesos::internal::sla
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenqiang updated MESOS-3079:
-
Comment: was deleted
(was: no, can't too.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
>
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenqiang updated MESOS-3079:
-
Comment: was deleted
(was: no, can't too.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
>
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900518#comment-14900518
]
chenqiang commented on MESOS-3079:
--
no, can't too.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> mesos::internal::sla
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900516#comment-14900516
]
chenqiang commented on MESOS-3079:
--
no, can't too.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> mesos::internal::sla
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900494#comment-14900494
]
haosdent commented on MESOS-3079:
-
You could open http://:5050 successfully in other machine?
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave,
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900489#comment-14900489
]
chenqiang commented on MESOS-3079:
--
It's there some good idea to fix the my connection issue? thanks.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Partitio
[jira] [Issue Comment Deleted] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenqiang updated MESOS-3079:
-
Comment: was deleted
(was: BTW, I logged in my windows side from the master IP, with
http://:5050, I'm sure it can't be the cause for this issue, thanks.)
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ F
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900445#comment-14900445
]
chenqiang commented on MESOS-3079:
--
BTW, I logged in my windows side from the master IP, with
http://:5050, I'm sure it can't be the cause for this issue, thanks.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900446#comment-14900446
]
chenqiang commented on MESOS-3079:
--
BTW, I logged in my windows side from the master IP, with
http://:5050, I'm sure it can't be the cause for this issue, thanks.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900443#comment-14900443
]
chenqiang commented on MESOS-3079:
--
OK, it means those are not the root cause that made me can't access to
http:127.0.0.1:5050
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] Sl
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900440#comment-14900440
]
chenqiang commented on MESOS-3079:
--
[root@chenqiang-master-dev001-shgq ~]# telnet 127.0.0.1 5050
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::sla
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900436#comment-14900436
]
haosdent commented on MESOS-3079:
-
You could ignore this failed tests.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam =
> m
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900435#comment-14900435
]
haosdent commented on MESOS-3079:
-
Could you telnet to 127.0.0.1 5050 in mesos master machine?
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.PartitionedSlav
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[ https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900417#comment-14900417 ] chenqiang commented on MESOS-3079: -- my fails listed below, thanks. [==] 713 tests from 117 test cases ran. (301085 ms total) [ PASSED ] 676 tests. [ FAILED ] 37 tests, listed below: [ FAILED ] PerfTest.ROOT_SamplePid [ FAILED ] CgroupsNoHierarchyTest.ROOT_CGROUPS_NOHIERARCHY_MountUnmountHierarchy [ FAILED ] CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf [ FAILED ] CgroupsAnyHierarchyMemoryPressureTest.ROOT_IncreaseUnlockedRSS [ FAILED ] CgroupsAnyHierarchyMemoryPressureTest.ROOT_IncreasePageCache [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.PartitionedSlave, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.MasterFailover, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.MultipleFrameworks, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.MultipleSlaves, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] SlaveRecoveryTest/0.RestartBeforeContainerizerLaunch, where TypeParam = mesos::internal::slave::MesosContainerizer [ FAILED ] MesosContainerizerSlaveRecoveryTest.ResourceStatistics [ FAILED ] MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward [ FAILED ] MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceForward [ FAILED ] MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceBackward [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample [ FAILED ] UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup, where TypeParam = mesos::internal::slave::CgroupsMemIsolatorProcess [ FAILED ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup, where TypeParam = mesos::internal::slave::CgroupsCpushareIsolatorProcess [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess 37 FAILED TESTS YOU HAVE 12 DISABLED TESTS I0921 14:01:07.216980 29337 exec.cpp:452] Slave exited, but framework has checkpointing enabled. Waiting 15mins to reconnect with slave 20150921-135826-2186009866-44268-27222-S0 make[3]: *** [check-local] Error 1 make[3]: Leaving directory `/home/chenqiang/downloads/mesos-0.23.0/build/src' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/chenqiang/downloads/mesos-0.23.0/build/src' make[1]: *** [check] Error 2 make[1]: Leaving directory `/home/chenqiang/downloads/mesos-0.23.0/build/src' make: *** [check-recursive] Error 1 > `sudo make distcheck` fails on Ubuntu 14.04 (and p
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900397#comment-14900397
]
chenqiang commented on MESOS-3079:
--
Hi haosdent,
Thanks for your quick response.
I use the centos 6.4 x86_64, mesos0.23.0, g++ 4.8.1
I checked that the 5050 port is in listen and establish status.
-
In mesos-master side, I saw following msg:
I0921 16:31:26.478057 4309 hierarchical.hpp:588] Slave
20150921-130346-16777343-5050-23074-S0 (my-vm) updated with oversubscribed
resources (total: cpus(*):4; mem(*):6845; disk(*):31036;
ports(*):[31000-32000], allocated: )
and in mesos-slave side,
I0921 16:59:11.596024 4340 slave.cpp:4179] Querying resource estimator for
oversubscribable resources
I0921 16:59:11.596247 4340 slave.cpp:4193] Received oversubscribable resources
from the resource estimator
Thanks.
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.S
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900394#comment-14900394
]
haosdent commented on MESOS-3079:
-
Which version are you used? master branch or 0.24? And what is your operation
system?
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileShutdownFramework, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileTasksMissingFromSlave, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.SchedulerFailover, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveReco
[jira] [Commented] (MESOS-3079) `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
[
https://issues.apache.org/jira/browse/MESOS-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900337#comment-14900337
]
chenqiang commented on MESOS-3079:
--
Hi Marco Massenzio, I encountered those 37 fails also, and I run following
commands, I can't connect to the mesos web page via http://127.0.0.1:5050, so
does those failures made it cannot access or still have others? thanks.
# Start mesos master (Ensure work directory exists and has proper
permissions).
$ ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
# Start mesos slave.
$ ./bin/mesos-slave.sh --master=127.0.0.1:5050
# Visit the mesos web page.
$ http://127.0.0.1:5050
> `sudo make distcheck` fails on Ubuntu 14.04 (and possibly other OSes too)
> -
>
> Key: MESOS-3079
> URL: https://issues.apache.org/jira/browse/MESOS-3079
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Marco Massenzio
>Assignee: Marco Massenzio
>Priority: Blocker
> Labels: mesosphere, tests
> Fix For: 0.24.0
>
> Attachments: test-results.log
>
>
> Running tests as root causes a large number of failures.
> {noformat}
> $ lsb_release -a
> LSB Version:
> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
> Distributor ID: Ubuntu
> Description:Ubuntu 14.04.2 LTS
> Release:14.04
> Codename: trusty
> $ sudo make -j12 V=0 check
> [==] 712 tests from 116 test cases ran. (318672 ms total)
> [ PASSED ] 676 tests.
> [ FAILED ] 36 tests, listed below:
> [ FAILED ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> [ FAILED ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> [ FAILED ] SlaveRecoveryTest/0.RecoverSlaveState, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverStatusUpdateManager, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconnectExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverUnregisteredExecutor, where TypeParam
> = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverTerminatedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RecoverCompletedExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.CleanupExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RemoveNonCheckpointingFramework, where
> TypeParam = mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.NonCheckpointingFramework, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.KillTask, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.Reboot, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.GCExecutor, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.RegisterDisconnectedSlave, where TypeParam =
> mesos::internal::slave::MesosContainerizer
> [ FAILED ] SlaveRecoveryTest/0.ReconcileKillTask, where TypeParam =
> mesos::i
[jira] [Commented] (MESOS-3479) COMMAND Health Checks are not executed if the timeout is exceeded
[ https://issues.apache.org/jira/browse/MESOS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900319#comment-14900319 ] Matthias Veit commented on MESOS-3479: -- [~nfnt] Please refine with the details you found. Thanks. > COMMAND Health Checks are not executed if the timeout is exceeded > - > > Key: MESOS-3479 > URL: https://issues.apache.org/jira/browse/MESOS-3479 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.23.0 >Reporter: Matthias Veit >Priority: Critical > > The issue first appeared as Marathon Bug: See here for reference: > https://github.com/mesosphere/marathon/issues/2179. > A COMMAND health check is defined with a timeout of 20 seconds. > The command itself takes longer than 20 seconds to execute. > Current behavior: > - The mesos health check process get's killed, but the defined command > process not (in the example the curl command returns after 21 seconds). > - The check attempt is considered healthy, if the timeout is exceeded > - The health check stops and is not executed any longer > Expected behavior: > - The defined health check command is killed, when the timeout is exceeded > - The check attempt is considered Unhealthy, if the timeout is exceeded > - The health check does not stop -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3479) COMMAND Health Checks are not executed if the timeout is exceeded
Matthias Veit created MESOS-3479: Summary: COMMAND Health Checks are not executed if the timeout is exceeded Key: MESOS-3479 URL: https://issues.apache.org/jira/browse/MESOS-3479 Project: Mesos Issue Type: Bug Affects Versions: 0.23.0 Reporter: Matthias Veit Priority: Critical The issue first appeared as Marathon Bug: See here for reference: https://github.com/mesosphere/marathon/issues/2179. A COMMAND health check is defined with a timeout of 20 seconds. The command itself takes longer than 20 seconds to execute. Current behavior: - The mesos health check process get's killed, but the defined command process not (in the example the curl command returns after 21 seconds). - The check attempt is considered healthy, if the timeout is exceeded - The health check stops and is not executed any longer Expected behavior: - The defined health check command is killed, when the timeout is exceeded - The check attempt is considered Unhealthy, if the timeout is exceeded - The health check does not stop -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900287#comment-14900287 ] Yong Qiao Wang commented on MESOS-3177: --- Thanks [~thomasr], I think this requirement should be covered by Quota proposal. This ticket should only focus on the roles/weights add/remove/update. > Make Mesos own configuration of roles/weights > - > > Key: MESOS-3177 > URL: https://issues.apache.org/jira/browse/MESOS-3177 > Project: Mesos > Issue Type: Improvement > Components: master, slave >Reporter: Cody Maloney >Assignee: Yong Qiao Wang > Labels: mesosphere > > All roles and weights must currently be specified up-front when starting > Mesos masters currently. In addition, they should be consistent on every > master, otherwise unexpected behavior could occur (You can have them be > inconsistent for some upgrade paths / changing the set). > This makes it hard to introduce new groups of machines under new roles > dynamically (Have to generate a new master configuration, deploy that, before > we can connect slaves with a new role to the cluster). > Ideally an administrator can manually add / remove / edit roles and have the > settings replicated / passed to all masters in the cluster by Mesos. > Effectively Mesos takes ownership of the setting, rather than requiring it to > be done externally. > In addition, if a new slave joins the cluster with an unexpected / new role > that should just work, making it much easier to introduce machines with new > roles. (Policy around whether or not a slave can cause creation of a new > role, a given slave can register with a given role, etc. is out of scope, and > would be controls in the general registration process). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
