[jira] [Commented] (MESOS-1925) Docker kill does not allow containers to exit gracefully
[ https://issues.apache.org/jira/browse/MESOS-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190216#comment-14190216 ] Ryan Thomas commented on MESOS-1925: [~tnachen] is there anything more to do in order to get this patch merged? Docker kill does not allow containers to exit gracefully Key: MESOS-1925 URL: https://issues.apache.org/jira/browse/MESOS-1925 Project: Mesos Issue Type: Improvement Components: containerization Affects Versions: 0.20.1 Reporter: Ryan Thomas Assignee: Timothy Chen The docker implementation uses the docker kill command, this immediately terminated the container, not allowing it to exit gracefully. We should be using the docker stop command that will send a kill after a predetermined amount of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2015) Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
Till Toenshoff created MESOS-2015:
-
Summary: Build failure due to unconditional linux/ns.hpp inclusion
in OSX builds
Key: MESOS-2015
URL: https://issues.apache.org/jira/browse/MESOS-2015
Project: Mesos
Issue Type: Bug
Environment: OSX 10.10, clang 3.5
Reporter: Till Toenshoff
{noformat}
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT tests/mesos_tests-credentials_tests.o -MD
-MP -MF tests/.deps/mesos_tests-credentials_tests.Tpo -c -o
tests/mesos_tests-credentials_tests.o `test -f 'tests/credentials_tests.cpp' ||
echo '../../src/'`tests/credentials_tests.cpp
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT
tests/mesos_tests-docker_containerizer_tests.o -MD -MP -MF
tests/.deps/mesos_tests-docker_containerizer_tests.Tpo -c -o
tests/mesos_tests-docker_containerizer_tests.o `test -f
'tests/docker_containerizer_tests.cpp' || echo '../../src/'`
tests/docker_containerizer_tests.cpp
In file included from ../../src/tests/setns_test_helper.cpp:24:
../../src/linux/ns.hpp:20:2: error: linux/ns.hpp is only available on Linux
systems.
#error linux/ns.hpp is only available on Linux systems.
^
In file included from ../../src/tests/setns_test_helper.cpp:24:
In file included from ../../src/linux/ns.hpp:36:
../../3rdparty/libprocess/3rdparty/stout/include/stout/proc.hpp:19:2: error:
stout/proc.hpp is only available on Linux systems.
#error stout/proc.hpp is only available on Linux systems.
^
../../3rdparty/libprocess/3rdparty/stout/include/stout/proc.hpp:48:11: error:
redefinition of 'proc' as different kind of symbol
namespace proc {
^
/usr/include/sys/proc.h:84:8: note: previous definition is here
struct
[jira] [Commented] (MESOS-2015) Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
[
https://issues.apache.org/jira/browse/MESOS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190312#comment-14190312
]
Till Toenshoff commented on MESOS-2015:
---
[~idownes] could you please have a look?
Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
---
Key: MESOS-2015
URL: https://issues.apache.org/jira/browse/MESOS-2015
Project: Mesos
Issue Type: Bug
Environment: OSX 10.10, clang 3.5
Reporter: Till Toenshoff
{noformat}
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT tests/mesos_tests-credentials_tests.o -MD
-MP -MF tests/.deps/mesos_tests-credentials_tests.Tpo -c -o
tests/mesos_tests-credentials_tests.o `test -f 'tests/credentials_tests.cpp'
|| echo '../../src/'`tests/credentials_tests.cpp
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT
tests/mesos_tests-docker_containerizer_tests.o -MD -MP -MF
tests/.deps/mesos_tests-docker_containerizer_tests.Tpo -c -o
tests/mesos_tests-docker_containerizer_tests.o `test -f
'tests/docker_containerizer_tests.cpp' || echo '../../src/'`
tests/docker_containerizer_tests.cpp
In file included from ../../src/tests/setns_test_helper.cpp:24:
../../src/linux/ns.hpp:20:2: error: linux/ns.hpp is only available on Linux
systems.
#error linux/ns.hpp is only available on Linux systems.
^
In file included from ../../src/tests/setns_test_helper.cpp:24:
In file included from ../../src/linux/ns.hpp:36:
[jira] [Created] (MESOS-2017) Segfault with Pure virtual method called when tests fail
Yan Xu created MESOS-2017:
-
Summary: Segfault with Pure virtual method called when tests fail
Key: MESOS-2017
URL: https://issues.apache.org/jira/browse/MESOS-2017
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.21.0
Reporter: Yan Xu
The most recent one:
{noformat:title=DRFAllocatorTest.DRFAllocatorProcess}
[ RUN ] DRFAllocatorTest.DRFAllocatorProcess
Using temporary directory '/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j'
I1030 05:55:06.934813 24459 leveldb.cpp:176] Opened db in 3.175202ms
I1030 05:55:06.935925 24459 leveldb.cpp:183] Compacted db in 1.077924ms
I1030 05:55:06.935976 24459 leveldb.cpp:198] Created db iterator in 16460ns
I1030 05:55:06.935995 24459 leveldb.cpp:204] Seeked to beginning of db in 2018ns
I1030 05:55:06.936005 24459 leveldb.cpp:273] Iterated through 0 keys in the db
in 335ns
I1030 05:55:06.936039 24459 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
I1030 05:55:06.936705 24480 recover.cpp:437] Starting replica recovery
I1030 05:55:06.937023 24480 recover.cpp:463] Replica is in EMPTY status
I1030 05:55:06.938158 24475 replica.cpp:638] Replica in EMPTY status received a
broadcasted recover request
I1030 05:55:06.938859 24482 recover.cpp:188] Received a recover response from a
replica in EMPTY status
I1030 05:55:06.939486 24474 recover.cpp:554] Updating replica status to STARTING
I1030 05:55:06.940249 24489 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 591981ns
I1030 05:55:06.940274 24489 replica.cpp:320] Persisted replica status to
STARTING
I1030 05:55:06.940752 24481 recover.cpp:463] Replica is in STARTING status
I1030 05:55:06.940820 24489 master.cpp:312] Master
20141030-055506-3142697795-40429-24459 (pomona.apache.org) started on
67.195.81.187:40429
I1030 05:55:06.940871 24489 master.cpp:358] Master only allowing authenticated
frameworks to register
I1030 05:55:06.940891 24489 master.cpp:363] Master only allowing authenticated
slaves to register
I1030 05:55:06.940908 24489 credentials.hpp:36] Loading credentials for
authentication from
'/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j/credentials'
I1030 05:55:06.941215 24489 master.cpp:392] Authorization enabled
I1030 05:55:06.941751 24475 master.cpp:120] No whitelist given. Advertising
offers for all slaves
I1030 05:55:06.942227 24474 replica.cpp:638] Replica in STARTING status
received a broadcasted recover request
I1030 05:55:06.942401 24476 hierarchical_allocator_process.hpp:299]
Initializing hierarchical allocator process with master :
master@67.195.81.187:40429
I1030 05:55:06.942895 24483 recover.cpp:188] Received a recover response from a
replica in STARTING status
I1030 05:55:06.943035 24474 master.cpp:1242] The newly elected leader is
master@67.195.81.187:40429 with id 20141030-055506-3142697795-40429-24459
I1030 05:55:06.943063 24474 master.cpp:1255] Elected as the leading master!
I1030 05:55:06.943079 24474 master.cpp:1073] Recovering from registrar
I1030 05:55:06.943313 24480 registrar.cpp:313] Recovering registrar
I1030 05:55:06.943455 24475 recover.cpp:554] Updating replica status to VOTING
I1030 05:55:06.944144 24474 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 536365ns
I1030 05:55:06.944172 24474 replica.cpp:320] Persisted replica status to VOTING
I1030 05:55:06.944355 24489 recover.cpp:568] Successfully joined the Paxos group
I1030 05:55:06.944576 24489 recover.cpp:452] Recover process terminated
I1030 05:55:06.945155 24486 log.cpp:656] Attempting to start the writer
I1030 05:55:06.947013 24473 replica.cpp:474] Replica received implicit promise
request with proposal 1
I1030 05:55:06.947854 24473 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 806463ns
I1030 05:55:06.947883 24473 replica.cpp:342] Persisted promised to 1
I1030 05:55:06.948547 24481 coordinator.cpp:230] Coordinator attemping to fill
missing position
I1030 05:55:06.950269 24479 replica.cpp:375] Replica received explicit promise
request for position 0 with proposal 2
I1030 05:55:06.950933 24479 leveldb.cpp:343] Persisting action (8 bytes) to
leveldb took 603843ns
I1030 05:55:06.950961 24479 replica.cpp:676] Persisted action at 0
I1030 05:55:06.952180 24476 replica.cpp:508] Replica received write request for
position 0
I1030 05:55:06.952239 24476 leveldb.cpp:438] Reading position from leveldb took
28437ns
I1030 05:55:06.952896 24476 leveldb.cpp:343] Persisting action (14 bytes) to
leveldb took 623980ns
I1030 05:55:06.952926 24476 replica.cpp:676] Persisted action at 0
I1030 05:55:06.953543 24485 replica.cpp:655] Replica received learned notice
for position 0
I1030 05:55:06.954082 24485 leveldb.cpp:343] Persisting action (16 bytes) to
leveldb took 511807ns
I1030 05:55:06.954107 24485 replica.cpp:676] Persisted action at 0
I1030 05:55:06.954128 24485 replica.cpp:661] Replica
[jira] [Commented] (MESOS-2017) Segfault with Pure virtual method called when tests fail
[
https://issues.apache.org/jira/browse/MESOS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190480#comment-14190480
]
Yan Xu commented on MESOS-2017:
---
[~jvanremoortere] do you think it could be due to the recently libprocess
change?
Segfault with Pure virtual method called when tests fail
--
Key: MESOS-2017
URL: https://issues.apache.org/jira/browse/MESOS-2017
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.21.0
Reporter: Yan Xu
The most recent one:
{noformat:title=DRFAllocatorTest.DRFAllocatorProcess}
[ RUN ] DRFAllocatorTest.DRFAllocatorProcess
Using temporary directory '/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j'
I1030 05:55:06.934813 24459 leveldb.cpp:176] Opened db in 3.175202ms
I1030 05:55:06.935925 24459 leveldb.cpp:183] Compacted db in 1.077924ms
I1030 05:55:06.935976 24459 leveldb.cpp:198] Created db iterator in 16460ns
I1030 05:55:06.935995 24459 leveldb.cpp:204] Seeked to beginning of db in
2018ns
I1030 05:55:06.936005 24459 leveldb.cpp:273] Iterated through 0 keys in the
db in 335ns
I1030 05:55:06.936039 24459 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
I1030 05:55:06.936705 24480 recover.cpp:437] Starting replica recovery
I1030 05:55:06.937023 24480 recover.cpp:463] Replica is in EMPTY status
I1030 05:55:06.938158 24475 replica.cpp:638] Replica in EMPTY status received
a broadcasted recover request
I1030 05:55:06.938859 24482 recover.cpp:188] Received a recover response from
a replica in EMPTY status
I1030 05:55:06.939486 24474 recover.cpp:554] Updating replica status to
STARTING
I1030 05:55:06.940249 24489 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 591981ns
I1030 05:55:06.940274 24489 replica.cpp:320] Persisted replica status to
STARTING
I1030 05:55:06.940752 24481 recover.cpp:463] Replica is in STARTING status
I1030 05:55:06.940820 24489 master.cpp:312] Master
20141030-055506-3142697795-40429-24459 (pomona.apache.org) started on
67.195.81.187:40429
I1030 05:55:06.940871 24489 master.cpp:358] Master only allowing
authenticated frameworks to register
I1030 05:55:06.940891 24489 master.cpp:363] Master only allowing
authenticated slaves to register
I1030 05:55:06.940908 24489 credentials.hpp:36] Loading credentials for
authentication from
'/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j/credentials'
I1030 05:55:06.941215 24489 master.cpp:392] Authorization enabled
I1030 05:55:06.941751 24475 master.cpp:120] No whitelist given. Advertising
offers for all slaves
I1030 05:55:06.942227 24474 replica.cpp:638] Replica in STARTING status
received a broadcasted recover request
I1030 05:55:06.942401 24476 hierarchical_allocator_process.hpp:299]
Initializing hierarchical allocator process with master :
master@67.195.81.187:40429
I1030 05:55:06.942895 24483 recover.cpp:188] Received a recover response from
a replica in STARTING status
I1030 05:55:06.943035 24474 master.cpp:1242] The newly elected leader is
master@67.195.81.187:40429 with id 20141030-055506-3142697795-40429-24459
I1030 05:55:06.943063 24474 master.cpp:1255] Elected as the leading master!
I1030 05:55:06.943079 24474 master.cpp:1073] Recovering from registrar
I1030 05:55:06.943313 24480 registrar.cpp:313] Recovering registrar
I1030 05:55:06.943455 24475 recover.cpp:554] Updating replica status to VOTING
I1030 05:55:06.944144 24474 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 536365ns
I1030 05:55:06.944172 24474 replica.cpp:320] Persisted replica status to
VOTING
I1030 05:55:06.944355 24489 recover.cpp:568] Successfully joined the Paxos
group
I1030 05:55:06.944576 24489 recover.cpp:452] Recover process terminated
I1030 05:55:06.945155 24486 log.cpp:656] Attempting to start the writer
I1030 05:55:06.947013 24473 replica.cpp:474] Replica received implicit
promise request with proposal 1
I1030 05:55:06.947854 24473 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 806463ns
I1030 05:55:06.947883 24473 replica.cpp:342] Persisted promised to 1
I1030 05:55:06.948547 24481 coordinator.cpp:230] Coordinator attemping to
fill missing position
I1030 05:55:06.950269 24479 replica.cpp:375] Replica received explicit
promise request for position 0 with proposal 2
I1030 05:55:06.950933 24479 leveldb.cpp:343] Persisting action (8 bytes) to
leveldb took 603843ns
I1030 05:55:06.950961 24479 replica.cpp:676] Persisted action at 0
I1030 05:55:06.952180 24476 replica.cpp:508] Replica received write request
for position 0
I1030 05:55:06.952239 24476 leveldb.cpp:438] Reading position from leveldb
took 28437ns
I1030 05:55:06.952896 24476 leveldb.cpp:343] Persisting action (14 bytes) to
leveldb took 623980ns
[jira] [Commented] (MESOS-2017) Segfault with Pure virtual method called when tests fail
[
https://issues.apache.org/jira/browse/MESOS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190505#comment-14190505
]
Dominic Hamon commented on MESOS-2017:
--
This looks a lot like static destruction ordering. Ie, we have a method being
called on an object that is partially destructed.
Segfault with Pure virtual method called when tests fail
--
Key: MESOS-2017
URL: https://issues.apache.org/jira/browse/MESOS-2017
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.21.0
Reporter: Yan Xu
The most recent one:
{noformat:title=DRFAllocatorTest.DRFAllocatorProcess}
[ RUN ] DRFAllocatorTest.DRFAllocatorProcess
Using temporary directory '/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j'
I1030 05:55:06.934813 24459 leveldb.cpp:176] Opened db in 3.175202ms
I1030 05:55:06.935925 24459 leveldb.cpp:183] Compacted db in 1.077924ms
I1030 05:55:06.935976 24459 leveldb.cpp:198] Created db iterator in 16460ns
I1030 05:55:06.935995 24459 leveldb.cpp:204] Seeked to beginning of db in
2018ns
I1030 05:55:06.936005 24459 leveldb.cpp:273] Iterated through 0 keys in the
db in 335ns
I1030 05:55:06.936039 24459 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
I1030 05:55:06.936705 24480 recover.cpp:437] Starting replica recovery
I1030 05:55:06.937023 24480 recover.cpp:463] Replica is in EMPTY status
I1030 05:55:06.938158 24475 replica.cpp:638] Replica in EMPTY status received
a broadcasted recover request
I1030 05:55:06.938859 24482 recover.cpp:188] Received a recover response from
a replica in EMPTY status
I1030 05:55:06.939486 24474 recover.cpp:554] Updating replica status to
STARTING
I1030 05:55:06.940249 24489 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 591981ns
I1030 05:55:06.940274 24489 replica.cpp:320] Persisted replica status to
STARTING
I1030 05:55:06.940752 24481 recover.cpp:463] Replica is in STARTING status
I1030 05:55:06.940820 24489 master.cpp:312] Master
20141030-055506-3142697795-40429-24459 (pomona.apache.org) started on
67.195.81.187:40429
I1030 05:55:06.940871 24489 master.cpp:358] Master only allowing
authenticated frameworks to register
I1030 05:55:06.940891 24489 master.cpp:363] Master only allowing
authenticated slaves to register
I1030 05:55:06.940908 24489 credentials.hpp:36] Loading credentials for
authentication from
'/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j/credentials'
I1030 05:55:06.941215 24489 master.cpp:392] Authorization enabled
I1030 05:55:06.941751 24475 master.cpp:120] No whitelist given. Advertising
offers for all slaves
I1030 05:55:06.942227 24474 replica.cpp:638] Replica in STARTING status
received a broadcasted recover request
I1030 05:55:06.942401 24476 hierarchical_allocator_process.hpp:299]
Initializing hierarchical allocator process with master :
master@67.195.81.187:40429
I1030 05:55:06.942895 24483 recover.cpp:188] Received a recover response from
a replica in STARTING status
I1030 05:55:06.943035 24474 master.cpp:1242] The newly elected leader is
master@67.195.81.187:40429 with id 20141030-055506-3142697795-40429-24459
I1030 05:55:06.943063 24474 master.cpp:1255] Elected as the leading master!
I1030 05:55:06.943079 24474 master.cpp:1073] Recovering from registrar
I1030 05:55:06.943313 24480 registrar.cpp:313] Recovering registrar
I1030 05:55:06.943455 24475 recover.cpp:554] Updating replica status to VOTING
I1030 05:55:06.944144 24474 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 536365ns
I1030 05:55:06.944172 24474 replica.cpp:320] Persisted replica status to
VOTING
I1030 05:55:06.944355 24489 recover.cpp:568] Successfully joined the Paxos
group
I1030 05:55:06.944576 24489 recover.cpp:452] Recover process terminated
I1030 05:55:06.945155 24486 log.cpp:656] Attempting to start the writer
I1030 05:55:06.947013 24473 replica.cpp:474] Replica received implicit
promise request with proposal 1
I1030 05:55:06.947854 24473 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 806463ns
I1030 05:55:06.947883 24473 replica.cpp:342] Persisted promised to 1
I1030 05:55:06.948547 24481 coordinator.cpp:230] Coordinator attemping to
fill missing position
I1030 05:55:06.950269 24479 replica.cpp:375] Replica received explicit
promise request for position 0 with proposal 2
I1030 05:55:06.950933 24479 leveldb.cpp:343] Persisting action (8 bytes) to
leveldb took 603843ns
I1030 05:55:06.950961 24479 replica.cpp:676] Persisted action at 0
I1030 05:55:06.952180 24476 replica.cpp:508] Replica received write request
for position 0
I1030 05:55:06.952239 24476 leveldb.cpp:438] Reading position from leveldb
took 28437ns
I1030 05:55:06.952896 24476 leveldb.cpp
[jira] [Assigned] (MESOS-2016) docker_name_prefix is too generic
[
https://issues.apache.org/jira/browse/MESOS-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Chen reassigned MESOS-2016:
---
Assignee: Timothy Chen
docker_name_prefix is too generic
-
Key: MESOS-2016
URL: https://issues.apache.org/jira/browse/MESOS-2016
Project: Mesos
Issue Type: Bug
Reporter: Jay Buffington
Assignee: Timothy Chen
From docker.hpp and docker.cpp:
{quote}
// Prefix used to name Docker containers in order to distinguish those
// created by Mesos from those created manually.
extern std::string DOCKER_NAME_PREFIX;
// TODO(benh): At some point to run multiple slaves we'll need to make
// the Docker container name creation include the slave ID.
string DOCKER_NAME_PREFIX = mesos-;
{quote}
This name is too generic. A common pattern in docker land is to run
everything in a container and use volume mounts to share sockets do RPC
between containers. CoreOS has popularized this technique.
Inevitably, what people do is start a container named mesos-slave which
runs the docker containerizer recovery code which removes all containers that
start with mesos- And then ask huh, why did my mesos-slave docker
container die? I don't see any error messages...
Ideally, we should do what Ben suggested and add the slave id to the name
prefix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2017) Segfault with Pure virtual method called when tests fail
[
https://issues.apache.org/jira/browse/MESOS-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190602#comment-14190602
]
Joris Van Remoortere commented on MESOS-2017:
-
[~xujyan] which change are you referring to specifically? I can help track this
down if you need help.
Segfault with Pure virtual method called when tests fail
--
Key: MESOS-2017
URL: https://issues.apache.org/jira/browse/MESOS-2017
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.21.0
Reporter: Yan Xu
The most recent one:
{noformat:title=DRFAllocatorTest.DRFAllocatorProcess}
[ RUN ] DRFAllocatorTest.DRFAllocatorProcess
Using temporary directory '/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j'
I1030 05:55:06.934813 24459 leveldb.cpp:176] Opened db in 3.175202ms
I1030 05:55:06.935925 24459 leveldb.cpp:183] Compacted db in 1.077924ms
I1030 05:55:06.935976 24459 leveldb.cpp:198] Created db iterator in 16460ns
I1030 05:55:06.935995 24459 leveldb.cpp:204] Seeked to beginning of db in
2018ns
I1030 05:55:06.936005 24459 leveldb.cpp:273] Iterated through 0 keys in the
db in 335ns
I1030 05:55:06.936039 24459 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
I1030 05:55:06.936705 24480 recover.cpp:437] Starting replica recovery
I1030 05:55:06.937023 24480 recover.cpp:463] Replica is in EMPTY status
I1030 05:55:06.938158 24475 replica.cpp:638] Replica in EMPTY status received
a broadcasted recover request
I1030 05:55:06.938859 24482 recover.cpp:188] Received a recover response from
a replica in EMPTY status
I1030 05:55:06.939486 24474 recover.cpp:554] Updating replica status to
STARTING
I1030 05:55:06.940249 24489 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 591981ns
I1030 05:55:06.940274 24489 replica.cpp:320] Persisted replica status to
STARTING
I1030 05:55:06.940752 24481 recover.cpp:463] Replica is in STARTING status
I1030 05:55:06.940820 24489 master.cpp:312] Master
20141030-055506-3142697795-40429-24459 (pomona.apache.org) started on
67.195.81.187:40429
I1030 05:55:06.940871 24489 master.cpp:358] Master only allowing
authenticated frameworks to register
I1030 05:55:06.940891 24489 master.cpp:363] Master only allowing
authenticated slaves to register
I1030 05:55:06.940908 24489 credentials.hpp:36] Loading credentials for
authentication from
'/tmp/DRFAllocatorTest_DRFAllocatorProcess_BI905j/credentials'
I1030 05:55:06.941215 24489 master.cpp:392] Authorization enabled
I1030 05:55:06.941751 24475 master.cpp:120] No whitelist given. Advertising
offers for all slaves
I1030 05:55:06.942227 24474 replica.cpp:638] Replica in STARTING status
received a broadcasted recover request
I1030 05:55:06.942401 24476 hierarchical_allocator_process.hpp:299]
Initializing hierarchical allocator process with master :
master@67.195.81.187:40429
I1030 05:55:06.942895 24483 recover.cpp:188] Received a recover response from
a replica in STARTING status
I1030 05:55:06.943035 24474 master.cpp:1242] The newly elected leader is
master@67.195.81.187:40429 with id 20141030-055506-3142697795-40429-24459
I1030 05:55:06.943063 24474 master.cpp:1255] Elected as the leading master!
I1030 05:55:06.943079 24474 master.cpp:1073] Recovering from registrar
I1030 05:55:06.943313 24480 registrar.cpp:313] Recovering registrar
I1030 05:55:06.943455 24475 recover.cpp:554] Updating replica status to VOTING
I1030 05:55:06.944144 24474 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 536365ns
I1030 05:55:06.944172 24474 replica.cpp:320] Persisted replica status to
VOTING
I1030 05:55:06.944355 24489 recover.cpp:568] Successfully joined the Paxos
group
I1030 05:55:06.944576 24489 recover.cpp:452] Recover process terminated
I1030 05:55:06.945155 24486 log.cpp:656] Attempting to start the writer
I1030 05:55:06.947013 24473 replica.cpp:474] Replica received implicit
promise request with proposal 1
I1030 05:55:06.947854 24473 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 806463ns
I1030 05:55:06.947883 24473 replica.cpp:342] Persisted promised to 1
I1030 05:55:06.948547 24481 coordinator.cpp:230] Coordinator attemping to
fill missing position
I1030 05:55:06.950269 24479 replica.cpp:375] Replica received explicit
promise request for position 0 with proposal 2
I1030 05:55:06.950933 24479 leveldb.cpp:343] Persisting action (8 bytes) to
leveldb took 603843ns
I1030 05:55:06.950961 24479 replica.cpp:676] Persisted action at 0
I1030 05:55:06.952180 24476 replica.cpp:508] Replica received write request
for position 0
I1030 05:55:06.952239 24476 leveldb.cpp:438] Reading position from leveldb
took 28437ns
I1030 05:55:06.952896 24476 leveldb.cpp:343
[jira] [Updated] (MESOS-719) missing-call-to-setgroups
[ https://issues.apache.org/jira/browse/MESOS-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Simon updated MESOS-719: Attachment: MESOS-719-0.20.1.patch Attached is a patch I've been using that fixes this. It calls initgroups after calling setgid so that the auxiliary groups for the su'd user are set. This is important for docker support because it lets you add your mesos user to the docker group so it can talk to docker through /var/run/docker.sock (which is owned by a docker group by default in most installations.) Without initgroups, the mesos user only has its primary GID set. missing-call-to-setgroups - Key: MESOS-719 URL: https://issues.apache.org/jira/browse/MESOS-719 Project: Mesos Issue Type: Bug Components: general Affects Versions: 0.15.0 Reporter: Timothy St. Clair Labels: newbie Attachments: MESOS-719-0.20.1.patch This traces into stout/os.hpp in vetting the code as part of fedora packaging, rpmlint outputs an error around priv-changing . mesos.x86_64: E: missing-call-to-setgroups /usr/lib64/libmesos-0.15.0.so.0.0.0 https://www.securecoding.cert.org/confluence/display/seccode/POS36-C.+Observe+correct+revocation+order+while+relinquishing+privileges -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-719) missing-call-to-setgroups
[ https://issues.apache.org/jira/browse/MESOS-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190759#comment-14190759 ] Ken Simon commented on MESOS-719: - (I'm not familiar with mesos's jira or review board processes, so I'm not sure where to put this patch other than here. Anyone who can help me, it would be appreciated!) missing-call-to-setgroups - Key: MESOS-719 URL: https://issues.apache.org/jira/browse/MESOS-719 Project: Mesos Issue Type: Bug Components: general Affects Versions: 0.15.0 Reporter: Timothy St. Clair Labels: newbie Attachments: MESOS-719-0.20.1.patch This traces into stout/os.hpp in vetting the code as part of fedora packaging, rpmlint outputs an error around priv-changing . mesos.x86_64: E: missing-call-to-setgroups /usr/lib64/libmesos-0.15.0.so.0.0.0 https://www.securecoding.cert.org/confluence/display/seccode/POS36-C.+Observe+correct+revocation+order+while+relinquishing+privileges -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-2015) Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
[
https://issues.apache.org/jira/browse/MESOS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Toenshoff reassigned MESOS-2015:
-
Assignee: Till Toenshoff
Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
---
Key: MESOS-2015
URL: https://issues.apache.org/jira/browse/MESOS-2015
Project: Mesos
Issue Type: Bug
Environment: OSX 10.10, clang 3.5
Reporter: Till Toenshoff
Assignee: Till Toenshoff
{noformat}
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT tests/mesos_tests-credentials_tests.o -MD
-MP -MF tests/.deps/mesos_tests-credentials_tests.Tpo -c -o
tests/mesos_tests-credentials_tests.o `test -f 'tests/credentials_tests.cpp'
|| echo '../../src/'`tests/credentials_tests.cpp
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT
tests/mesos_tests-docker_containerizer_tests.o -MD -MP -MF
tests/.deps/mesos_tests-docker_containerizer_tests.Tpo -c -o
tests/mesos_tests-docker_containerizer_tests.o `test -f
'tests/docker_containerizer_tests.cpp' || echo '../../src/'`
tests/docker_containerizer_tests.cpp
In file included from ../../src/tests/setns_test_helper.cpp:24:
../../src/linux/ns.hpp:20:2: error: linux/ns.hpp is only available on Linux
systems.
#error linux/ns.hpp is only available on Linux systems.
^
In file included from ../../src/tests/setns_test_helper.cpp:24:
In file included from ../../src/linux/ns.hpp:36:
../../3rdparty/libprocess/3rdparty/stout/include/stout/proc.hpp:19:2: error:
stout/proc.hpp
[jira] [Comment Edited] (MESOS-2015) Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
[
https://issues.apache.org/jira/browse/MESOS-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190312#comment-14190312
]
Till Toenshoff edited comment on MESOS-2015 at 10/30/14 9:28 PM:
-
[~idownes] could you please have a look?
Actually, was trivial to fix and I took the freedom to do it, please check:
https://reviews.apache.org/r/27395/
was (Author: tillt):
[~idownes] could you please have a look?
Build failure due to unconditional linux/ns.hpp inclusion in OSX builds
---
Key: MESOS-2015
URL: https://issues.apache.org/jira/browse/MESOS-2015
Project: Mesos
Issue Type: Bug
Environment: OSX 10.10, clang 3.5
Reporter: Till Toenshoff
{noformat}
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT tests/mesos_tests-credentials_tests.o -MD
-MP -MF tests/.deps/mesos_tests-credentials_tests.Tpo -c -o
tests/mesos_tests-credentials_tests.o `test -f 'tests/credentials_tests.cpp'
|| echo '../../src/'`tests/credentials_tests.cpp
g++ -DPACKAGE_NAME=\mesos\ -DPACKAGE_TARNAME=\mesos\
-DPACKAGE_VERSION=\0.21.0\ -DPACKAGE_STRING=\mesos\ 0.21.0\
-DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\mesos\
-DVERSION=\0.21.0\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_
STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
-DLT_OBJDIR=\.libs/\ -DHAVE_PTHREAD=1 -DHAVE_LIBZ=1 -DHAVE_LIBCURL=1
-DHAVE_LIBAPR_1=1 -DHAVE_LIBSVN_SUBR_1=1 -DHAVE_LIBSVN_DELTA_
1=1 -DHAVE_LIBSASL2=1 -I. -I../../src -Wall -Werror
-DLIBDIR=\/usr/local/lib\ -DPKGLIBEXECDIR=\/usr/local/libexec/mesos\
-DPKGDATADIR=\/usr/local/share/mesos\ -I../../include
-I../../3rdparty/libprocess/include
-I../../3rdparty/libprocess/3rdparty/stout/include -
I../include -I../include/mesos -I../3rdparty/libprocess/3rdparty/boost-1.53.0
-I../3rdparty/libprocess/3rdparty/picojson-4f93734
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-I../3rdparty/libprocess/3rdparty/glog-0.3.3/src
-I../3rdparty/libprocess/3rdparty/glog-0
.3.3/src -I../3rdparty/leveldb/include
-I../3rdparty/zookeeper-3.4.5/src/c/include
-I../3rdparty/zookeeper-3.4.5/src/c/generated
-I../3rdparty/libprocess/3rdparty/protobuf-2.5.0/src
-DSOURCE_DIR=\/Users/till/Development/mesos-private/build/..\
-DBUILD_DIR=\/Users/til
l/Development/mesos-private/build\
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/gtest/include
-I../3rdparty/libprocess/3rdparty/gmock-1.6.0/include
-I/usr/include/subversion-1 -I/usr/include/apr-1 -I/usr/include/apr-1.0
-D_THREAD_SAFE -g1 -O0 -std=c++11 -stdlib=libc
++ -DGTEST_USE_OWN_TR1_TUPLE=1 -MT
tests/mesos_tests-docker_containerizer_tests.o -MD -MP -MF
tests/.deps/mesos_tests-docker_containerizer_tests.Tpo -c -o
tests/mesos_tests-docker_containerizer_tests.o `test -f
'tests/docker_containerizer_tests.cpp' || echo '../../src/'`
tests/docker_containerizer_tests.cpp
In file included from ../../src/tests/setns_test_helper.cpp:24:
../../src/linux/ns.hpp:20:2: error: linux/ns.hpp is only available on Linux
systems.
#error
[jira] [Assigned] (MESOS-2018) Dynamic Resource Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B reassigned MESOS-2018: - Assignee: Adam B (was: Michael Park) Dynamic Resource Reservations - Key: MESOS-2018 URL: https://issues.apache.org/jira/browse/MESOS-2018 Project: Mesos Issue Type: Improvement Components: allocation, framework, master, slave Reporter: Adam B Assignee: Adam B Labels: offer, persistence, reservations, resource, stateful, storage This is a feature to provide better support for running stateful services on Mesos such as HDFS (Distributed Filesystem), Cassandra (Distributed Database), or MySQL (Local Database). Current resource reservations (henceforth called static reservations) are statically determined by the slave operator at slave start time, and individual frameworks have no authority to reserve resources themselves. Dynamic reservations allow a framework to dynamically/lazily reserve offered resources at task launch time, such that when that task completes, those resources will only be re-offered to the same framework (or other frameworks with the same role). This is especially useful if the framework's task stored some state on the slave, and needs a guaranteed set of resources reserved so that it can re-launch a task on the same slave to recover that state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Resource Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-2018: -- Assignee: Michael Park (was: Adam B) Dynamic Resource Reservations - Key: MESOS-2018 URL: https://issues.apache.org/jira/browse/MESOS-2018 Project: Mesos Issue Type: Improvement Components: allocation, framework, master, slave Reporter: Adam B Assignee: Michael Park Labels: offer, persistence, reservations, resource, stateful, storage This is a feature to provide better support for running stateful services on Mesos such as HDFS (Distributed Filesystem), Cassandra (Distributed Database), or MySQL (Local Database). Current resource reservations (henceforth called static reservations) are statically determined by the slave operator at slave start time, and individual frameworks have no authority to reserve resources themselves. Dynamic reservations allow a framework to dynamically/lazily reserve offered resources at task launch time, such that when that task completes, those resources will only be re-offered to the same framework (or other frameworks with the same role). This is especially useful if the framework's task stored some state on the slave, and needs a guaranteed set of resources reserved so that it can re-launch a task on the same slave to recover that state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Resource Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-2018: -- Assignee: Michael Park (was: Adam B) Dynamic Resource Reservations - Key: MESOS-2018 URL: https://issues.apache.org/jira/browse/MESOS-2018 Project: Mesos Issue Type: Improvement Components: allocation, framework, master, slave Reporter: Adam B Assignee: Michael Park Labels: offer, persistence, reservations, resource, stateful, storage This is a feature to provide better support for running stateful services on Mesos such as HDFS (Distributed Filesystem), Cassandra (Distributed Database), or MySQL (Local Database). Current resource reservations (henceforth called static reservations) are statically determined by the slave operator at slave start time, and individual frameworks have no authority to reserve resources themselves. Dynamic reservations allow a framework to dynamically/lazily reserve offered resources at task launch time, such that when that task completes, those resources will only be re-offered to the same framework (or other frameworks with the same role). This is especially useful if the framework's task stored some state on the slave, and needs a guaranteed set of resources reserved so that it can re-launch a task on the same slave to recover that state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-2018) Dynamic Resource Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B reassigned MESOS-2018: - Assignee: Adam B (was: Michael Park) Dynamic Resource Reservations - Key: MESOS-2018 URL: https://issues.apache.org/jira/browse/MESOS-2018 Project: Mesos Issue Type: Improvement Components: allocation, framework, master, slave Reporter: Adam B Assignee: Adam B Labels: offer, persistence, reservations, resource, stateful, storage This is a feature to provide better support for running stateful services on Mesos such as HDFS (Distributed Filesystem), Cassandra (Distributed Database), or MySQL (Local Database). Current resource reservations (henceforth called static reservations) are statically determined by the slave operator at slave start time, and individual frameworks have no authority to reserve resources themselves. Dynamic reservations allow a framework to dynamically/lazily reserve offered resources at task launch time, such that when that task completes, those resources will only be re-offered to the same framework (or other frameworks with the same role). This is especially useful if the framework's task stored some state on the slave, and needs a guaranteed set of resources reserved so that it can re-launch a task on the same slave to recover that state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1864) Add test integration for module developers
[ https://issues.apache.org/jira/browse/MESOS-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191162#comment-14191162 ] Kapil Arya commented on MESOS-1864: --- commit 5348496aafa9b09f2b85f84822b5b05308c6c844 Author: Kapil Arya ka...@mesosphere.io Date: Thu Oct 23 18:24:32 2014 + Added --modules flag for tests. This allows the user to specify the modules to load during tests. The modules are made available to the master and slave subsystems. Review: https://reviews.apache.org/r/26796 Add test integration for module developers -- Key: MESOS-1864 URL: https://issues.apache.org/jira/browse/MESOS-1864 Project: Mesos Issue Type: Task Components: modules Reporter: Niklas Quarfot Nielsen Assignee: Kapil Arya To help module developers write and test mesos-modules, we should wire up integration suites that let the usual unit tests be run with custom built modules. A couple of examples could be: $ ./bin/mesos-tests.sh --modules=path:name or a dedicated test scripts: $ ./bin/modules-test.sh --modules=path:name --isolation=name --authentication=name We should also think about how to encourage internal module testing (tests that will be specific for that particular module) In the case of ./bin/modules-test.sh - we could run 1) our own (general) tests and 2) tests provided by the module it self (maybe as an extra field in the module registration struct) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2019) Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept.
[ https://issues.apache.org/jira/browse/MESOS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evelina Dumitrescu updated MESOS-2019: -- Component/s: (was: libprocess) Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept. - Key: MESOS-2019 URL: https://issues.apache.org/jira/browse/MESOS-2019 Project: Mesos Issue Type: Improvement Components: framework Reporter: Evelina Dumitrescu Priority: Minor The Node class abstracts the endpoint notion: it defines the association of the ip and port for a connection.A node defines more the host(which can have multiple active endpoints). At the moment, the Node class is used to keep a mapping from a socket to the ip port pair in the process namespace. I want to propose to rename this class in Endpoint and also extend its use by replacing the ip port fields from the UPID class and process namespace with this type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2019) Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept.
[ https://issues.apache.org/jira/browse/MESOS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evelina Dumitrescu updated MESOS-2019: -- Description: The Node class abstracts the endpoint notion: it defines the association of the ip and port for a connection. A node defines more the host(which can have multiple active endpoints). At the moment, the Node class is used to keep a mapping from a socket to the ip port pair in the process namespace. I want to propose to rename this class in Endpoint and also extend its use by replacing the ip port fields from the UPID class and process namespace with this type. was: The Node class abstracts the endpoint notion: it defines the association of the ip and port for a connection.A node defines more the host(which can have multiple active endpoints). At the moment, the Node class is used to keep a mapping from a socket to the ip port pair in the process namespace. I want to propose to rename this class in Endpoint and also extend its use by replacing the ip port fields from the UPID class and process namespace with this type. Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept. - Key: MESOS-2019 URL: https://issues.apache.org/jira/browse/MESOS-2019 Project: Mesos Issue Type: Improvement Components: framework Reporter: Evelina Dumitrescu Priority: Minor The Node class abstracts the endpoint notion: it defines the association of the ip and port for a connection. A node defines more the host(which can have multiple active endpoints). At the moment, the Node class is used to keep a mapping from a socket to the ip port pair in the process namespace. I want to propose to rename this class in Endpoint and also extend its use by replacing the ip port fields from the UPID class and process namespace with this type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2019) Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept.
[ https://issues.apache.org/jira/browse/MESOS-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14191286#comment-14191286 ] Evelina Dumitrescu commented on MESOS-2019: --- https://reviews.apache.org/r/27413/ Rename the Node class in Endpoint and replace the ip and port pairs from the UPID class and process namespace with this concept. - Key: MESOS-2019 URL: https://issues.apache.org/jira/browse/MESOS-2019 Project: Mesos Issue Type: Improvement Components: framework Reporter: Evelina Dumitrescu Priority: Minor The Node class abstracts the endpoint notion: it defines the association of the ip and port for a connection. A node defines more the host(which can have multiple active endpoints). At the moment, the Node class is used to keep a mapping from a socket to the ip port pair in the process namespace. I want to propose to rename this class in Endpoint and also extend its use by replacing the ip port fields from the UPID class and process namespace with this type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
