[jira] [Commented] (MESOS-3155) Add a containerizer and executor that simulate the launching of tasks.
[
https://issues.apache.org/jira/browse/MESOS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646346#comment-14646346
]
James Peach commented on MESOS-3155:
The implementation we discussed was a (system) process that creates {{N}}
libprocess processes, each of which registers as an independent slave. This
would mean you can run a single command and generate {{N}} slaves (which
publish an arbitrary resources). These null slaves don't need to actually run
the tasks, they just need to correctly allocate resources. There are enough
fields in the {{TaskInfo}} that you can designate specific triggers for how the
virtual task should behave (e.g. you could use the {{Environment}} for this).
The null slaves can introspect this information to make tasks fail, succeed
after specific timeouts, etc.
In principle, we would like to be able to use the null slave with our internal
scheduler, but we haven't figured out how to deal with the task image in that
context yet. Maybe it won't turn out to be much of a problem.
Add a containerizer and executor that simulate the launching of tasks.
---
Key: MESOS-3155
URL: https://issues.apache.org/jira/browse/MESOS-3155
Project: Mesos
Issue Type: Improvement
Components: containerization, slave
Reporter: Cody Roseborough
Assignee: Cody Roseborough
Priority: Minor
The Simulator Containerizer (SC) is a containerizer that can be used in
conjunction with mesos-local to exercise frameworks at a large scale without
launching a large cluster. The SC launches a fake executor instead of the
one specified by the tasks, in order to avoid using actual resources. The SC
provides normal tasks updates as well as configurable task options via a
configuration JSON file.
Some of the options available for configuration might be length or failure
rate.
Other points of contact for this are: [~lukeleslie], [~derekchiang]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3172) Getting Started docs still mentions about v0.22.1
[ https://issues.apache.org/jira/browse/MESOS-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646463#comment-14646463 ] haosdent commented on MESOS-3172: - (￣▽￣) OK Getting Started docs still mentions about v0.22.1 - Key: MESOS-3172 URL: https://issues.apache.org/jira/browse/MESOS-3172 Project: Mesos Issue Type: Documentation Reporter: Ryuichi Okumura Assignee: Ryuichi Okumura Priority: Minor Mesos v0.23.0 seems to released, but the Getting Started docs still mentions about Mesos v0.22.1. See: http://mesos.apache.org/gettingstarted/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3172) Getting Started docs still mentions about v0.22.1
[
https://issues.apache.org/jira/browse/MESOS-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646433#comment-14646433
]
Marco Massenzio commented on MESOS-3172:
I'm not a great fan of Homebrew (but that's my personal opinion and I use it
anyway for things like wget and other minutiae).
Given that anyone installing Mesos on a OSX machine is doing so to do some form
of experimentation/development, I think a much better user experience can be
had using the tarballs/cloning the repos; as HB hides too many details and puts
stuff in unintuitive places.
Again, that's my personal opinion, and I'm sure there's lots of folk who will,
legitimately, disagree with me (hey, the world is awesome because it's varied!)
So, by all means, feel free to add that comment to the OSX section, I won't
stop you... but I won't be aiding and abetting it either :D
(but I would also recommend you don't just leave it at that, but explain where
stuff goes, to add {{/usr/sbin}} to {{PATH}}, that a config file apparently
goes in {{/etc/mesos}} or something, etc. etc. - just doing {{brew install
mesos}} is likely to disappoint).
Getting Started docs still mentions about v0.22.1
-
Key: MESOS-3172
URL: https://issues.apache.org/jira/browse/MESOS-3172
Project: Mesos
Issue Type: Documentation
Reporter: Ryuichi Okumura
Assignee: Ryuichi Okumura
Priority: Minor
Mesos v0.23.0 seems to released, but the Getting Started docs still
mentions about Mesos v0.22.1.
See: http://mesos.apache.org/gettingstarted/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-3173) Mark Path::basename, Path::dirname as const functions.
[ https://issues.apache.org/jira/browse/MESOS-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Toenshoff updated MESOS-3173: -- Comment: was deleted (was: https://reviews.apache.org/r/36773/) Mark Path::basename, Path::dirname as const functions. -- Key: MESOS-3173 URL: https://issues.apache.org/jira/browse/MESOS-3173 Project: Mesos Issue Type: Improvement Components: stout Reporter: Jan Schlicht Assignee: Jan Schlicht Priority: Trivial Labels: easyfix, mesosphere The functions Path::basename and Path::dirname in stout/path.hpp are not marked const, although they could. Marking them const would remove some ambiguities in the usage of these functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3168) MesosZooKeeperTest fixture can have side effects across tests
[ https://issues.apache.org/jira/browse/MESOS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646483#comment-14646483 ] Vinod Kone commented on MESOS-3168: --- Thanks [~haosd...@gmail.com] for the quick fix! commit e6e7d732cc54355a679951147c96e46609514aba Author: haosdent huang haosd...@gmail.com Date: Wed Jul 29 10:44:14 2015 -0700 Call parent SetUp() and TearDown() in MesosZooKeeperTest. Review: https://reviews.apache.org/r/36909 MesosZooKeeperTest fixture can have side effects across tests - Key: MESOS-3168 URL: https://issues.apache.org/jira/browse/MESOS-3168 Project: Mesos Issue Type: Bug Components: test Reporter: Vinod Kone Assignee: Vinod Kone Fix For: 0.24.0 MesosZooKeeperTest fixture doesn't restart the ZooKeeper server for each test. This means if a test shuts down the ZooKeeper server, the next test (using the same fixture) might fail. For an example see https://reviews.apache.org/r/36807/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-2497) Create synchronous validations for Calls
[
https://issues.apache.org/jira/browse/MESOS-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646727#comment-14646727
]
Benjamin Mahler commented on MESOS-2497:
The following pulls out the call validation logic:
{noformat}
commit d5cc1a606ca65821447daef378ee45e0da02864b
Author: Benjamin Mahler benjamin.mah...@gmail.com
Date: Wed Jul 29 12:22:10 2015 -0700
Pulled out call validation.
Review: https://reviews.apache.org/r/36919
{noformat}
Create synchronous validations for Calls
Key: MESOS-2497
URL: https://issues.apache.org/jira/browse/MESOS-2497
Project: Mesos
Issue Type: Bug
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-349) remove mounts when garbage collecting tasks
[
https://issues.apache.org/jira/browse/MESOS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646492#comment-14646492
]
Vinod Kone commented on MESOS-349:
--
[~jdef] added you as contributor. you should be able to reopen issues going
forward.
remove mounts when garbage collecting tasks
---
Key: MESOS-349
URL: https://issues.apache.org/jira/browse/MESOS-349
Project: Mesos
Issue Type: Improvement
Components: slave
Reporter: Jonathan Boulle
Priority: Minor
It would be extremely helpful if the GC process on a slave (which is
currently effectively just an {{rm -rf}}) could also remove mounts within the
executor sandbox.
This would allow sandboxes to incorporate mounts from different filesystems,
for example, or to utilise chroots (which require various mounts to function
properly - e.g. {{/proc}} and {{/sys}} on Linux) - and still be cleaned up by
the mesos slave without any external intervention.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3169) FrameworkInfo should only be updated if the re-registration is valid
[
https://issues.apache.org/jira/browse/MESOS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646489#comment-14646489
]
Anand Mazumdar commented on MESOS-3169:
---
The `FrameworkErrorMessage` generated from `failoverFramework` is sent to the
old scheduler. So , we should go ahead with updating the framework info
correctly for that case as we are doing now.
The only point of contention hence is this:
{code }else if (from != framework-pid); {code}
I guess the easiest fix would be to update the info at the end of the function
rather then at the beginning unless I am missing something ?
FrameworkInfo should only be updated if the re-registration is valid
Key: MESOS-3169
URL: https://issues.apache.org/jira/browse/MESOS-3169
Project: Mesos
Issue Type: Bug
Components: master
Affects Versions: 0.23.0
Reporter: Joris Van Remoortere
Labels: framework, master, mesosphere
See Ben Mahler's comment in https://reviews.apache.org/r/32961/
FrameworkInfo should not be updated if the re-registration is invalid. This
can happen in a few cases under the branching logic, so this requires some
refactoring.
Notice that a {code}FrameworkErrorMessage{code} can be generated both inside
{code}else if (from != framework-pid){code} as well as from inside
{code}failoverFramework(framework, from);{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3093) Support HTTPS requests in libprocess
[ https://issues.apache.org/jira/browse/MESOS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen updated MESOS-3093: Fix Version/s: 0.24.0 Support HTTPS requests in libprocess Key: MESOS-3093 URL: https://issues.apache.org/jira/browse/MESOS-3093 Project: Mesos Issue Type: Improvement Components: containerization, docker Reporter: Lily Chen Assignee: Jojy Varghese Labels: mesosphere Fix For: 0.24.0 In order to pull images from Docker registries, https calls are needed to securely communicate with the registry hosts. Currently, only http requests are supported through libprocess. Now that SSL sockets are available through libprocess, support for https can be added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3073) Introduce HTTP endpoints for Quota
[
https://issues.apache.org/jira/browse/MESOS-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-3073:
-
Description:
We need to implement the HTTP endpoints for Quota as outlined in the Design
Doc:
(https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I).
This also includes validating quota requests in terms of syntax correctness,
updating Master bookkeeping structures, persisting quota requests in the
{{Registry}}.
was:
We need to implement the HTTP endpoints for Quota as outlined in the Design
Doc:(https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I).
This also includes validating quota requests in terms of syntax correctness,
updating Master bookkeeping structures, persisting quota requests in the
{{Registry}}.
Introduce HTTP endpoints for Quota
--
Key: MESOS-3073
URL: https://issues.apache.org/jira/browse/MESOS-3073
Project: Mesos
Issue Type: Improvement
Reporter: Joerg Schad
Assignee: Joerg Schad
Labels: mesosphere
We need to implement the HTTP endpoints for Quota as outlined in the Design
Doc:
(https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I).
This also includes validating quota requests in terms of syntax correctness,
updating Master bookkeeping structures, persisting quota requests in the
{{Registry}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3169) FrameworkInfo should only be updated if the re-registration is valid
[
https://issues.apache.org/jira/browse/MESOS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646489#comment-14646489
]
Anand Mazumdar edited comment on MESOS-3169 at 7/29/15 5:48 PM:
The `FrameworkErrorMessage` generated from `failoverFramework` is sent to the
old scheduler. So , we should go ahead with updating the framework info
correctly for that case as we are doing now.
The only point of contention hence is this:
{code}else if (from != framework-pid); {code}
I guess the easiest fix would be to update the info at the end of the function
rather then at the beginning unless I am missing something ?
was (Author: anandmazumdar):
The `FrameworkErrorMessage` generated from `failoverFramework` is sent to the
old scheduler. So , we should go ahead with updating the framework info
correctly for that case as we are doing now.
The only point of contention hence is this:
{code }else if (from != framework-pid); {code}
I guess the easiest fix would be to update the info at the end of the function
rather then at the beginning unless I am missing something ?
FrameworkInfo should only be updated if the re-registration is valid
Key: MESOS-3169
URL: https://issues.apache.org/jira/browse/MESOS-3169
Project: Mesos
Issue Type: Bug
Components: master
Affects Versions: 0.23.0
Reporter: Joris Van Remoortere
Labels: framework, master, mesosphere
See Ben Mahler's comment in https://reviews.apache.org/r/32961/
FrameworkInfo should not be updated if the re-registration is invalid. This
can happen in a few cases under the branching logic, so this requires some
refactoring.
Notice that a {code}FrameworkErrorMessage{code} can be generated both inside
{code}else if (from != framework-pid){code} as well as from inside
{code}failoverFramework(framework, from);{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3093) Support HTTPS requests in libprocess
[ https://issues.apache.org/jira/browse/MESOS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646494#comment-14646494 ] Timothy Chen commented on MESOS-3093: - commit 5b183ee215847cdb4a5121bedf9af0952426cef7 Author: Jojy Varghese j...@mesosphere.io Date: Tue Jul 28 12:00:18 2015 -0700 Added https support in libprocess. Current http implementation lacks a https interface. This change exposes SSL socket for https URL scheme. Review: https://reviews.apache.org/r/36757 Support HTTPS requests in libprocess Key: MESOS-3093 URL: https://issues.apache.org/jira/browse/MESOS-3093 Project: Mesos Issue Type: Improvement Components: containerization, docker Reporter: Lily Chen Assignee: Jojy Varghese Labels: mesosphere In order to pull images from Docker registries, https calls are needed to securely communicate with the registry hosts. Currently, only http requests are supported through libprocess. Now that SSL sockets are available through libprocess, support for https can be added. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3155) Add a containerizer and executor that simulate the launching of tasks.
[ https://issues.apache.org/jira/browse/MESOS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646697#comment-14646697 ] Derek Chiang commented on MESOS-3155: - [~jamespeach] Our approach is extremely similar. We will post the design doc up here very soon, but basically we leverage mesos-local such that each slave runs in a libprocess process. Parameters like task length and failure rate are specified by a configuration file. Add a containerizer and executor that simulate the launching of tasks. --- Key: MESOS-3155 URL: https://issues.apache.org/jira/browse/MESOS-3155 Project: Mesos Issue Type: Improvement Components: containerization, slave Reporter: Cody Roseborough Assignee: Cody Roseborough Priority: Minor The Simulator Containerizer (SC) is a containerizer that can be used in conjunction with mesos-local to exercise frameworks at a large scale without launching a large cluster. The SC launches a fake executor instead of the one specified by the tasks, in order to avoid using actual resources. The SC provides normal tasks updates as well as configurable task options via a configuration JSON file. Some of the options available for configuration might be length or failure rate. Other points of contact for this are: [~lukeleslie], [~derekchiang] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-3120) Remove pthread specific code from Mesos
[
https://issues.apache.org/jira/browse/MESOS-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641172#comment-14641172
]
Benjamin Hindman edited comment on MESOS-3120 at 7/29/15 10:45 PM:
---
{noformat}
commit 8727301d3c00a8f93b32a36737d5244307ea3834
Author: Joris Van Remoortere joris.van.remoort...@gmail.com
Date: Wed Jul 29 15:45:03 2015 -0700
Used std::thread instead of pthread for Long Lived Executor.
Review: https://reviews.apache.org/r/36822
commit 42257809b5cee7d9c0e1b660f63a7cad0413d9ac
Author: Joris Van Remoortere joris.van.remoort...@gmail.com
Date: Fri Jul 24 14:36:06 2015 -0700
Removed pthread from Zookeeper test helper.
Review: https://reviews.apache.org/r/36676
commit 4fc8089bbefda0fbc640da6ecf0be37020e9f680
Author: Joris Van Remoortere joris.van.remoort...@gmail.com
Date: Fri Jul 24 14:35:12 2015 -0700
Removed pthread and used Latch in executor and scheduler drivers.
Review: https://reviews.apache.org/r/36674
{noformat}
was (Author: benjaminhindman):
{noformat}
commit 42257809b5cee7d9c0e1b660f63a7cad0413d9ac
Author: Joris Van Remoortere joris.van.remoort...@gmail.com
Date: Fri Jul 24 14:36:06 2015 -0700
Removed pthread from Zookeeper test helper.
Review: https://reviews.apache.org/r/36676
commit 4fc8089bbefda0fbc640da6ecf0be37020e9f680
Author: Joris Van Remoortere joris.van.remoort...@gmail.com
Date: Fri Jul 24 14:35:12 2015 -0700
Removed pthread and used Latch in executor and scheduler drivers.
Review: https://reviews.apache.org/r/36674
{noformat}
Remove pthread specific code from Mesos
---
Key: MESOS-3120
URL: https://issues.apache.org/jira/browse/MESOS-3120
Project: Mesos
Issue Type: Improvement
Components: libprocess
Reporter: Joris Van Remoortere
Assignee: Joris Van Remoortere
Labels: mesosphere, windows
Fix For: 0.24.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3155) Add a containerizer and executor that simulate the launching of tasks.
[ https://issues.apache.org/jira/browse/MESOS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Roseborough updated MESOS-3155: Description: The Simulator Containerizer (SC) is a containerizer that can be used in conjunction with mesos-local to exercise frameworks at a large scale without launching a large cluster. The SC launches a fake executor instead of the one specified by the tasks, in order to avoid using actual resources. The SC provides normal tasks updates as well as configurable task options via a configuration JSON file. Some of the options available for configuration might be length or failure rate. A Design doc that is a work in progress is [here|https://docs.google.com/document/d/1Ygq9MPWrqcQLf0J-mraVeEIRYk3xNXXQ0xRHFqTiXsQ/edit?usp=sharing] Other points of contact for this are: [~lukeleslie], [~derekchiang] was: The Simulator Containerizer (SC) is a containerizer that can be used in conjunction with mesos-local to exercise frameworks at a large scale without launching a large cluster. The SC launches a fake executor instead of the one specified by the tasks, in order to avoid using actual resources. The SC provides normal tasks updates as well as configurable task options via a configuration JSON file. Some of the options available for configuration might be length or failure rate. Other points of contact for this are: [~lukeleslie], [~derekchiang] Add a containerizer and executor that simulate the launching of tasks. --- Key: MESOS-3155 URL: https://issues.apache.org/jira/browse/MESOS-3155 Project: Mesos Issue Type: Improvement Components: containerization, slave Reporter: Cody Roseborough Assignee: Cody Roseborough Priority: Minor The Simulator Containerizer (SC) is a containerizer that can be used in conjunction with mesos-local to exercise frameworks at a large scale without launching a large cluster. The SC launches a fake executor instead of the one specified by the tasks, in order to avoid using actual resources. The SC provides normal tasks updates as well as configurable task options via a configuration JSON file. Some of the options available for configuration might be length or failure rate. A Design doc that is a work in progress is [here|https://docs.google.com/document/d/1Ygq9MPWrqcQLf0J-mraVeEIRYk3xNXXQ0xRHFqTiXsQ/edit?usp=sharing] Other points of contact for this are: [~lukeleslie], [~derekchiang] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2697) Add a /teardown endpoint on master to teardown a framework
[ https://issues.apache.org/jira/browse/MESOS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schad updated MESOS-2697: --- Description: We plan to rename /shutdown endpoint to /teardown to be compatible with the new API. /shutdown will be deprecated in 0.23.0 or later. (was: We plan to rename /shutdown endpoint to /teardown to be compatible with the new API. /shutdown will be deprecated in 0.24.0 or later.) Add a /teardown endpoint on master to teardown a framework -- Key: MESOS-2697 URL: https://issues.apache.org/jira/browse/MESOS-2697 Project: Mesos Issue Type: Task Reporter: Vinod Kone Assignee: Vinod Kone Fix For: 0.23.0 We plan to rename /shutdown endpoint to /teardown to be compatible with the new API. /shutdown will be deprecated in 0.23.0 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3164) Introduce QuotaInfo message
[
https://issues.apache.org/jira/browse/MESOS-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Schad reassigned MESOS-3164:
--
Assignee: Joerg Schad
Introduce QuotaInfo message
---
Key: MESOS-3164
URL: https://issues.apache.org/jira/browse/MESOS-3164
Project: Mesos
Issue Type: Task
Components: master
Reporter: Alexander Rukletsov
Assignee: Joerg Schad
Labels: mesosphere
A {{QuotaInfo}} protobuf message is internal representation for quota related
information (e.g. for persisting quota). The protobuf message should be
extendable for future needs and allows for easy aggregation across roles and
operator principals. It may also be used to pass quota information to
allocators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3164) Introduce QuotaInfo message
[
https://issues.apache.org/jira/browse/MESOS-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645844#comment-14645844
]
Joerg Schad commented on MESOS-3164:
Review Chain
Contributor: [~js84]
Reviewer 1: [~alex-mesos]
Reviwer 2: [~tillt]
Committer: [~benjaminhindman]
Introduce QuotaInfo message
---
Key: MESOS-3164
URL: https://issues.apache.org/jira/browse/MESOS-3164
Project: Mesos
Issue Type: Task
Components: master
Reporter: Alexander Rukletsov
Assignee: Joerg Schad
Labels: mesosphere
A {{QuotaInfo}} protobuf message is internal representation for quota related
information (e.g. for persisting quota). The protobuf message should be
extendable for future needs and allows for easy aggregation across roles and
operator principals. It may also be used to pass quota information to
allocators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3168) MesosZooKeeperTest fixture can have side effects across tests
[
https://issues.apache.org/jira/browse/MESOS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645799#comment-14645799
]
haosdent commented on MESOS-3168:
-
This patch let the jenkins
[failed|https://builds.apache.org/job/Mesos/COMPILER=gcc,LABEL=docker%7C%7CHadoop,OS=centos:7/lastUnsuccessfulBuild/console].
Could you check it again? [~vinodkone]
{code}
ERROR: files left in build directory after distclean:
./src/master/replicated_log/09.log
./src/master/replicated_log/CURRENT
./src/master/replicated_log/LOG.old
./src/master/replicated_log/LOG
./src/master/replicated_log/LOCK
./src/master/replicated_log/MANIFEST-06
./src/master/replicated_log/11.sst
./src/credentials
make[1]: *** [distcleancheck] Error 1
make[1]: Leaving directory `/mesos/mesos-0.24.0/_build'
make: *** [distcheck] Error 1
{code}
MesosZooKeeperTest fixture can have side effects across tests
-
Key: MESOS-3168
URL: https://issues.apache.org/jira/browse/MESOS-3168
Project: Mesos
Issue Type: Bug
Components: test
Reporter: Vinod Kone
Assignee: Vinod Kone
Fix For: 0.24.0
MesosZooKeeperTest fixture doesn't restart the ZooKeeper server for each
test. This means if a test shuts down the ZooKeeper server, the next test
(using the same fixture) might fail.
For an example see https://reviews.apache.org/r/36807/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-3170) 0.23 Build fails when compiling against -lsasl2 which has been statically linked
Chris Heller created MESOS-3170: --- Summary: 0.23 Build fails when compiling against -lsasl2 which has been statically linked Key: MESOS-3170 URL: https://issues.apache.org/jira/browse/MESOS-3170 Project: Mesos Issue Type: Bug Components: build Affects Versions: 0.23.0 Reporter: Chris Heller Priority: Minor Fix For: 0.24.0 If the sasl library has been statically linked the check from CRAM-MD5 can fail, due to missing symbols. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3164) Introduce QuotaInfo message
[
https://issues.apache.org/jira/browse/MESOS-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-3164:
---
Sprint: Mesosphere Sprint 15
Introduce QuotaInfo message
---
Key: MESOS-3164
URL: https://issues.apache.org/jira/browse/MESOS-3164
Project: Mesos
Issue Type: Task
Components: master
Reporter: Alexander Rukletsov
Assignee: Joerg Schad
Labels: mesosphere
A {{QuotaInfo}} protobuf message is internal representation for quota related
information (e.g. for persisting quota). The protobuf message should be
extendable for future needs and allows for easy aggregation across roles and
operator principals. It may also be used to pass quota information to
allocators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-3171) Fetcher Tests use EXPECT while subsequent logic relies on the outcome.
Joerg Schad created MESOS-3171: -- Summary: Fetcher Tests use EXPECT while subsequent logic relies on the outcome. Key: MESOS-3171 URL: https://issues.apache.org/jira/browse/MESOS-3171 Project: Mesos Issue Type: Bug Reporter: Joerg Schad Assignee: Joerg Schad Priority: Minor The fetcher tests use EXPECT validation for critical measures (e.g. non-empty results) and the subsequent logic releis on this (i.e. by accessing the first element). In such cases we should use ASSERT/CHECK. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-349) remove mounts when garbage collecting tasks
[
https://issues.apache.org/jira/browse/MESOS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646230#comment-14646230
]
James DeFelice commented on MESOS-349:
--
I have a specific use case that doesn't appear to be solved by the file system
translator. The kubernetes-mesos framework schedules a single
kubelet-executor process that runs on a slave for all k8s-mesos tasks
(currently uses mesos containerizer). This kubelet proc creates mounts in
$sandbox/pods/volumes according to volumes delared in k8s pod specs. Many
different types of mount-types are supported by k8s volume plugins (e.g. nfs,
iscsi, bind, tmpfs). These mount points are passed to a 'docker run' invocation
so that k8s pods can see data in these mounted volume directories.
Running the kubelet in an isolated filesystem breaks this model because the
changes to the mount table of the kubelet-executor (running in an isolated
mount-ns) are not visible in the hosts's mount-ns (where docker is looking when
spinning up CT's).
There is no guaranteed way to clean up these mount points upon termination of
the kubelet-executor if the process terminates abnormally in some way. The
slave GC algorithm will remove the sandbox files but will not clean up the
mount points.
I'd like to re-open this issue for discussion but JIRA won't let me.
remove mounts when garbage collecting tasks
---
Key: MESOS-349
URL: https://issues.apache.org/jira/browse/MESOS-349
Project: Mesos
Issue Type: Improvement
Components: slave
Reporter: Jonathan Boulle
Priority: Minor
It would be extremely helpful if the GC process on a slave (which is
currently effectively just an {{rm -rf}}) could also remove mounts within the
executor sandbox.
This would allow sandboxes to incorporate mounts from different filesystems,
for example, or to utilise chroots (which require various mounts to function
properly - e.g. {{/proc}} and {{/sys}} on Linux) - and still be cleaned up by
the mesos slave without any external intervention.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3173) Mark Path::basename, Path::dirname as const functions.
[ https://issues.apache.org/jira/browse/MESOS-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646129#comment-14646129 ] Jan Schlicht commented on MESOS-3173: - https://reviews.apache.org/r/36914/ Mark Path::basename, Path::dirname as const functions. -- Key: MESOS-3173 URL: https://issues.apache.org/jira/browse/MESOS-3173 Project: Mesos Issue Type: Improvement Components: stout Reporter: Jan Schlicht Assignee: Jan Schlicht Priority: Trivial Labels: easyfix, mesosphere The functions Path::basename and Path::dirname in stout/path.hpp are not marked const, although they could. Marking them const would remove some ambiguities in the usage of these functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-3172) Getting Started docs still mentions about v0.22.1
Ryuichi Okumura created MESOS-3172: -- Summary: Getting Started docs still mentions about v0.22.1 Key: MESOS-3172 URL: https://issues.apache.org/jira/browse/MESOS-3172 Project: Mesos Issue Type: Documentation Reporter: Ryuichi Okumura Assignee: Ryuichi Okumura Priority: Minor Mesos v0.23.0 seems to released, but the Getting Started docs still mentions about Mesos v0.22.1. See: http://mesos.apache.org/gettingstarted/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3073) Introduce HTTP endpoints for Quota
[
https://issues.apache.org/jira/browse/MESOS-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646107#comment-14646107
]
Joerg Schad commented on MESOS-3073:
Review Chain:
Contributor: [~js84]
Reviewer: [~alex-mesos]
Committer: [~benjaminhindman]
Introduce HTTP endpoints for Quota
--
Key: MESOS-3073
URL: https://issues.apache.org/jira/browse/MESOS-3073
Project: Mesos
Issue Type: Improvement
Reporter: Joerg Schad
Assignee: Joerg Schad
Labels: mesosphere
We need to implement the HTTP endpoints for Quota as outlined in the Design
Doc:(https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I).
This also includes validating quota requests in terms of syntax correctness,
updating Master bookkeeping structures, persisting quota requests in the
{{Registry}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
