[jira] [Updated] (MESOS-5855) Create a 'Disk (not) full' example framework
[ https://issues.apache.org/jira/browse/MESOS-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5855: - Description: We need example frameworks for verifying the correct behavior of posix/disk isolator when the disk quota enforcement is in place. One framework for verifying that disk quota enforcement is working and that container gets terminated when it goes beyond disk quota, and another one for verifying that container does not get killed if it stays within its disk quota bounds. was: We need example frameworks for verifying the correct behavior of posix/disk isolator when the disk quota enforcement is in place. One framework for verifying that disk quota enforcement is working and that container gets terminated when it goes beyond quota, and another one for verifying that container does not get killed if it stays within it's quota bouds. > Create a 'Disk (not) full' example framework > > > Key: MESOS-5855 > URL: https://issues.apache.org/jira/browse/MESOS-5855 > Project: Mesos > Issue Type: Task >Reporter: Artem Harutyunyan >Assignee: Artem Harutyunyan >Priority: Minor > > We need example frameworks for verifying the correct behavior of posix/disk > isolator when the disk quota enforcement is in place. One framework for > verifying that disk quota enforcement is working and that container gets > terminated when it goes beyond disk quota, and another one for verifying that > container does not get killed if it stays within its disk quota bounds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5855) Create a 'Disk (not) full' example framework
[ https://issues.apache.org/jira/browse/MESOS-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5855: - Description: We need example frameworks for verifying the correct behavior of posix/disk isolator when the disk quota enforcement is in place. One framework for verifying that disk quota enforcement is working and that container gets terminated when it goes beyond quota, and another one for verifying that container does not get killed if it stays within it's quota bouds. was:We need an example framework for verifying the correct behavior of posix/disk isolator when the disk quota enforcement is in place. > Create a 'Disk (not) full' example framework > > > Key: MESOS-5855 > URL: https://issues.apache.org/jira/browse/MESOS-5855 > Project: Mesos > Issue Type: Task >Reporter: Artem Harutyunyan >Assignee: Artem Harutyunyan >Priority: Minor > > We need example frameworks for verifying the correct behavior of posix/disk > isolator when the disk quota enforcement is in place. One framework for > verifying that disk quota enforcement is working and that container gets > terminated when it goes beyond quota, and another one for verifying that > container does not get killed if it stays within it's quota bouds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5855) Create a 'Disk (not) full' example framework
[ https://issues.apache.org/jira/browse/MESOS-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5855: - Summary: Create a 'Disk (not) full' example framework (was: Create a 'Disk not full' example framework) > Create a 'Disk (not) full' example framework > > > Key: MESOS-5855 > URL: https://issues.apache.org/jira/browse/MESOS-5855 > Project: Mesos > Issue Type: Task >Reporter: Artem Harutyunyan >Assignee: Artem Harutyunyan >Priority: Minor > > We need an example framework for verifying the correct behavior of posix/disk > isolator when the disk quota enforcement is in place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5855) Create a 'Disk not full' example framework
Artem Harutyunyan created MESOS-5855: Summary: Create a 'Disk not full' example framework Key: MESOS-5855 URL: https://issues.apache.org/jira/browse/MESOS-5855 Project: Mesos Issue Type: Task Reporter: Artem Harutyunyan Assignee: Artem Harutyunyan Priority: Minor We need an example framework for verifying the correct behavior of posix/disk isolator when the disk quota enforcement is in place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5464) The max number of completed executors for a mesos slave should be configurable
[ https://issues.apache.org/jira/browse/MESOS-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381019#comment-15381019 ] Lijun Tang commented on MESOS-5464: --- Hi, I am new to Mesos, this issue seems a good start point for me. Should I implement this feature by adding one more command line option, like --max_completed_executors_per_framework? Should I add some unit test for this? Thanks, Lijun > The max number of completed executors for a mesos slave should be configurable > -- > > Key: MESOS-5464 > URL: https://issues.apache.org/jira/browse/MESOS-5464 > Project: Mesos > Issue Type: Improvement >Reporter: Kevin Johnstone >Priority: Trivial > Original Estimate: 24h > Remaining Estimate: 24h > > The number of completed executors per framework should be configurable. > Frameworks such as Chronos make one executor per tasks and the default of 150 > executors makes sandbox logs inaccessible through the mesos UI very quickly, > far before the specified timeout for garbage collection for a task. > https://github.com/apache/mesos/blob/4db9b630cc67f706a8814436309ab589cbaa64fc/src/slave/constants.hpp#L64 > shows where the constant is currently set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5186) mesos.interface: Allow using protobuf 3.x
[
https://issues.apache.org/jira/browse/MESOS-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380866#comment-15380866
]
Yong Tang commented on MESOS-5186:
--
[~xds2000] protobuf 3.0 is still in beta but it looks like protobuf 3 will be
released around end of July:
https://groups.google.com/forum/#!topic/protobuf/NcK5ae8ZUSU
I think we could wait until 3.0 is released.
> mesos.interface: Allow using protobuf 3.x
> -
>
> Key: MESOS-5186
> URL: https://issues.apache.org/jira/browse/MESOS-5186
> Project: Mesos
> Issue Type: Improvement
> Components: python api
>Reporter: Myautsai PAN
>Assignee: Yong Tang
>Priority: Minor
> Labels: easyfix
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> We're working on integrating TensorFlow(https://www.tensorflow.org) with
> mesos. Both the two require {{protobuf}}. The python package
> {{mesos.interface}} requires {{protobuf>=2.6.1,<3}}, but {{tensorflow}}
> requires {{protobuf>=3.0.0}} . Though protobuf 3.x is not compatible with
> protobuf 2.x, but anyway we modify the {{setup.py}}
> (https://github.com/apache/mesos/blob/66cddaf/src/python/interface/setup.py.in#L29)
> from {{'install_requires': [ 'google-common>=0.0.1', 'protobuf>=2.6.1,<3'
> ],}} to {{'install_requires': [ 'google-common>=0.0.1', 'protobuf>=2.6.1' ],}}
> It works fine. Would you please consider support protobuf 3.x officially in
> the next release? Maybe just remove the {{,<3}} restriction is enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5700) Benchmark for Resource class (protobuf vs. C++)
[ https://issues.apache.org/jira/browse/MESOS-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma updated MESOS-5700: Attachment: port.perf.log > Benchmark for Resource class (protobuf vs. C++) > --- > > Key: MESOS-5700 > URL: https://issues.apache.org/jira/browse/MESOS-5700 > Project: Mesos > Issue Type: Bug >Reporter: Klaus Ma >Assignee: Klaus Ma > Attachments: port.perf.log, reservation.perf.log > > > Add benchmark of Resource class for Allocation Performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5700) Benchmark for Resource class (protobuf vs. C++)
[ https://issues.apache.org/jira/browse/MESOS-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma updated MESOS-5700: Attachment: reservation.perf.log > Benchmark for Resource class (protobuf vs. C++) > --- > > Key: MESOS-5700 > URL: https://issues.apache.org/jira/browse/MESOS-5700 > Project: Mesos > Issue Type: Bug >Reporter: Klaus Ma >Assignee: Klaus Ma > Attachments: reservation.perf.log > > > Add benchmark of Resource class for Allocation Performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5700) Benchmark for Resource class (protobuf vs. C++)
[
https://issues.apache.org/jira/browse/MESOS-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380797#comment-15380797
]
Klaus Ma commented on MESOS-5700:
-
Just did a profiling for Resources class based on the benchmark, please refer
to the attachment for the detail. Here's suggestion to improve the performance:
1. In reservation.perf.log, it shows {{operator!=(string, string)}} in
{{addable/subtractable}} is the heavy function; so I'm thinking to
* Make name of Resource to be enum instread of string (as we discussed in
the doc)
* Introduce roleId (uint64_t), similar to uid in Linux; {{roleId}} is used
within Mesos master/agent
2. In port.perf.log, it shows {{ranges validation}} is the heavy function; no
conclusion for now, but it's better to refine {{Resource::validate}}:
* role validation is not necessary in every operator/loop
* ranges validation maybe not necessary in every operator/loop,
{{coalesce}} may handle it (investigating)
cc [~bmahler]/[~gyliu]/[~alexr]
> Benchmark for Resource class (protobuf vs. C++)
> ---
>
> Key: MESOS-5700
> URL: https://issues.apache.org/jira/browse/MESOS-5700
> Project: Mesos
> Issue Type: Bug
>Reporter: Klaus Ma
>Assignee: Klaus Ma
>
> Add benchmark of Resource class for Allocation Performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-5123) Docker task may fail if path to agent work_dir is relative.
[
https://issues.apache.org/jira/browse/MESOS-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Ma reassigned MESOS-5123:
---
Assignee: Klaus Ma
> Docker task may fail if path to agent work_dir is relative.
>
>
> Key: MESOS-5123
> URL: https://issues.apache.org/jira/browse/MESOS-5123
> Project: Mesos
> Issue Type: Improvement
> Components: docker
>Affects Versions: 1.0.0
>Reporter: Alexander Rukletsov
>Assignee: Klaus Ma
> Labels: docker, documentation, mesosphere
>
> When a local folder for agent’s {{\-\-work_dir}} is specified (e.g.,
> {{\-\-work_dir=w/s}}) docker complains that there are forbidden symbols in a
> *local* volume name. Specifying an absolute path (e.g.,
> {{\-\-work_dir=/tmp}}) solves the problem.
> Docker error observed:
> {noformat}
> docker: Error response from daemon: create
> w/s/slaves/33b8fe47-e9e0-468a-83a6-98c1e3537e59-S1/frameworks/33b8fe47-e9e0-468a-83a6-98c1e3537e59-0001/executors/docker-test/runs/3cc5cb04-d0a9-490e-94d5-d446b66c97cc:
> volume name invalid:
> "w/s/slaves/33b8fe47-e9e0-468a-83a6-98c1e3537e59-S1/frameworks/33b8fe47-e9e0-468a-83a6-98c1e3537e59-0001/executors/docker-test/runs/3cc5cb04-d0a9-490e-94d5-d446b66c97cc"
> includes invalid characters for a local volume name, only
> "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed.
> {noformat}
> First off, it is not obvious that Mesos always creates a volume for the
> sandbox. We may want to document it.
> Second, it's hard to understand that local {{work_dir}} can trigger forbidden
> symbols error in docker. Does it make sense to check it during agent launch
> if docker containerizer is enabled? Or reject docker tasks during task
> validation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
