[jira] [Created] (MESOS-1753) Allow default/deleted functions
Dominic Hamon created MESOS-1753: Summary: Allow default/deleted functions Key: MESOS-1753 URL: https://issues.apache.org/jira/browse/MESOS-1753 Project: Mesos Issue Type: Improvement Reporter: Dominic Hamon Assignee: Dominic Hamon Priority: Minor Add default/delete functions to the configure script. Once there, we can start using them across the code-base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-1044) Require C++11 compiler support.
[ https://issues.apache.org/jira/browse/MESOS-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon reassigned MESOS-1044: Assignee: Dominic Hamon Require C++11 compiler support. --- Key: MESOS-1044 URL: https://issues.apache.org/jira/browse/MESOS-1044 Project: Mesos Issue Type: Sub-task Reporter: Benjamin Mahler Assignee: Dominic Hamon Fix For: 0.21.0 As per MESOS-750, we're targeting 0.19.0 for removing support for older compilers that lack C++11 support. At the current time, Mesos requires gcc 4.8.x for C++11 builds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MESOS-1044) Require C++11 compiler support.
[ https://issues.apache.org/jira/browse/MESOS-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon resolved MESOS-1044. -- Resolution: Fixed Fix Version/s: 0.21.0 Require C++11 compiler support. --- Key: MESOS-1044 URL: https://issues.apache.org/jira/browse/MESOS-1044 Project: Mesos Issue Type: Sub-task Reporter: Benjamin Mahler Assignee: Dominic Hamon Fix For: 0.21.0 As per MESOS-750, we're targeting 0.19.0 for removing support for older compilers that lack C++11 support. At the current time, Mesos requires gcc 4.8.x for C++11 builds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1752) Allow variadic templates
[ https://issues.apache.org/jira/browse/MESOS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1752: - Sprint: Q3 Sprint 4 Allow variadic templates Key: MESOS-1752 URL: https://issues.apache.org/jira/browse/MESOS-1752 Project: Mesos Issue Type: Improvement Reporter: Dominic Hamon Assignee: Dominic Hamon Priority: Minor Labels: c++11 Add variadic templates to the C++11 configure check. Once there, we can start using them in the code-base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1753) Allow default/deleted functions
[ https://issues.apache.org/jira/browse/MESOS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1753: - Sprint: Q3 Sprint 4 Allow default/deleted functions --- Key: MESOS-1753 URL: https://issues.apache.org/jira/browse/MESOS-1753 Project: Mesos Issue Type: Improvement Reporter: Dominic Hamon Assignee: Dominic Hamon Priority: Minor Labels: c++11 Add default/delete functions to the configure script. Once there, we can start using them across the code-base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1753) Allow default/deleted functions
[ https://issues.apache.org/jira/browse/MESOS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118429#comment-14118429 ] Dominic Hamon commented on MESOS-1753: -- https://reviews.apache.org/r/25261/ Allow default/deleted functions --- Key: MESOS-1753 URL: https://issues.apache.org/jira/browse/MESOS-1753 Project: Mesos Issue Type: Improvement Reporter: Dominic Hamon Assignee: Dominic Hamon Priority: Minor Labels: c++11 Add default/delete functions to the configure script. Once there, we can start using them across the code-base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-1754) Mesos static library has undefined symbols from 3rd party deps
Vinod Kone created MESOS-1754:
-
Summary: Mesos static library has undefined symbols from 3rd party
deps
Key: MESOS-1754
URL: https://issues.apache.org/jira/browse/MESOS-1754
Project: Mesos
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Vinod Kone
Assignee: Vinod Kone
Looks like the static libmesos library that we build is missing some symbols
from 3rd party deps (e.g, GLOG, ZooKeeper). I suspect this has to do with the
order of libraries defined on the linker command line.
{code}
zookeeper_init symbol is present in .so but not in .a.
$ nm libmesos.so | grep zookeeper_init
030519f0 T zookeeper_init
$ nm libmesos.a | grep zookeeper_init
nm: libleveldb.a: File format not recognized
U zookeeper_init
Same with google::InstallFailureSignalHandler.
$ nm libmesos.so | grep InstallFailureSignalHandler
0301901d T _ZN6google27InstallFailureSignalHandlerEv
$ nm libmesos.a | grep InstallFailureSignalHandler
nm: libleveldb.a: File format not recognized
U _ZN6google27InstallFailureSignalHandlerEv
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-1735) Better Startup Failure For Duplicate Master
[ https://issues.apache.org/jira/browse/MESOS-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118544#comment-14118544 ] Benjamin Mahler commented on MESOS-1735: We could use the EXIT approach from stout/exit.hpp here to avoid the abort / stacktrace and to include a helpful message. Better Startup Failure For Duplicate Master --- Key: MESOS-1735 URL: https://issues.apache.org/jira/browse/MESOS-1735 Project: Mesos Issue Type: Bug Components: master Affects Versions: 0.20.0 Environment: Ubuntu 12.04 Reporter: Ken Sipe The error message is cryptic when starting a mesos-master when a mesos-master is already running. The error message is: mesos-master --ip=192.168.74.174 --work_dir=~/mesos WARNING: Logging before InitGoogleLogging() is written to STDERR F0826 20:24:56.940961 3057 process.cpp:1632] Failed to initialize, bind: Address already in use [98] *** Check failure stack trace: *** Aborted (core dumped) This can be a new person's first experience. It isn't clear to them that the process is already running. And they are lost as to what to do next. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-1755) Add docker support to mesos-execute
Vinod Kone created MESOS-1755: - Summary: Add docker support to mesos-execute Key: MESOS-1755 URL: https://issues.apache.org/jira/browse/MESOS-1755 Project: Mesos Issue Type: Bug Reporter: Vinod Kone Assignee: Timothy Chen The fix for this is already committed at https://reviews.apache.org/r/24808/. I'm creating this ticket to track that this patch gets included in 0.20.1 release, since apparently Singularity framework depends on this patch to work with Docker !?!? https://groups.google.com/forum/#!topic/singularity-users/GzzswbpI92E [~tnachen]: Can you confirm if this has to be included in 0.20.1? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1291) Use clang-format to automatically format code to style
[ https://issues.apache.org/jira/browse/MESOS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119082#comment-14119082 ] Michael Park commented on MESOS-1291: - I'm for moving forward with clang-format-3.5 as the standard. Here's the list of disagreements with Mesos Style Guide: - The braces after namespaces should not be wrapped. - The braces after structs and unions should be wrapped. - Parameters and arguments should be indented by 4 spaces rather than 2. - Overloaded operators should be padded with spaces. (e.g. Foo operator + (...);) - Should not follow Google's style of wrapping on open parentheses, we should try to reduce jaggedness in the code. The first 4 discrepancies are fixed in my branch of clang with 3 commits. 2 of which can probably be pushed upstream since they add useful options. One of them is adding a Mesos style BreakBeforeBraces attribute, which probably wouldn't go upstream as smoothly. Use clang-format to automatically format code to style -- Key: MESOS-1291 URL: https://issues.apache.org/jira/browse/MESOS-1291 Project: Mesos Issue Type: Improvement Components: technical debt Reporter: Dominic Hamon Labels: style Instead of relying on a script to check and report style errors, we should move to a workflow that allows people to write code how they feel comfortable and then automatically format it to conform to our style guide. The Chromium style from clang-format (http://clang.llvm.org/docs/ClangFormat.html) is very close to our style except for the dropped braces on class, struct, and function definitions, and two lines of whitespace between method definitions outside a class. As such, we should consider adopting clang-format and patching it to include a Mesos style variant. It can be run as part of post-reviews or as a git commit hook, or manually from within editors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1754) Mesos static library has undefined symbols from 3rd party deps
[
https://issues.apache.org/jira/browse/MESOS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119115#comment-14119115
]
Timothy St. Clair commented on MESOS-1754:
--
So you could do versioned.so file which was the original recommendation (ಠ_ಠ) ,
or you will have to extract and reassemble :
http://stackoverflow.com/questions/3821916/how-to-merge-two-ar-static-libraries-into-one
.
Mesos static library has undefined symbols from 3rd party deps
--
Key: MESOS-1754
URL: https://issues.apache.org/jira/browse/MESOS-1754
Project: Mesos
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Vinod Kone
Assignee: Vinod Kone
Looks like the static libmesos library that we build is missing some symbols
from 3rd party deps (e.g, GLOG, ZooKeeper). I suspect this has to do with the
order of libraries defined on the linker command line.
{code}
zookeeper_init symbol is present in .so but not in .a.
$ nm libmesos.so | grep zookeeper_init
030519f0 T zookeeper_init
$ nm libmesos.a | grep zookeeper_init
nm: libleveldb.a: File format not recognized
U zookeeper_init
Same with google::InstallFailureSignalHandler.
$ nm libmesos.so | grep InstallFailureSignalHandler
0301901d T _ZN6google27InstallFailureSignalHandlerEv
$ nm libmesos.a | grep InstallFailureSignalHandler
nm: libleveldb.a: File format not recognized
U _ZN6google27InstallFailureSignalHandlerEv
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-1756) Support etcd as an alternative for Zk in Mesos
Timothy Chen created MESOS-1756: --- Summary: Support etcd as an alternative for Zk in Mesos Key: MESOS-1756 URL: https://issues.apache.org/jira/browse/MESOS-1756 Project: Mesos Issue Type: Story Reporter: Timothy Chen With the increase number of etcd users, for them to use Mesos it's often required to run another zookeeper cluster just for Mesos. Will be ideal if Mesos can just run on Etcd as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1756) Support etcd as an alternative for Zk in Mesos
[ https://issues.apache.org/jira/browse/MESOS-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-1756: Priority: Minor (was: Major) Support etcd as an alternative for Zk in Mesos -- Key: MESOS-1756 URL: https://issues.apache.org/jira/browse/MESOS-1756 Project: Mesos Issue Type: Story Reporter: Timothy Chen Priority: Minor With the increase number of etcd users, for them to use Mesos it's often required to run another zookeeper cluster just for Mesos. Will be ideal if Mesos can just run on Etcd as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MESOS-1643) Provide APIs to return port resource for a given role
[ https://issues.apache.org/jira/browse/MESOS-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone resolved MESOS-1643. --- Resolution: Fixed Fix Version/s: 0.21.0 commit 18344e03e4bcfde6157997e28265084e2e10d971 Author: Zuyu Zhang hit...@gmail.com Date: Tue Sep 2 21:38:06 2014 -0700 Added Resources support to return the port range for the given number of ports. Review: https://reviews.apache.org/r/24810 Provide APIs to return port resource for a given role - Key: MESOS-1643 URL: https://issues.apache.org/jira/browse/MESOS-1643 Project: Mesos Issue Type: Improvement Reporter: Zuyu Zhang Assignee: Zuyu Zhang Priority: Trivial Fix For: 0.21.0 It makes more sense to return port resource for a given role, rather than all ports in Resources. In mesos/resource.hpp: OptionValue::Ranges Resources::ports(const string role = *); // Check whether Resources have the given number (num_port) of ports, and return the begin number of the port range. Optionlong Resources::getPorts(long num_port, const string role = *); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
