[jira] [Updated] (MESOS-2436) Adapt unit test relying on non-checkpointing slaves
[ https://issues.apache.org/jira/browse/MESOS-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rukletsov updated MESOS-2436: --- Target Version/s: 0.23.0 > Adapt unit test relying on non-checkpointing slaves > --- > > Key: MESOS-2436 > URL: https://issues.apache.org/jira/browse/MESOS-2436 > Project: Mesos > Issue Type: Technical task >Reporter: Joerg Schad >Assignee: Joerg Schad > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2486) With unbundled dependencies Mesos doesn't build with -Wl,--no-copy-dt-needed-entries
[
https://issues.apache.org/jira/browse/MESOS-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-2486:
--
Target Version/s: 0.22.0
> With unbundled dependencies Mesos doesn't build with
> -Wl,--no-copy-dt-needed-entries
>
>
> Key: MESOS-2486
> URL: https://issues.apache.org/jira/browse/MESOS-2486
> Project: Mesos
> Issue Type: Bug
> Components: build
>Affects Versions: 0.22.0
> Environment: Ubuntu 14.10
>Reporter: Cody Maloney
>Assignee: Cody Maloney
>Priority: Blocker
> Labels: mesosphere
>
> To build a module, glog, protobuf, and boost need to be unbundled so they can
> be used by both the module as well as Mesos.
> In a bundled build, we build the libraries into libmesos.la / libmesos.so, so
> every program picks them up.
> In unbundled dependencies are used, we link against all of the dynamic
> libraries / .so files manually. We link libmesos.so against them, then link
> all the other programs against libmesos.so to get the dependencies.
> This relies on the DT_NEEDED flag "copying" the .so's dependencies into the
> executable. [Ubuntu and
> Debian|https://wiki.ubuntu.com/ToolChain/CompilerFlags#A-Wl.2C--no-copy-dt-needed-entries]
> forcibly add the flag `-Wl,--no-copy-dt-needed-entries` to the linker to
> disable this.
> This breaks the build with unbundled dependencies on those platforms. Some
> sample error messages:
> {code}
> /usr/bin/ld: log/mesos_log-main.o: undefined reference to symbol
> '_ZN6google4base21CheckOpMessageBuilder7ForVar2Ev'
> /usr/bin/ld: local/mesos_local-main.o: undefined reference to symbol
> '_ZN6google4base21CheckOpMessageBuilder7ForVar2Ev'
> cli/mesos-mesos.o: In function `os::getenv(std::string const&, bool) [clone
> .part.30]':
> mesos.cpp:(.text.unlikely+0x2b): undefined reference to
> `google::LogMessageFatal::LogMessageFatal(char const*, int)'
> mesos.cpp:(.text.unlikely+0x33): undefined reference to
> `google::LogMessage::stream()'
> mesos.cpp:(.text.unlikely+0x66): undefined reference to
> `google::LogMessageFatal::~LogMessageFatal()'
> collect2: error: ld returned 1 exit status
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2495) Evaluate a suitable regular expressions library
[ https://issues.apache.org/jira/browse/MESOS-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361336#comment-14361336 ] Alexander Rukletsov commented on MESOS-2495: We already have boost 1.53 as a dependency in stout. We can wrap boost::regex and expose it from stout. > Evaluate a suitable regular expressions library > --- > > Key: MESOS-2495 > URL: https://issues.apache.org/jira/browse/MESOS-2495 > Project: Mesos > Issue Type: Wish >Reporter: Alexander Rojas > > There are a couple of situations where regular expressions would be an easy > solution within mesos (i.e. disabling endpoints). So far no regex library has > been introduced in order to avoid binary dependencies; however, given regex > power, we would like to evaluate which library could be introduced and how > would be the best way to do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2487) Ensure protobuf "==" operator does not go out of sync with new protobuf fields
[ https://issues.apache.org/jira/browse/MESOS-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361314#comment-14361314 ] Alexander Rukletsov commented on MESOS-2487: I wonder whether a single comparison operation is enough. We definitely need a notion of equivalence, I think that maps to what Michael calls essential fields. But do we need equality in terms of, say, raw bytes equality? Anyway, it looks like we can't avoid writing custom equivalence test functions for our messages. > Ensure protobuf "==" operator does not go out of sync with new protobuf fields > -- > > Key: MESOS-2487 > URL: https://issues.apache.org/jira/browse/MESOS-2487 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone > > Currently when a new field is added to a protobuf that has a custom "==" > operator defined, we don't make sure that the field is accounted for in the > comparison. Ideally we should catch such errors at build time or 'make check' > time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2162) Consider a C++ implementation of CoreOS AppContainer spec
[ https://issues.apache.org/jira/browse/MESOS-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-2162: Labels: gsoc mesosphere twitter (was: mesosphere twitter) > Consider a C++ implementation of CoreOS AppContainer spec > - > > Key: MESOS-2162 > URL: https://issues.apache.org/jira/browse/MESOS-2162 > Project: Mesos > Issue Type: Story > Components: containerization >Reporter: Dominic Hamon > Labels: gsoc, mesosphere, twitter > > CoreOS have released a > [specification|https://github.com/coreos/rocket/blob/master/app-container/SPEC.md] > for a container abstraction as an alternative to Docker. They have also > released a reference implementation, [rocket|https://coreos.com/blog/rocket/]. > We should consider a C++ implementation of the specification to have parity > with the community and then use this implementation for our containerizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akanksha Agrawal updated MESOS-1194:
Comment: was deleted
(was: Added the required validation in the constructor:
)
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359142#comment-14359142
]
Akanksha Agrawal edited comment on MESOS-1194 at 3/13/15 7:36 PM:
--
Added the required validation in the constructor:
was (Author: akanksha08):
Added the required validatiion in the constructor:
{quote}
if (!message.IsInitialized()) {
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
{quote}
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359142#comment-14359142
]
Akanksha Agrawal edited comment on MESOS-1194 at 3/13/15 7:36 PM:
--
Added the required validatiion in the constructor:
{quote}
if (!message.IsInitialized()) {
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
{quote}
was (Author: akanksha08):
Added the required validatiion in the constructor:
if (!message.IsInitialized()) {
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359142#comment-14359142
]
Akanksha Agrawal edited comment on MESOS-1194 at 3/13/15 7:34 PM:
--
Added the required validatiion in the constructor:
if (!message.IsInitialized()) {
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
was (Author: akanksha08):
In if (!message.IsInitialized()) {
Changed
return Error(message.InitializationErrorString() +
" is required but not initialized");
to
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
in protobuf.hpp
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-577) bootstrap fails with automake 1.14
[
https://issues.apache.org/jira/browse/MESOS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360965#comment-14360965
]
Cody Maloney commented on MESOS-577:
Not using subdir-objects is going to go away according to current bootstrap /
autoreconf options... We should update mesos to not need the flag at all or fix
the instances which are broken. This is likely to bite us before too much
longer with a new automake release.
{code}
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled. For now, the corresponding
output
automake: object file(s) will be placed in the top-level directory. However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same
subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
{code}
> bootstrap fails with automake 1.14
> --
>
> Key: MESOS-577
> URL: https://issues.apache.org/jira/browse/MESOS-577
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.14.0
> Environment: OSX 10.8.4
>Reporter: Vinod Kone
>Assignee: Timothy St. Clair
> Fix For: 0.19.0
>
>
> Related to http://comments.gmane.org/gmane.comp.web.curl.library/39737
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-2497) Create synchronous validations for Calls
Isabel Jimenez created MESOS-2497: - Summary: Create synchronous validations for Calls Key: MESOS-2497 URL: https://issues.apache.org/jira/browse/MESOS-2497 Project: Mesos Issue Type: Technical task Reporter: Isabel Jimenez Assignee: Isabel Jimenez /call endpoint will return 202 accepted code but has to do some basic validations before. In case of invalidation it will return a 4xx code. We have to create a mechanism that will validate the 'request' and send back the appropriate code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2497) Create synchronous validations for Calls
[ https://issues.apache.org/jira/browse/MESOS-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-2497: -- Labels: HTTP mesosphere (was: HTTP) > Create synchronous validations for Calls > > > Key: MESOS-2497 > URL: https://issues.apache.org/jira/browse/MESOS-2497 > Project: Mesos > Issue Type: Technical task >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > Labels: HTTP, mesosphere > > /call endpoint will return 202 accepted code but has to do some basic > validations before. In case of invalidation it will return a 4xx code. We > have to create a mechanism that will validate the 'request' and send back the > appropriate code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2497) Create synchronous validations for Calls
[ https://issues.apache.org/jira/browse/MESOS-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-2497: -- Description: /call endpoint will return a 202 accepted code but has to do some basic validations before. In case of invalidation it will return a 4xx code. We have to create a mechanism that will validate the 'request' and send back the appropriate code. (was: /call endpoint will return 202 accepted code but has to do some basic validations before. In case of invalidation it will return a 4xx code. We have to create a mechanism that will validate the 'request' and send back the appropriate code.) > Create synchronous validations for Calls > > > Key: MESOS-2497 > URL: https://issues.apache.org/jira/browse/MESOS-2497 > Project: Mesos > Issue Type: Technical task >Reporter: Isabel Jimenez >Assignee: Isabel Jimenez > Labels: HTTP, mesosphere > > /call endpoint will return a 202 accepted code but has to do some basic > validations before. In case of invalidation it will return a 4xx code. We > have to create a mechanism that will validate the 'request' and send back the > appropriate code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2402) MesosContainerizerDestroyTest.LauncherDestroyFailure is flaky
[
https://issues.apache.org/jira/browse/MESOS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360913#comment-14360913
]
Vinod Kone commented on MESOS-2402:
---
Unable to repro this locally.
Submitted a small patch to print the errno to aid further debugging.
{code}
commit 958dff7d7a52977129cb87c003277b6290dff9eb
Author: Vinod Kone
Date: Fri Mar 13 11:46:47 2015 -0700
Print errno in process:childMain().
diff --git a/3rdparty/libprocess/src/subprocess.cpp
b/3rdparty/libprocess/src/subprocess.cpp
index 859a4f7..ab8a343 100644
--- a/3rdparty/libprocess/src/subprocess.cpp
+++ b/3rdparty/libprocess/src/subprocess.cpp
@@ -162,7 +162,7 @@ static int childMain(
os::execvpe(path.c_str(), argv, (*envp)());
- ABORT("Failed to os::execvpe in childMain\n");
+ ABORT(string("Failed to os::execvpe in childMain: ") + strerror(errno));
}
{code}
> MesosContainerizerDestroyTest.LauncherDestroyFailure is flaky
> -
>
> Key: MESOS-2402
> URL: https://issues.apache.org/jira/browse/MESOS-2402
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Vinod Kone
>Assignee: Vinod Kone
>
> "Failed to os::execvpe in childMain". Never seen this one before.
> {code}
> [ RUN ] MesosContainerizerDestroyTest.LauncherDestroyFailure
> Using temporary directory
> '/tmp/MesosContainerizerDestroyTest_LauncherDestroyFailure_QpjQEn'
> I0224 18:55:49.326912 21391 containerizer.cpp:461] Starting container
> 'test_container' for executor 'executor' of framework ''
> I0224 18:55:49.332252 21391 launcher.cpp:130] Forked child with pid '23496'
> for container 'test_container'
> ABORT: (src/subprocess.cpp:165): Failed to os::execvpe in childMain
> *** Aborted at 1424832949 (unix time) try "date -d @1424832949" if you are
> using GNU date ***
> PC: @ 0x2b178c5db0d5 (unknown)
> I0224 18:55:49.340955 21392 process.cpp:2117] Dropped / Lost event for PID:
> scheduler-509d37ac-296f-4429-b101-af433c1800e9@127.0.1.1:39647
> I0224 18:55:49.342300 21386 containerizer.cpp:911] Destroying container
> 'test_container'
> *** SIGABRT (@0x3e85bc8) received by PID 23496 (TID 0x2b178f9f0700) from
> PID 23496; stack trace: ***
> @ 0x2b178c397cb0 (unknown)
> @ 0x2b178c5db0d5 (unknown)
> @ 0x2b178c5de83b (unknown)
> @ 0x87a945 _Abort()
> @ 0x2b1789f610b9 process::childMain()
> I0224 18:55:49.391793 21386 containerizer.cpp:1120] Executor for container
> 'test_container' has exited
> I0224 18:55:49.400478 21391 process.cpp:2770] Handling HTTP event for process
> 'metrics' with path: '/metrics/snapshot'
> tests/containerizer_tests.cpp:485: Failure
> Value of: metrics.values["containerizer/mesos/container_destroy_errors"]
> Actual: 16-byte object <02-00 00-00 17-2B 00-00 E0-86 0E-04 00-00 00-00>
> Expected: 1u
> Which is: 1
> [ FAILED ] MesosContainerizerDestroyTest.LauncherDestroyFailure (89 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2290) Move all scheduler driver validations to master
[ https://issues.apache.org/jira/browse/MESOS-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-2290: -- Labels: mesosphere (was: ) > Move all scheduler driver validations to master > --- > > Key: MESOS-2290 > URL: https://issues.apache.org/jira/browse/MESOS-2290 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Isabel Jimenez > Labels: mesosphere > > With HTTP API, the scheduler driver will no longer exist and hence all the > validations should move to the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2297) Add authentication support for HTTP API
[ https://issues.apache.org/jira/browse/MESOS-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-2297: -- Labels: mesosphere (was: ) > Add authentication support for HTTP API > --- > > Key: MESOS-2297 > URL: https://issues.apache.org/jira/browse/MESOS-2297 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Isabel Jimenez > Labels: mesosphere > > To start with, we will only support basic http auth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2293) Implement the Call endpoint on master
[ https://issues.apache.org/jira/browse/MESOS-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez updated MESOS-2293: -- Labels: mesosphere twitter (was: twitter) > Implement the Call endpoint on master > - > > Key: MESOS-2293 > URL: https://issues.apache.org/jira/browse/MESOS-2293 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Isabel Jimenez > Labels: mesosphere, twitter > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-2293) Implement the Call endpoint on master
[ https://issues.apache.org/jira/browse/MESOS-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isabel Jimenez reassigned MESOS-2293: - Assignee: Isabel Jimenez > Implement the Call endpoint on master > - > > Key: MESOS-2293 > URL: https://issues.apache.org/jira/browse/MESOS-2293 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Isabel Jimenez > Labels: twitter > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359142#comment-14359142
]
Akanksha Agrawal edited comment on MESOS-1194 at 3/13/15 6:07 PM:
--
In if (!message.IsInitialized()) {
Changed return Error(message.InitializationErrorString() +
" is required but not initialized");
to std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
in protobuf.hpp
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359142#comment-14359142
]
Akanksha Agrawal edited comment on MESOS-1194 at 3/13/15 6:07 PM:
--
In if (!message.IsInitialized()) {
Changed
return Error(message.InitializationErrorString() +
" is required but not initialized");
to
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
in protobuf.hpp
was (Author: akanksha08):
In if (!message.IsInitialized()) {
Changed return Error(message.InitializationErrorString() +
" is required but not initialized");
to std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
in protobuf.hpp
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-1194) protobuf-JSON rendering doesnt validate
[
https://issues.apache.org/jira/browse/MESOS-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359142#comment-14359142
]
Akanksha Agrawal edited comment on MESOS-1194 at 3/13/15 6:08 PM:
--
In if (!message.IsInitialized()) {
Changed
return Error(message.InitializationErrorString() +
" is required but not initialized");
to
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
in protobuf.hpp
was (Author: akanksha08):
In if (!message.IsInitialized()) {
Changed
return Error(message.InitializationErrorString() +
" is required but not initialized");
to
std::cerr << "Protobuf not initialized: " <<
message.InitializationErrorString() << std::endl;
abort();
}
in protobuf.hpp
> protobuf-JSON rendering doesnt validate
> ---
>
> Key: MESOS-1194
> URL: https://issues.apache.org/jira/browse/MESOS-1194
> Project: Mesos
> Issue Type: Bug
> Components: stout
>Affects Versions: 0.19.0
>Reporter: Till Toenshoff
>Assignee: Akanksha Agrawal
>Priority: Minor
> Labels: json, newbie, protobuf, stout
>
> When using JSON::Protobuf(Message&), the supplied protobuf is not checked for
> being properly initialized, hence e.g. required fields could be missing.
> It would be desirable to have a feedback mechanism in place for this
> constructor - maybe this would do:
> {noformat}
> if (!message.IsInitialized()) {
> std::cerr << "Protobuf not initialized: " <<
> message.InitializationErrorString() << std::endl;
> abort();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2402) MesosContainerizerDestroyTest.LauncherDestroyFailure is flaky
[
https://issues.apache.org/jira/browse/MESOS-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360742#comment-14360742
]
Vinod Kone commented on MESOS-2402:
---
Looks like os::execvpe is failing!
> MesosContainerizerDestroyTest.LauncherDestroyFailure is flaky
> -
>
> Key: MESOS-2402
> URL: https://issues.apache.org/jira/browse/MESOS-2402
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.23.0
>Reporter: Vinod Kone
>Assignee: Vinod Kone
>
> "Failed to os::execvpe in childMain". Never seen this one before.
> {code}
> [ RUN ] MesosContainerizerDestroyTest.LauncherDestroyFailure
> Using temporary directory
> '/tmp/MesosContainerizerDestroyTest_LauncherDestroyFailure_QpjQEn'
> I0224 18:55:49.326912 21391 containerizer.cpp:461] Starting container
> 'test_container' for executor 'executor' of framework ''
> I0224 18:55:49.332252 21391 launcher.cpp:130] Forked child with pid '23496'
> for container 'test_container'
> ABORT: (src/subprocess.cpp:165): Failed to os::execvpe in childMain
> *** Aborted at 1424832949 (unix time) try "date -d @1424832949" if you are
> using GNU date ***
> PC: @ 0x2b178c5db0d5 (unknown)
> I0224 18:55:49.340955 21392 process.cpp:2117] Dropped / Lost event for PID:
> scheduler-509d37ac-296f-4429-b101-af433c1800e9@127.0.1.1:39647
> I0224 18:55:49.342300 21386 containerizer.cpp:911] Destroying container
> 'test_container'
> *** SIGABRT (@0x3e85bc8) received by PID 23496 (TID 0x2b178f9f0700) from
> PID 23496; stack trace: ***
> @ 0x2b178c397cb0 (unknown)
> @ 0x2b178c5db0d5 (unknown)
> @ 0x2b178c5de83b (unknown)
> @ 0x87a945 _Abort()
> @ 0x2b1789f610b9 process::childMain()
> I0224 18:55:49.391793 21386 containerizer.cpp:1120] Executor for container
> 'test_container' has exited
> I0224 18:55:49.400478 21391 process.cpp:2770] Handling HTTP event for process
> 'metrics' with path: '/metrics/snapshot'
> tests/containerizer_tests.cpp:485: Failure
> Value of: metrics.values["containerizer/mesos/container_destroy_errors"]
> Actual: 16-byte object <02-00 00-00 17-2B 00-00 E0-86 0E-04 00-00 00-00>
> Expected: 1u
> Which is: 1
> [ FAILED ] MesosContainerizerDestroyTest.LauncherDestroyFailure (89 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2487) Ensure protobuf "==" operator does not go out of sync with new protobuf fields
[ https://issues.apache.org/jira/browse/MESOS-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360660#comment-14360660 ] Vinod Kone commented on MESOS-2487: --- Thanks Michael for the thorough thoughts! This was the reason I created a new JIRA and didn't (attempt to) solve it in the previous review :) > Ensure protobuf "==" operator does not go out of sync with new protobuf fields > -- > > Key: MESOS-2487 > URL: https://issues.apache.org/jira/browse/MESOS-2487 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone > > Currently when a new field is added to a protobuf that has a custom "==" > operator defined, we don't make sure that the field is accounted for in the > comparison. Ideally we should catch such errors at build time or 'make check' > time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2496) Make description consistent when adding flags
[ https://issues.apache.org/jira/browse/MESOS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schad updated MESOS-2496: --- Description: When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent in adding newline at the end of the the description. For example mesos-slave.sh --help sometimes has a empty line between flags and sometimes not. Personally I like extra empty line between flags as it makes the help text more readable, but most importantly we should have this consistent. Actually other tools such as gcc do not have newlines between flags. was: When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent in adding newline at the end of the the description. For example mesos-slave.sh --help sometimes has a empty line between flags and sometimes not. Personally I like extra empty line between flags as it makes the help text more readable, but most importantly we should have this consistent. > Make description consistent when adding flags > - > > Key: MESOS-2496 > URL: https://issues.apache.org/jira/browse/MESOS-2496 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad >Priority: Minor > > When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent > in adding newline at the end of the the description. For example > mesos-slave.sh --help sometimes has a empty line between flags and sometimes > not. > Personally I like extra empty line between flags as it makes the help text > more readable, but most importantly we should have this consistent. > Actually other tools such as gcc do not have newlines between flags. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2496) Make description consistent when adding flags
[ https://issues.apache.org/jira/browse/MESOS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360589#comment-14360589 ] Alexander Rojas commented on MESOS-2496: I like the idea of having a line break after every description. It creates a visual boundary between flags. > Make description consistent when adding flags > - > > Key: MESOS-2496 > URL: https://issues.apache.org/jira/browse/MESOS-2496 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad >Priority: Minor > > When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent > in adding newline at the end of the the description. For example > mesos-slave.sh --help sometimes has a empty line between flags and sometimes > not. > Personally I like extra empty line between flags as it makes the help text > more readable, but most importantly we should have this consistent. > Actually other tools such as gcc do not have newlines between flags. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2496) Make description consistent when adding flags
[ https://issues.apache.org/jira/browse/MESOS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schad updated MESOS-2496: --- Summary: Make description consistent when adding flags (was: Make description text when adding flags consistent) > Make description consistent when adding flags > - > > Key: MESOS-2496 > URL: https://issues.apache.org/jira/browse/MESOS-2496 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad >Priority: Minor > > When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent > in adding newline at the end of the the description. For example > mesos-slave.sh --help sometimes has a empty line between flags and sometimes > not. > Personally I like extra empty line between flags as it makes the help text > more readable, but most importantly we should have this consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2496) Make description text when adding flags consistent
Joerg Schad created MESOS-2496: -- Summary: Make description text when adding flags consistent Key: MESOS-2496 URL: https://issues.apache.org/jira/browse/MESOS-2496 Project: Mesos Issue Type: Task Reporter: Joerg Schad Assignee: Joerg Schad Priority: Minor When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent in adding newline at the end of the the description. For example mesos-slave.sh --help sometimes has a empty line between flags and sometimes not. Personally I like extra empty line between flags as it makes the help text more readable, but most importantly we should have this consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2191) Add ContainerId to the TaskStatus message
[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas updated MESOS-2191:
---
Shepherd: Till Toenshoff
> Add ContainerId to the TaskStatus message
> -
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
>Reporter: Marcel Neuhausler
>Assignee: Alexander Rojas
> Labels: mesosphere
>
> {{TaskStatus}} provides the frameworks with certain information
> ({{executorId}}, {{slaveId}}, etc.) which is useful when collecting
> statistics about cluster performance; however, it is difficult to associate
> tasks to the container it is executed since this information stays always
> within mesos itself. Therefore it would be good to provide the framework
> scheduler with this information, adding a new field in the {{TaskStatus}}
> message.
> See comments for a use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2191) Add ContainerId to the TaskStatus message
[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360503#comment-14360503
]
Alexander Rojas commented on MESOS-2191:
https://reviews.apache.org/r/31985/
https://reviews.apache.org/r/31986/
> Add ContainerId to the TaskStatus message
> -
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
>Reporter: Marcel Neuhausler
>Assignee: Alexander Rojas
> Labels: mesosphere
>
> {{TaskStatus}} provides the frameworks with certain information
> ({{executorId}}, {{slaveId}}, etc.) which is useful when collecting
> statistics about cluster performance; however, it is difficult to associate
> tasks to the container it is executed since this information stays always
> within mesos itself. Therefore it would be good to provide the framework
> scheduler with this information, adding a new field in the {{TaskStatus}}
> message.
> See comments for a use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2495) Evaluate a suitable regular expressions library
[ https://issues.apache.org/jira/browse/MESOS-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360468#comment-14360468 ] Michael Park commented on MESOS-2495: - I'm wondering what the issues are with having a binary dependency. Could you explain a little? Is it a portability issue? Increases the size of the mesos library or binary drastically? > Evaluate a suitable regular expressions library > --- > > Key: MESOS-2495 > URL: https://issues.apache.org/jira/browse/MESOS-2495 > Project: Mesos > Issue Type: Wish >Reporter: Alexander Rojas > > There are a couple of situations where regular expressions would be an easy > solution within mesos (i.e. disabling endpoints). So far no regex library has > been introduced in order to avoid binary dependencies; however, given regex > power, we would like to evaluate which library could be introduced and how > would be the best way to do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2495) Evaluate a suitable regular expressions library
Alexander Rojas created MESOS-2495: -- Summary: Evaluate a suitable regular expressions library Key: MESOS-2495 URL: https://issues.apache.org/jira/browse/MESOS-2495 Project: Mesos Issue Type: Bug Reporter: Alexander Rojas There are a couple of situations where regular expressions would be an easy solution within mesos (i.e. disabling endpoints). So far no regex library has been introduced in order to avoid binary dependencies; however, given regex power, we would like to evaluate which library could be introduced and how would be the best way to do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2495) Evaluate a suitable regular expressions library
[ https://issues.apache.org/jira/browse/MESOS-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rojas updated MESOS-2495: --- Issue Type: Wish (was: Bug) > Evaluate a suitable regular expressions library > --- > > Key: MESOS-2495 > URL: https://issues.apache.org/jira/browse/MESOS-2495 > Project: Mesos > Issue Type: Wish >Reporter: Alexander Rojas > > There are a couple of situations where regular expressions would be an easy > solution within mesos (i.e. disabling endpoints). So far no regex library has > been introduced in order to avoid binary dependencies; however, given regex > power, we would like to evaluate which library could be introduced and how > would be the best way to do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2494) Clang build broken with "expression result unused" warning
[
https://issues.apache.org/jira/browse/MESOS-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360200#comment-14360200
]
Alexander Rojas commented on MESOS-2494:
https://reviews.apache.org/r/32034/
> Clang build broken with "expression result unused" warning
> --
>
> Key: MESOS-2494
> URL: https://issues.apache.org/jira/browse/MESOS-2494
> Project: Mesos
> Issue Type: Bug
>Reporter: Alexander Rojas
>Assignee: Alexander Rojas
>
> Commit 8385bba added code which thoroughly compares protobuf messages,
> however one of the changes looks like:
> {code}
> return left.task_id() == right.task_id(); // This semicolon shouldn't be
> here.
> left.state() == right.state() &&
> left.data() == right.data() &&
> left.message() == right.message() &&
> left.slave_id() == right.slave_id() &&
> left.timestamp() == right.timestamp() &&
> left.executor_id() == right.executor_id() &&
> left.healthy() == right.healthy() &&
> left.source() == right.source() &&
> left.reason() == right.reason() &&
> left.uuid() == right.uuid();
> {code}
> which results to clang build's failing with "expression result unused." Not
> to mention the given code has a bug in itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2494) Clang build broken with "expression result unused" warning
[
https://issues.apache.org/jira/browse/MESOS-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas updated MESOS-2494:
---
Shepherd: Till Toenshoff
> Clang build broken with "expression result unused" warning
> --
>
> Key: MESOS-2494
> URL: https://issues.apache.org/jira/browse/MESOS-2494
> Project: Mesos
> Issue Type: Bug
>Reporter: Alexander Rojas
>Assignee: Alexander Rojas
>
> Commit 8385bba added code which thoroughly compares protobuf messages,
> however one of the changes looks like:
> {code}
> return left.task_id() == right.task_id(); // This semicolon shouldn't be
> here.
> left.state() == right.state() &&
> left.data() == right.data() &&
> left.message() == right.message() &&
> left.slave_id() == right.slave_id() &&
> left.timestamp() == right.timestamp() &&
> left.executor_id() == right.executor_id() &&
> left.healthy() == right.healthy() &&
> left.source() == right.source() &&
> left.reason() == right.reason() &&
> left.uuid() == right.uuid();
> {code}
> which results to clang build's failing with "expression result unused." Not
> to mention the given code has a bug in itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-2494) Clang build broken with "expression result unused" warning
Alexander Rojas created MESOS-2494:
--
Summary: Clang build broken with "expression result unused" warning
Key: MESOS-2494
URL: https://issues.apache.org/jira/browse/MESOS-2494
Project: Mesos
Issue Type: Bug
Reporter: Alexander Rojas
Commit 8385bba added code which thoroughly compares protobuf messages, however
one of the changes looks like:
{code}
return left.task_id() == right.task_id(); // This semicolon shouldn't be here.
left.state() == right.state() &&
left.data() == right.data() &&
left.message() == right.message() &&
left.slave_id() == right.slave_id() &&
left.timestamp() == right.timestamp() &&
left.executor_id() == right.executor_id() &&
left.healthy() == right.healthy() &&
left.source() == right.source() &&
left.reason() == right.reason() &&
left.uuid() == right.uuid();
{code}
which results to clang build's failing with "expression result unused." Not to
mention the given code has a bug in itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-2494) Clang build broken with "expression result unused" warning
[
https://issues.apache.org/jira/browse/MESOS-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas reassigned MESOS-2494:
--
Assignee: Alexander Rojas
> Clang build broken with "expression result unused" warning
> --
>
> Key: MESOS-2494
> URL: https://issues.apache.org/jira/browse/MESOS-2494
> Project: Mesos
> Issue Type: Bug
>Reporter: Alexander Rojas
>Assignee: Alexander Rojas
>
> Commit 8385bba added code which thoroughly compares protobuf messages,
> however one of the changes looks like:
> {code}
> return left.task_id() == right.task_id(); // This semicolon shouldn't be
> here.
> left.state() == right.state() &&
> left.data() == right.data() &&
> left.message() == right.message() &&
> left.slave_id() == right.slave_id() &&
> left.timestamp() == right.timestamp() &&
> left.executor_id() == right.executor_id() &&
> left.healthy() == right.healthy() &&
> left.source() == right.source() &&
> left.reason() == right.reason() &&
> left.uuid() == right.uuid();
> {code}
> which results to clang build's failing with "expression result unused." Not
> to mention the given code has a bug in itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2191) Add ContainerId to the TaskStatus message
[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas updated MESOS-2191:
---
Description:
{{TaskStatus}} provides the frameworks with certain information
({{executorId}}, {{slaveId}}, etc.) which is useful when collecting statistics
about cluster performance; however, it is difficult to associate tasks to the
container it is executed since this information stays always within mesos
itself. Therefore it would be good to provide the framework scheduler with this
information, adding a new field in the {{TaskStatus}} message.
See comments for a use case.
was:ContainerId should be returned to the Framework as part of the
StatusMessage
> Add ContainerId to the TaskStatus message
> -
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
>Reporter: Marcel Neuhausler
>Assignee: Alexander Rojas
> Labels: mesosphere
>
> {{TaskStatus}} provides the frameworks with certain information
> ({{executorId}}, {{slaveId}}, etc.) which is useful when collecting
> statistics about cluster performance; however, it is difficult to associate
> tasks to the container it is executed since this information stays always
> within mesos itself. Therefore it would be good to provide the framework
> scheduler with this information, adding a new field in the {{TaskStatus}}
> message.
> See comments for a use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2191) Add ContainerId to the TaskStatus message
[ https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rojas updated MESOS-2191: --- Summary: Add ContainerId to the TaskStatus message (was: Add ContainerId into StatusMessage) > Add ContainerId to the TaskStatus message > - > > Key: MESOS-2191 > URL: https://issues.apache.org/jira/browse/MESOS-2191 > Project: Mesos > Issue Type: Wish > Components: containerization >Reporter: Marcel Neuhausler >Assignee: Alexander Rojas > Labels: mesosphere > > ContainerId should be returned to the Framework as part of the StatusMessage -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2216) The "configure" phase breaks with the IBM JVM.
[ https://issues.apache.org/jira/browse/MESOS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360138#comment-14360138 ] Tony Reix commented on MESOS-2216: -- I've had a look at Hadoop-9435 . And I do not see any link about their solution to the code of Mesos. And I've no skills about Mesos internals. Only porting it. So, when do you plan to try building Mesos with the IBM JVM and to fix this blocking issue ? > The "configure" phase breaks with the IBM JVM. > -- > > Key: MESOS-2216 > URL: https://issues.apache.org/jira/browse/MESOS-2216 > Project: Mesos > Issue Type: Bug >Affects Versions: 1.0.0, 0.20.1 > Environment: Ubuntu / x86_64 >Reporter: Tony Reix >Priority: Blocker > > ./configure does not work with IBM JVM, since it looks for a directory: >/usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server x86_64 >/usr/lib/jvm/ibm-java-ppc64le-71/jre/lib/ppc64le/serverPPC64 LE > that does not exist for the IBM JVM. > Though this directory does exist for Oracle JVM and Open JDK: >/usr/lib/jvm/jdk1.7.0_71/jre/lib/amd64/server Oracle JVM >/usr/lib/jvm/java-1.7.0-openjdk-amd64/jre/lib/amd64/server OpenJDK > However, the files: > libjsig.so > libjvm.so (3 versions) > do exist for IBM JVM. > Anyway, creating the server directory and copying the files (tried with the 3 > versions of libjvm.so) does not fix the issue: > checking whether or not we can build with JNI... > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlopen' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlclose' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlerror' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dlsym' > /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined > reference to `dladdr' > Something (dlopen, dlclose, dlerror, dlsym, dladdr) is missing in IBM JVM. > So, either the configure step relies on a feature that is not in the Java > standard but only in the Oracle JVM and OpenJDK, or the IBM JVM lacks part of > the Java standard. > I'm not an expert about this. So, I'd like Mesos people to experiment with > IBM JVM. Maybe there is another solution for this step of the Mesos configure > that would work with all 3 JVMs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2493) google glog link is incorrect
haosdent created MESOS-2493: --- Summary: google glog link is incorrect Key: MESOS-2493 URL: https://issues.apache.org/jira/browse/MESOS-2493 Project: Mesos Issue Type: Bug Components: documentation Reporter: haosdent Priority: Minor In this page: http://mesos.apache.org/documentation/latest/logging-and-debugging/. The link of "Google Logging library" is incorrect. "http://mesos.apache.org/documentation/latest/http://code.google.com/p/google-glog"; ==> "http://code.google.com/p/google-glog"; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2205) Add user documentation for reservations
[
https://issues.apache.org/jira/browse/MESOS-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360103#comment-14360103
]
Nikita Vetoshkin commented on MESOS-2205:
-
Other codes that come to mind are:
* {{400 Bad Request}} for invalid arguments.
* {{412 Precondition Failed}}
I think that {{409 Conflict}} should be used for something like concurrent
update issue, when someone already modified item you wish to update. Mesos
example that comes to mind is attempt to {{launchTasks}} with optimistic offers.
I like the way errors are specified in grpc, e.g. here is [Java
version|https://github.com/grpc/grpc-java/blob/master/core/src/main/java/io/grpc/Status.java#L130].
In our case we are interested in {{INVALID_ARGUMENT}}, {{FAILED_PRECONDITION}}
and {{OUT_OF_RANGE}}.
Anyway, HTTP codes are not strict and can be argued about which to choose.
Specifying which code was chosen for which case is a must :)
> Add user documentation for reservations
> ---
>
> Key: MESOS-2205
> URL: https://issues.apache.org/jira/browse/MESOS-2205
> Project: Mesos
> Issue Type: Documentation
> Components: documentation, framework
>Reporter: Michael Park
>Assignee: Michael Park
> Labels: mesosphere
>
> Add a user guide for reservations which describes basic usage of them, how
> ACLs are used to specify who can unreserve whose resources, and few advanced
> usage cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-2492) Enable the allocator to account for framework reservations in the sorter
Michael Park created MESOS-2492: --- Summary: Enable the allocator to account for framework reservations in the sorter Key: MESOS-2492 URL: https://issues.apache.org/jira/browse/MESOS-2492 Project: Mesos Issue Type: Task Components: allocation Reporter: Michael Park Assignee: Michael Park h3. Goal This is the subsequent task in relation to [MESOS-2490|https://issues.apache.org/jira/browse/MESOS-2490] which enables the allocator to distinguish between role reservations and framework reservations. For allocation purposes, framework reservations are modeled after a long-running task using unreserved resources. * LaunchTask -> Takes resources away from the unreserved pool -> RecoverResources * Reserve -> Takes resources away from the unreserved pool -> Unreserve The goal of this task is to teach the hierarchical allocator how to account for framework reservations in this way. h3. Expected Outcome * The allocator should be able to account for framework reservations in a way that it affects the framework's allocation share in terms of DRF. This will help enforce fair allocation of the unreserved resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-2490) Enable the allocator to distinguish between role and framework reservations
[ https://issues.apache.org/jira/browse/MESOS-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park reassigned MESOS-2490: --- Assignee: Michael Park > Enable the allocator to distinguish between role and framework reservations > --- > > Key: MESOS-2490 > URL: https://issues.apache.org/jira/browse/MESOS-2490 > Project: Mesos > Issue Type: Task > Components: allocation >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere > > h3. Goal > This is the subsequent task after > [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489] which enables a > framework to send back a reservation offer operation to reserve resources for > its role. The goal for this ticket is to teach the allocator to distinguish > between a role reservation and framework reservation. Note in particular that > this means updating the sorter is out of scope of this task. The goal is > strictly to teach the allocator how to send offers to a particular framework > rather than a role. > h3. Expected Outcome > * The framework can send back reservation operations to (un)reserve resources > for itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2491) Persist the reservation state on the slave
Michael Park created MESOS-2491:
---
Summary: Persist the reservation state on the slave
Key: MESOS-2491
URL: https://issues.apache.org/jira/browse/MESOS-2491
Project: Mesos
Issue Type: Task
Components: master, slave
Reporter: Michael Park
Assignee: Michael Park
h3. Goal
The goal for this task is to persist the reservation state stored on the master
on the corresponding slave. The {{needCheckpointing}} predicate is used to
capture the condition for which a resource needs to be checkpointed. Currently
the only condition is {{isPersistentVolume}}. We'll update this to include
dynamically reserved resources.
h3. Expected Outcome
* The dynamically reserved resources will be persisted on the slave.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2490) Enable the allocator to distinguish between role and framework reservations
[ https://issues.apache.org/jira/browse/MESOS-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park updated MESOS-2490: Description: h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489] which enables a framework to send back a reservation offer operation to reserve resources for a its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. Note in particular that this means updating the sorter is out of scope of this task. The goal is strictly to teach the allocator how to send offers to a particular framework rather than a role. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. was: h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489]. MESOS-2489 enables a framework to send back a reservation offer operation to reserve resources for a its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. Note in particular that this means updating the sorter is out of scope of this task. The goal is strictly to teach the allocator how to send offers to a particular framework rather than a role. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. > Enable the allocator to distinguish between role and framework reservations > --- > > Key: MESOS-2490 > URL: https://issues.apache.org/jira/browse/MESOS-2490 > Project: Mesos > Issue Type: Task > Components: allocation >Reporter: Michael Park > Labels: mesosphere > > h3. Goal > This is the subsequent task after > [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489] which enables a > framework to send back a reservation offer operation to reserve resources for > a its role. The goal for this ticket is to teach the allocator to distinguish > between a role reservation and framework reservation. Note in particular that > this means updating the sorter is out of scope of this task. The goal is > strictly to teach the allocator how to send offers to a particular framework > rather than a role. > h3. Expected Outcome > * The framework can send back reservation operations to (un)reserve resources > for itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2490) Enable the allocator to distinguish between role and framework reservations
[ https://issues.apache.org/jira/browse/MESOS-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park updated MESOS-2490: Description: h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489] which enables a framework to send back a reservation offer operation to reserve resources for its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. Note in particular that this means updating the sorter is out of scope of this task. The goal is strictly to teach the allocator how to send offers to a particular framework rather than a role. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. was: h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489] which enables a framework to send back a reservation offer operation to reserve resources for a its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. Note in particular that this means updating the sorter is out of scope of this task. The goal is strictly to teach the allocator how to send offers to a particular framework rather than a role. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. > Enable the allocator to distinguish between role and framework reservations > --- > > Key: MESOS-2490 > URL: https://issues.apache.org/jira/browse/MESOS-2490 > Project: Mesos > Issue Type: Task > Components: allocation >Reporter: Michael Park > Labels: mesosphere > > h3. Goal > This is the subsequent task after > [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489] which enables a > framework to send back a reservation offer operation to reserve resources for > its role. The goal for this ticket is to teach the allocator to distinguish > between a role reservation and framework reservation. Note in particular that > this means updating the sorter is out of scope of this task. The goal is > strictly to teach the allocator how to send offers to a particular framework > rather than a role. > h3. Expected Outcome > * The framework can send back reservation operations to (un)reserve resources > for itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2490) Enable the allocator to distinguish between role and framework reservations
[ https://issues.apache.org/jira/browse/MESOS-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park updated MESOS-2490: Description: h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489]. MESOS-2489 enables a framework to send back a reservation offer operation to reserve resources for a its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. Note in particular that this means updating the sorter is out of scope of this task. The goal is strictly to teach the allocator how to send offers to a particular framework rather than a role. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. was: h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489]. MESOS-2489 enables a framework to send back a reservation offer operation to reserve resources for a its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. > Enable the allocator to distinguish between role and framework reservations > --- > > Key: MESOS-2490 > URL: https://issues.apache.org/jira/browse/MESOS-2490 > Project: Mesos > Issue Type: Task > Components: allocation >Reporter: Michael Park > Labels: mesosphere > > h3. Goal > This is the subsequent task after > [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489]. MESOS-2489 > enables a framework to send back a reservation offer operation to reserve > resources for a its role. The goal for this ticket is to teach the allocator > to distinguish between a role reservation and framework reservation. Note in > particular that this means updating the sorter is out of scope of this task. > The goal is strictly to teach the allocator how to send offers to a > particular framework rather than a role. > h3. Expected Outcome > * The framework can send back reservation operations to (un)reserve resources > for itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-2490) Enable the allocator to distinguish between role and framework reservations
Michael Park created MESOS-2490: --- Summary: Enable the allocator to distinguish between role and framework reservations Key: MESOS-2490 URL: https://issues.apache.org/jira/browse/MESOS-2490 Project: Mesos Issue Type: Task Components: allocation Reporter: Michael Park h3. Goal This is the subsequent task after [MESOS-2489|https://issues.apache.org/jira/browse/MESOS-2489]. MESOS-2489 enables a framework to send back a reservation offer operation to reserve resources for a its role. The goal for this ticket is to teach the allocator to distinguish between a role reservation and framework reservation. h3. Expected Outcome * The framework can send back reservation operations to (un)reserve resources for itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2139) Enable the master to handle reservation operations
[
https://issues.apache.org/jira/browse/MESOS-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-2139:
Issue Type: Technical task (was: Task)
Parent: MESOS-2489
> Enable the master to handle reservation operations
> --
>
> Key: MESOS-2139
> URL: https://issues.apache.org/jira/browse/MESOS-2139
> Project: Mesos
> Issue Type: Technical task
> Components: master
>Reporter: Michael Park
>Assignee: Michael Park
> Labels: mesosphere
>
> master's {{_accept}} function currently only handles {{Create}} and
> {{Destroy}} operations which exist for persistent volumes. We need to handle
> the {{Reserve}} and {{Unreserve}} operations for dynamic reservations as well.
> In addition, we need to add {{validate}} functions for the reservation
> operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2477) Enable Resources::apply to handle reservation operations.
[
https://issues.apache.org/jira/browse/MESOS-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-2477:
Issue Type: Technical task (was: Task)
Parent: MESOS-2489
> Enable Resources::apply to handle reservation operations.
> -
>
> Key: MESOS-2477
> URL: https://issues.apache.org/jira/browse/MESOS-2477
> Project: Mesos
> Issue Type: Technical task
>Reporter: Michael Park
>Assignee: Michael Park
> Labels: mesosphere
>
> {{Resources::apply}} currently only handles {{Create}} and {{Destroy}}
> operations which exist for persistent volumes. We need to handle the
> {{Reserve}} and {{Unreserve}} operations for dynamic reservations as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2475) Add the Resource::ReservationInfo protobuf message
[
https://issues.apache.org/jira/browse/MESOS-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-2475:
Issue Type: Technical task (was: Task)
Parent: MESOS-2489
> Add the Resource::ReservationInfo protobuf message
> --
>
> Key: MESOS-2475
> URL: https://issues.apache.org/jira/browse/MESOS-2475
> Project: Mesos
> Issue Type: Technical task
>Reporter: Michael Park
>Assignee: Michael Park
> Labels: mesosphere
>
> The {{Resource::ReservationInfo}} protobuf message encapsulates information
> needed to keep track of reservations. It's named {{ReservationInfo}} rather
> than {{Reservation}} to keep consistency with {{Resource::DiskInfo}}.
> Here's essentially what it will look like:
> {code}
> message ReservationInfo {
> // Anyone can set this ID at the time of reservation in order to keep track.
> optional string id;
> // If this is set, it means that the resource is reserved for this
> particular
> // framework. Otherwise, the resource is reserved for the role.
> optional FrameworkID framework_id;
> // Indicates the principal of the operator or framework that created the
> // reservation. This is used to determine whether this resource can be
> // unreserved by an operator or a framework by checking the
> // "unreserve" ACL.
> required string principal;
> }
> // If this is set, this resource was dynamically reserved by an operator or
> // a framework. Otherwise, this resource was static configured by an
> // operator via the --resources flag.
> optional ReservationInfo reservation;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2476) Enable Resources to handle Resource::ReservationInfo
[
https://issues.apache.org/jira/browse/MESOS-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-2476:
Issue Type: Technical task (was: Task)
Parent: MESOS-2489
> Enable Resources to handle Resource::ReservationInfo
>
>
> Key: MESOS-2476
> URL: https://issues.apache.org/jira/browse/MESOS-2476
> Project: Mesos
> Issue Type: Technical task
>Reporter: Michael Park
>Assignee: Michael Park
> Labels: mesosphere
>
> After [MESOS-2475|https://issues.apache.org/jira/browse/MESOS-2475], our C++
> {{Resources}} class needs to know how to handle {{Resource}} protobuf
> messages that have the {{reservation}} field set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-2489) Enable a framework to perform reservation operations.
Michael Park created MESOS-2489:
---
Summary: Enable a framework to perform reservation operations.
Key: MESOS-2489
URL: https://issues.apache.org/jira/browse/MESOS-2489
Project: Mesos
Issue Type: Task
Components: master
Reporter: Michael Park
Assignee: Michael Park
h3. Goal
This is the first step to supporting dynamic reservations. The goal of this
task is to enable a framework to reply to a resource offer with *Reserve* and
*Unreserve* offer operations as defined by {{Offer::Operation}} in
{{mesos.proto}}.
h3. Overview
It's divided into a few subtasks so that it's clear what the small chunks to be
addressed are. In summary, we need to introduce the
{{Resource::ReservationInfo}} protobuf message to encapsulate the reservation
information, enable the C++ {{Resources}} class to handle it then enable the
master to handle reservation operations.
h3. Expected Outcome
* The framework will be able to send back reservation operations to (un)reserve
resources.
* The reservations are kept only in the master since we don't send the
{{CheckpointResources}} message to checkpoint the reservations on the slave yet.
* The reservations are considered to be reserved for the framework's role.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MESOS-2137) Add ReservationType protobuf message
[ https://issues.apache.org/jira/browse/MESOS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park closed MESOS-2137. --- Resolution: Won't Fix > Add ReservationType protobuf message > > > Key: MESOS-2137 > URL: https://issues.apache.org/jira/browse/MESOS-2137 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere, protobuf > > With the introduction of dynamic reservations, resources can be under one of > 2 reservation types: STATIC and DYNAMIC. We need to add a ReservationType to > the Resource protobuf in order to introduce this notion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MESOS-2137) Add ReservationType protobuf message
[ https://issues.apache.org/jira/browse/MESOS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park reopened MESOS-2137: - > Add ReservationType protobuf message > > > Key: MESOS-2137 > URL: https://issues.apache.org/jira/browse/MESOS-2137 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere, protobuf > > With the introduction of dynamic reservations, resources can be under one of > 2 reservation types: STATIC and DYNAMIC. We need to add a ReservationType to > the Resource protobuf in order to introduce this notion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MESOS-2137) Add ReservationType protobuf message
[ https://issues.apache.org/jira/browse/MESOS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park closed MESOS-2137. --- Resolution: Fixed > Add ReservationType protobuf message > > > Key: MESOS-2137 > URL: https://issues.apache.org/jira/browse/MESOS-2137 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere, protobuf > > With the introduction of dynamic reservations, resources can be under one of > 2 reservation types: STATIC and DYNAMIC. We need to add a ReservationType to > the Resource protobuf in order to introduce this notion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MESOS-2137) Add ReservationType protobuf message
[ https://issues.apache.org/jira/browse/MESOS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park closed MESOS-2137. --- Resolution: Won't Fix > Add ReservationType protobuf message > > > Key: MESOS-2137 > URL: https://issues.apache.org/jira/browse/MESOS-2137 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere, protobuf > > With the introduction of dynamic reservations, resources can be under one of > 2 reservation types: STATIC and DYNAMIC. We need to add a ReservationType to > the Resource protobuf in order to introduce this notion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MESOS-2137) Add ReservationType protobuf message
[ https://issues.apache.org/jira/browse/MESOS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park reopened MESOS-2137: - > Add ReservationType protobuf message > > > Key: MESOS-2137 > URL: https://issues.apache.org/jira/browse/MESOS-2137 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere, protobuf > > With the introduction of dynamic reservations, resources can be under one of > 2 reservation types: STATIC and DYNAMIC. We need to add a ReservationType to > the Resource protobuf in order to introduce this notion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MESOS-2137) Add ReservationType protobuf message
[ https://issues.apache.org/jira/browse/MESOS-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park reopened MESOS-2137: - > Add ReservationType protobuf message > > > Key: MESOS-2137 > URL: https://issues.apache.org/jira/browse/MESOS-2137 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Michael Park > Labels: mesosphere, protobuf > > With the introduction of dynamic reservations, resources can be under one of > 2 reservation types: STATIC and DYNAMIC. We need to add a ReservationType to > the Resource protobuf in order to introduce this notion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MESOS-2141) Introduce an explicit Reserve message.
[ https://issues.apache.org/jira/browse/MESOS-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park closed MESOS-2141. --- Resolution: Won't Fix > Introduce an explicit Reserve message. > -- > > Key: MESOS-2141 > URL: https://issues.apache.org/jira/browse/MESOS-2141 > Project: Mesos > Issue Type: Task >Reporter: Michael Park > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (MESOS-2141) Introduce an explicit Reserve message.
[ https://issues.apache.org/jira/browse/MESOS-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park reopened MESOS-2141: - > Introduce an explicit Reserve message. > -- > > Key: MESOS-2141 > URL: https://issues.apache.org/jira/browse/MESOS-2141 > Project: Mesos > Issue Type: Task >Reporter: Michael Park > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
