[jira] [Commented] (MESOS-4558) Reduce the running time of benchmark tests.
[
https://issues.apache.org/jira/browse/MESOS-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369990#comment-15369990
]
Guangya Liu commented on MESOS-4558:
[~jjanco] is trying to make the looping numbers of the benchmark as
configurable by a batch size which can reduce the time of benchmark test.
Please refer to https://reviews.apache.org/r/49616/ for detail.
> Reduce the running time of benchmark tests.
> ---
>
> Key: MESOS-4558
> URL: https://issues.apache.org/jira/browse/MESOS-4558
> Project: Mesos
> Issue Type: Task
>Reporter: Vinod Kone
> Labels: newbie++
>
> Currently benchmark tests take a long time (>5 hours). It would be nice to
> reduce the total time taken by the benchmark tests to enable us to run them
> on ASF CI.
> Command to run only benchmark tests
> {code}
> MESOS_BENCHMARK=1 GTEST_FILTER="*BENCHMARK*" make check
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-5701) Add benchmark for sorter performance
[ https://issues.apache.org/jira/browse/MESOS-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangya Liu reassigned MESOS-5701: -- Assignee: Guangya Liu > Add benchmark for sorter performance > > > Key: MESOS-5701 > URL: https://issues.apache.org/jira/browse/MESOS-5701 > Project: Mesos > Issue Type: Bug > Components: allocation >Reporter: Klaus Ma >Assignee: Guangya Liu > > Add benchmark of sorter in allocation for Allocation Performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5745) AuthenticationTest.UnauthenticatedSlave fails with clang++3.8
[
https://issues.apache.org/jira/browse/MESOS-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369957#comment-15369957
]
Benjamin Bannier commented on MESOS-5745:
-
Applying the unmerged upstream libcxx patch http://reviews.llvm.org/D20786
removes this failure.
> AuthenticationTest.UnauthenticatedSlave fails with clang++3.8
> -
>
> Key: MESOS-5745
> URL: https://issues.apache.org/jira/browse/MESOS-5745
> Project: Mesos
> Issue Type: Bug
> Components: test
>Reporter: Michael Park
> Labels: mesosphere
>
> With {{clang++-3.8}}, {{make check}} fails with the following message:
> {noformat}
> [ RUN ] AuthenticationTest.UnauthenticatedSlave
> *** Aborted at 1467208613 (unix time) try "date -d @1467208613" if you are
> using GNU date ***
> PC: @0x10b7f5a8b std::__1::__tree<>::__assign_multi<>()
> *** SIGSEGV (@0x0) received by PID 40053 (TID 0x7fff73aaf000) stack trace: ***
> @ 0x7fff8af4252a _sigtramp
> @0x110216a00 (unknown)
> @0x10b7f5881 mesos::internal::logging::Flags::operator=()
> @0x10b7f3076 mesos::internal::slave::Flags::operator=()
> @0x10b7f1cbf mesos::internal::tests::cluster::Slave::start()
> @0x10bf1a2d1 mesos::internal::tests::MesosTest::StartSlave()
> @0x10b7511b9
> mesos::internal::tests::AuthenticationTest_UnauthenticatedSlave_Test::TestBody()
> @0x10c703caa
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @0x10c703b0a testing::Test::Run()
> @0x10c704b02 testing::TestInfo::Run()
> @0x10c7053c3 testing::TestCase::Run()
> @0x10c70cefb testing::internal::UnitTestImpl::RunAllTests()
> @0x10c70ca43
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @0x10c70c95e testing::UnitTest::Run()
> @0x10bbe44f3 main
> @ 0x7fff9071a5ad start
> make[3]: *** [check-local] Segmentation fault: 11
> make[2]: *** [check-am] Error 2
> make[1]: *** [check] Error 2
> make: *** [check-recursive] Error 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4823) Implement port forwarding in `network/cni` isolator
[ https://issues.apache.org/jira/browse/MESOS-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369950#comment-15369950 ] Eduard Serra commented on MESOS-4823: - Then, how about making the port-forwarding also plugin-based? Something similar to what IPAM plugins are for CNI, you could also have a different methods to decouple and specify your cluster port-forwarding mechanisms once the (internal?) IP of the container has been assigned on the setup by calling the specific plugin. > Implement port forwarding in `network/cni` isolator > --- > > Key: MESOS-4823 > URL: https://issues.apache.org/jira/browse/MESOS-4823 > Project: Mesos > Issue Type: Task > Components: containerization > Environment: linux >Reporter: Avinash Sridharan >Assignee: Avinash Sridharan >Priority: Critical > Labels: mesosphere > > Most docker and appc images wish to expose ports that micro-services are > listening on, to the outside world. When containers are running on bridged > (or ptp) networking this can be achieved by installing port forwarding rules > on the agent (using iptables). This can be done in the `network/cni` > isolator. > The reason we would like this functionality to be implemented in the > `network/cni` isolator, and not a CNI plugin, is that the specifications > currently do not support specifying port forwarding rules. Further, to > install these rules the isolator needs two pieces of information, the exposed > ports and the IP address associated with the container. Bother are available > to the isolator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5824) Include disk source information in stringification
[
https://issues.apache.org/jira/browse/MESOS-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369663#comment-15369663
]
ASF GitHub Bot commented on MESOS-5824:
---
Github user timcharper commented on the issue:
https://github.com/apache/mesos/pull/133
I've followed the instructions and the JIRA issue is here:
https://issues.apache.org/jira/browse/MESOS-5824
> Include disk source information in stringification
> --
>
> Key: MESOS-5824
> URL: https://issues.apache.org/jira/browse/MESOS-5824
> Project: Mesos
> Issue Type: Improvement
> Components: stout
>Affects Versions: 0.28.2
>Reporter: Tim Harper
> Fix For: 0.28.3
>
> Attachments: 0001-Output-disk-resource-source-information.patch
>
>
> Some frameworks (like kafka_mesos) ignore the Source field when trying to
> reserve an offered mount or path persistent volume; the resulting error
> message is bewildering:
> {code:none}
> Task uses more resources
> cpus(*):4; mem(*):4096; ports(*):[31000-31000]; disk(kafka,
> kafka)[kafka_0:data]:960679
> than available
> cpus(*):32; mem(*):256819; ports(*):[31000-32000]; disk(kafka,
> kafka)[kafka_0:data]:960679; disk(*):240169;
> {code}
> The stringification of disk resources should include source information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5714) Specify soname for libmesos.so to major release
[
https://issues.apache.org/jira/browse/MESOS-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369655#comment-15369655
]
Tim Harper commented on MESOS-5714:
---
If there is an implicit expectation that the API doesn't change in backwards
incompatible ways between point releases, then the configuration should be
updated to reflect that.
> Specify soname for libmesos.so to major release
> ---
>
> Key: MESOS-5714
> URL: https://issues.apache.org/jira/browse/MESOS-5714
> Project: Mesos
> Issue Type: Improvement
> Components: build
>Affects Versions: 0.28.2
>Reporter: Tim Harper
> Labels: build
>
> I've installed mesos using the CentOS 7 package, and am building the
> Ceph-Mesos framework. I've noticed when running {{ldd}} that {{ceph-mesos}}
> is depending on too specific of a version of libmesos, which means that the
> build will be broken on subsequent point releases.
> This seems to be because the {{soname}} for libmesos is set to a very
> unforgiving value. If {{libmesos-0.28.2}} truly isn't ABI compatible with
> {{libmesos-0.28.x}}, then I suppose this is set correctly and this ticket
> should be closed summarily, albeit unfortunate.
> Here is the {{readelf}} output for {{libmesos}}
> {code}
> [root@6e189e07b470 /]# readelf -d /usr/local/lib/libmesos-0.28.2.so
> Dynamic section at offset 0x194cd18 contains 43 entries:
> TagType Name/Value
> 0x0001 (NEEDED) Shared library: [libcrypt.so.1]
> 0x0001 (NEEDED) Shared library: [libexpat.so.1]
> 0x0001 (NEEDED) Shared library: [libdb-5.3.so]
> 0x0001 (NEEDED) Shared library: [libsasl2.so.3]
> 0x0001 (NEEDED) Shared library: [libsvn_delta-1.so.0]
> 0x0001 (NEEDED) Shared library: [libsvn_subr-1.so.0]
> 0x0001 (NEEDED) Shared library: [libaprutil-1.so.0]
> 0x0001 (NEEDED) Shared library: [libapr-1.so.0]
> 0x0001 (NEEDED) Shared library: [libpthread.so.0]
> 0x0001 (NEEDED) Shared library: [libdl.so.2]
> 0x0001 (NEEDED) Shared library: [libcurl.so.4]
> 0x0001 (NEEDED) Shared library: [libz.so.1]
> 0x0001 (NEEDED) Shared library: [librt.so.1]
> 0x0001 (NEEDED) Shared library: [libstdc++.so.6]
> 0x0001 (NEEDED) Shared library: [libm.so.6]
> 0x0001 (NEEDED) Shared library: [libc.so.6]
> 0x0001 (NEEDED) Shared library:
> [ld-linux-x86-64.so.2]
> 0x0001 (NEEDED) Shared library: [libgcc_s.so.1]
> 0x000e (SONAME) Library soname: [libmesos-0.28.2.so]
> 0x000f (RPATH) Library rpath: [/usr/lib/mesos]
> 0x000c (INIT) 0x92a1f0
> 0x000d (FINI) 0x13a8e94
> 0x0019 (INIT_ARRAY) 0x1ae
> 0x001b (INIT_ARRAYSZ) 1712 (bytes)
> 0x001a (FINI_ARRAY) 0x1ae8f38
> 0x001c (FINI_ARRAYSZ) 8 (bytes)
> 0x6ef5 (GNU_HASH) 0x228
> 0x0005 (STRTAB) 0x1b0be8
> 0x0006 (SYMTAB) 0x66a08
> 0x000a (STRSZ) 6130210 (bytes)
> 0x000b (SYMENT) 24 (bytes)
> 0x0003 (PLTGOT) 0x1b66000
> 0x0002 (PLTRELSZ) 387000 (bytes)
> 0x0014 (PLTREL) RELA
> 0x0017 (JMPREL) 0x8cba38
> 0x0007 (RELA) 0x7a5018
> 0x0008 (RELASZ) 1206816 (bytes)
> 0x0009 (RELAENT)24 (bytes)
> 0x6ffe (VERNEED)0x7a4e38
> 0x6fff (VERNEEDNUM) 8
> 0x6ff0 (VERSYM) 0x78960a
> 0x6ff9 (RELACOUNT) 1357
> 0x (NULL) 0x0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5714) Specify soname for libmesos.so to major release
[
https://issues.apache.org/jira/browse/MESOS-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369654#comment-15369654
]
Tim Harper commented on MESOS-5714:
---
The Ceph Mesos framework is written in C++
> Specify soname for libmesos.so to major release
> ---
>
> Key: MESOS-5714
> URL: https://issues.apache.org/jira/browse/MESOS-5714
> Project: Mesos
> Issue Type: Improvement
> Components: build
>Affects Versions: 0.28.2
>Reporter: Tim Harper
> Labels: build
>
> I've installed mesos using the CentOS 7 package, and am building the
> Ceph-Mesos framework. I've noticed when running {{ldd}} that {{ceph-mesos}}
> is depending on too specific of a version of libmesos, which means that the
> build will be broken on subsequent point releases.
> This seems to be because the {{soname}} for libmesos is set to a very
> unforgiving value. If {{libmesos-0.28.2}} truly isn't ABI compatible with
> {{libmesos-0.28.x}}, then I suppose this is set correctly and this ticket
> should be closed summarily, albeit unfortunate.
> Here is the {{readelf}} output for {{libmesos}}
> {code}
> [root@6e189e07b470 /]# readelf -d /usr/local/lib/libmesos-0.28.2.so
> Dynamic section at offset 0x194cd18 contains 43 entries:
> TagType Name/Value
> 0x0001 (NEEDED) Shared library: [libcrypt.so.1]
> 0x0001 (NEEDED) Shared library: [libexpat.so.1]
> 0x0001 (NEEDED) Shared library: [libdb-5.3.so]
> 0x0001 (NEEDED) Shared library: [libsasl2.so.3]
> 0x0001 (NEEDED) Shared library: [libsvn_delta-1.so.0]
> 0x0001 (NEEDED) Shared library: [libsvn_subr-1.so.0]
> 0x0001 (NEEDED) Shared library: [libaprutil-1.so.0]
> 0x0001 (NEEDED) Shared library: [libapr-1.so.0]
> 0x0001 (NEEDED) Shared library: [libpthread.so.0]
> 0x0001 (NEEDED) Shared library: [libdl.so.2]
> 0x0001 (NEEDED) Shared library: [libcurl.so.4]
> 0x0001 (NEEDED) Shared library: [libz.so.1]
> 0x0001 (NEEDED) Shared library: [librt.so.1]
> 0x0001 (NEEDED) Shared library: [libstdc++.so.6]
> 0x0001 (NEEDED) Shared library: [libm.so.6]
> 0x0001 (NEEDED) Shared library: [libc.so.6]
> 0x0001 (NEEDED) Shared library:
> [ld-linux-x86-64.so.2]
> 0x0001 (NEEDED) Shared library: [libgcc_s.so.1]
> 0x000e (SONAME) Library soname: [libmesos-0.28.2.so]
> 0x000f (RPATH) Library rpath: [/usr/lib/mesos]
> 0x000c (INIT) 0x92a1f0
> 0x000d (FINI) 0x13a8e94
> 0x0019 (INIT_ARRAY) 0x1ae
> 0x001b (INIT_ARRAYSZ) 1712 (bytes)
> 0x001a (FINI_ARRAY) 0x1ae8f38
> 0x001c (FINI_ARRAYSZ) 8 (bytes)
> 0x6ef5 (GNU_HASH) 0x228
> 0x0005 (STRTAB) 0x1b0be8
> 0x0006 (SYMTAB) 0x66a08
> 0x000a (STRSZ) 6130210 (bytes)
> 0x000b (SYMENT) 24 (bytes)
> 0x0003 (PLTGOT) 0x1b66000
> 0x0002 (PLTRELSZ) 387000 (bytes)
> 0x0014 (PLTREL) RELA
> 0x0017 (JMPREL) 0x8cba38
> 0x0007 (RELA) 0x7a5018
> 0x0008 (RELASZ) 1206816 (bytes)
> 0x0009 (RELAENT)24 (bytes)
> 0x6ffe (VERNEED)0x7a4e38
> 0x6fff (VERNEEDNUM) 8
> 0x6ff0 (VERSYM) 0x78960a
> 0x6ff9 (RELACOUNT) 1357
> 0x (NULL) 0x0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5829) Mesos should be able to consume module for replicated_log
[
https://issues.apache.org/jira/browse/MESOS-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Guo updated MESOS-5829:
---
External issue ID: (was: https://issues.apache.org/jira/browse/MESOS-5828)
> Mesos should be able to consume module for replicated_log
> -
>
> Key: MESOS-5829
> URL: https://issues.apache.org/jira/browse/MESOS-5829
> Project: Mesos
> Issue Type: Bug
> Components: modules, replicated log
>Reporter: Jay Guo
>Assignee: Jay Guo
>
> Currently {{--quorum}} is hardcoded to 1 if no *zk* provided, assuming
> standalone mode, however this is not the true when using master contender and
> detector modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5829) Mesos should be able to consume module for replicated_log
Jay Guo created MESOS-5829:
--
Summary: Mesos should be able to consume module for replicated_log
Key: MESOS-5829
URL: https://issues.apache.org/jira/browse/MESOS-5829
Project: Mesos
Issue Type: Bug
Components: modules, replicated log
Reporter: Jay Guo
Assignee: Jay Guo
Currently {{--quorum}} is hardcoded to 1 if no *zk* provided, assuming
standalone mode, however this is not the true when using master contender and
detector modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5828) Modularize Network in replicated_log
Jay Guo created MESOS-5828: -- Summary: Modularize Network in replicated_log Key: MESOS-5828 URL: https://issues.apache.org/jira/browse/MESOS-5828 Project: Mesos Issue Type: Bug Components: replicated log Reporter: Jay Guo Assignee: Jay Guo Currently replicated_log relies on Zookeeper for coordinator election. This is done through network abstraction _ZookeeperNetwork_. We need to modularize this part in order to enable replicated_log when using Master contender/detector modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5827) Add example framework for using inverse offers
Artem Harutyunyan created MESOS-5827: Summary: Add example framework for using inverse offers Key: MESOS-5827 URL: https://issues.apache.org/jira/browse/MESOS-5827 Project: Mesos Issue Type: Task Reporter: Artem Harutyunyan Priority: Minor We should have an example framework (in src/examples) demonstrating how to handle inverse offers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5826) Streamline building of example frameworks
Artem Harutyunyan created MESOS-5826: Summary: Streamline building of example frameworks Key: MESOS-5826 URL: https://issues.apache.org/jira/browse/MESOS-5826 Project: Mesos Issue Type: Task Reporter: Artem Harutyunyan Priority: Minor Currently there is no easy way to build example frameworks. One has to do make check and wait until the entire test suites compiles. It'd be great to have an easy way to build example frameworks independently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5708) Add authz to /files/debug
[ https://issues.apache.org/jira/browse/MESOS-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369473#comment-15369473 ] Adam B commented on MESOS-5708: --- commit 49db3424bb6ad906596449668735dafbe744626f Author: Abhishek Dasgupta Date: Sun Jul 10 00:56:42 2016 -0700 Added text for authorization in endpoint docs for '/files/debug'. Review: https://reviews.apache.org/r/49794/ > Add authz to /files/debug > - > > Key: MESOS-5708 > URL: https://issues.apache.org/jira/browse/MESOS-5708 > Project: Mesos > Issue Type: Task > Components: security >Reporter: Adam B >Assignee: Abhishek Dasgupta >Priority: Minor > Labels: mesosphere, security > Fix For: 1.0.0 > > > The /files/debug endpoint exposes the attached master/agent log paths and > every attached sandbox path, which includes the frameworkId and executorId. > Even if sandboxes are protected, we still don't want to expose this > information to unauthorized users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5514) Implement LIST_FILES Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-5514: -- Shepherd: Anand Mazumdar > Implement LIST_FILES Call in v1 agent API. > -- > > Key: MESOS-5514 > URL: https://issues.apache.org/jira/browse/MESOS-5514 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Abhishek Dasgupta > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
