[jira] [Commented] (MESOS-6112) Frameworks are starved when > 5 are run concurrently
[ https://issues.apache.org/jira/browse/MESOS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450888#comment-15450888 ] Guangya Liu commented on MESOS-6112: Is this duplicate with MESOS-3202? I think that this will only happen when you have more frameworks than agents? Can quota help if one role per framework? > Frameworks are starved when > 5 are run concurrently > > > Key: MESOS-6112 > URL: https://issues.apache.org/jira/browse/MESOS-6112 > Project: Mesos > Issue Type: Task > Components: allocation, master >Affects Versions: 1.0.1 >Reporter: Michael Gummelt > > As I understand it, the master will send an offer to a list of frameworks > ordered by DRF, until the offer is accepted. There is a 1s wait time between > each offering. Once the decline timeout for the first framework has been > reached, rather than continuing to submit the offer to the rest of the > frameworks in the list, the master starts over at the beginning, starving the > rest of the frameworks. > This means that in order for Mesos to support > 5 concurrent frameworks, all > frameworks must be good citizens and set their decline timeout to something > large or suppress offers. I think this is a fairly undesirable state of > things. > I propose that the master instead continues to submit the offer to every > registered framework, even if the declineOffer timeout has been reached. > The potential increase in task startup latency that could be introduced by > this change can be obviated in part if we also make the master smarter about > how long to wait between successive offers, rather than a static 1s. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6107) Ubuntu installation and compilation instructions don't work (are out-of-date)
[
https://issues.apache.org/jira/browse/MESOS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450817#comment-15450817
]
haosdent commented on MESOS-6107:
-
[~cp1] 16.04 works for me as well. Could you show the files under {{build}}
folder and paste the detail logs about {{../configure}}
> Ubuntu installation and compilation instructions don't work (are out-of-date)
> -
>
> Key: MESOS-6107
> URL: https://issues.apache.org/jira/browse/MESOS-6107
> Project: Mesos
> Issue Type: Bug
>Reporter: Colbert Philippe
>
> I am new to Mesos. I read the installation documentation and compilation
> instructions. This process as described in the documentation on the website
> does not work when trying to install from Linux - Ubuntu. Compilation does
> not work!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-6112) Frameworks are starved when > 5 are run concurrently
[ https://issues.apache.org/jira/browse/MESOS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Gummelt updated MESOS-6112: --- Component/s: allocation > Frameworks are starved when > 5 are run concurrently > > > Key: MESOS-6112 > URL: https://issues.apache.org/jira/browse/MESOS-6112 > Project: Mesos > Issue Type: Task > Components: allocation, master >Affects Versions: 1.0.1 >Reporter: Michael Gummelt > > As I understand it, the master will send an offer to a list of frameworks > ordered by DRF, until the offer is accepted. There is a 1s wait time between > each offering. Once the decline timeout for the first framework has been > reached, rather than continuing to submit the offer to the rest of the > frameworks in the list, the master starts over at the beginning, starving the > rest of the frameworks. > This means that in order for Mesos to support > 5 concurrent frameworks, all > frameworks must be good citizens and set their decline timeout to something > large or suppress offers. I think this is a fairly undesirable state of > things. > I propose that the master instead continues to submit the offer to every > registered framework, even if the declineOffer timeout has been reached. > The potential increase in task startup latency that could be introduced by > this change can be obviated in part if we also make the master smarter about > how long to wait between successive offers, rather than a static 1s. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6112) Frameworks are starved when > 5 are run concurrently
[ https://issues.apache.org/jira/browse/MESOS-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450578#comment-15450578 ] Michael Gummelt commented on MESOS-6112: cc [~gabriel.hartm...@gmail.com] [~clambert] > Frameworks are starved when > 5 are run concurrently > > > Key: MESOS-6112 > URL: https://issues.apache.org/jira/browse/MESOS-6112 > Project: Mesos > Issue Type: Task > Components: master >Affects Versions: 1.0.1 >Reporter: Michael Gummelt > > As I understand it, the master will send an offer to a list of frameworks > ordered by DRF, until the offer is accepted. There is a 1s wait time between > each offering. Once the decline timeout for the first framework has been > reached, rather than continuing to submit the offer to the rest of the > frameworks in the list, the master starts over at the beginning, starving the > rest of the frameworks. > This means that in order for Mesos to support > 5 concurrent frameworks, all > frameworks must be good citizens and set their decline timeout to something > large or suppress offers. I think this is a fairly undesirable state of > things. > I propose that the master instead continues to submit the offer to every > registered framework, even if the declineOffer timeout has been reached. > The potential increase in task startup latency that could be introduced by > this change can be obviated in part if we also make the master smarter about > how long to wait between successive offers, rather than a static 1s. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6112) Frameworks are starved when > 5 are run concurrently
Michael Gummelt created MESOS-6112: -- Summary: Frameworks are starved when > 5 are run concurrently Key: MESOS-6112 URL: https://issues.apache.org/jira/browse/MESOS-6112 Project: Mesos Issue Type: Task Components: master Affects Versions: 1.0.1 Reporter: Michael Gummelt As I understand it, the master will send an offer to a list of frameworks ordered by DRF, until the offer is accepted. There is a 1s wait time between each offering. Once the decline timeout for the first framework has been reached, rather than continuing to submit the offer to the rest of the frameworks in the list, the master starts over at the beginning, starving the rest of the frameworks. This means that in order for Mesos to support > 5 concurrent frameworks, all frameworks must be good citizens and set their decline timeout to something large or suppress offers. I think this is a fairly undesirable state of things. I propose that the master instead continues to submit the offer to every registered framework, even if the declineOffer timeout has been reached. The potential increase in task startup latency that could be introduced by this change can be obviated in part if we also make the master smarter about how long to wait between successive offers, rather than a static 1s. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6111) Offer cycle is undocumented
Michael Gummelt created MESOS-6111: -- Summary: Offer cycle is undocumented Key: MESOS-6111 URL: https://issues.apache.org/jira/browse/MESOS-6111 Project: Mesos Issue Type: Task Components: documentation Affects Versions: 1.0.1 Reporter: Michael Gummelt cc [~neilc] AFAICT, the "offer cycle" in Mesos is undocumented. As it has been explained to me, the master will send on offer to a successive list of frameworks ordered by DRF, with a 1s gap in between each offer. And when the decline timeout (default 5s) is reached, it will start over at the beginning of the list. This means that, by default, all other frameworks other than the first 5 in DRF ordering will be starved. I'm going to submit a separate JIRA with a proposal to fix this, but at the very least, we should document the above behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6107) Ubuntu installation and compilation instructions don't work (are out-of-date)
[ https://issues.apache.org/jira/browse/MESOS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450508#comment-15450508 ] Colbert Philippe commented on MESOS-6107: - I'm installing Mesos 1.0.1 (latest version) on VirtualBox (latest version). I created a VM in VirtualBox with Unbuntu 16.06 (latest version).I followed the small number of steps from the website. I installed all the necessary dependencies without a problem. However, when came time to compile Mesos, I ran into problems. Here is the list of instructions to compile. # Change working directory. $ cd mesos # Bootstrap (Only required if building from git repository). $ ./bootstrap # Configure and build. $ mkdir build $ cd build $ ../configure $ make I managed to get to the second last line to run ../configure, without a problems. It ran fine, displaying a number of lines without apparent problems. When came time to run make, I get the error message: *** No targets specified and no makefile found. Stop This obviously means that there are no make files in the build directory. It's like the generation of the source directory was not completed properly. However, no error messages were given to that effect when running ../configure. I have a 64 Gigabyte hard-drive that is used only 23% (stats given by df command). This process of compiling Mesos needs to be reviewed. > Ubuntu installation and compilation instructions don't work (are out-of-date) > - > > Key: MESOS-6107 > URL: https://issues.apache.org/jira/browse/MESOS-6107 > Project: Mesos > Issue Type: Bug >Reporter: Colbert Philippe > > I am new to Mesos. I read the installation documentation and compilation > instructions. This process as described in the documentation on the website > does not work when trying to install from Linux - Ubuntu. Compilation does > not work! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6110) TASK_ERROR because of HealthCheck when using 1.1.0
[ https://issues.apache.org/jira/browse/MESOS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Silas Snider updated MESOS-6110: Description: When sending a task launch using the 1.0.x protos and the legacy (non-http) API, tasks with a healthcheck defined are rejected (TASK_ERROR) because the 'type' field is not set. This field is marked optional in the proto and is not available before 1.1.0, so it should not be required in order to keep the mesos v1 api compatibility promise. was: When sending a task launch using the 1.0.x protos and the legacy (non-http) API, tasks with a healthcheck defined are rejected (TASK_ERROR) because the 'type' field is not set. This field is marked optional in the proto and is not available before 1.1.0, so it should not be required in order to keep the compatibility consistent. > TASK_ERROR because of HealthCheck when using 1.1.0 > -- > > Key: MESOS-6110 > URL: https://issues.apache.org/jira/browse/MESOS-6110 > Project: Mesos > Issue Type: Bug > Components: master >Affects Versions: 1.1.0 >Reporter: Silas Snider >Assignee: Alexander Rukletsov >Priority: Blocker > Labels: compatibility, health-check > > When sending a task launch using the 1.0.x protos and the legacy (non-http) > API, tasks with a healthcheck defined are rejected (TASK_ERROR) because the > 'type' field is not set. > This field is marked optional in the proto and is not available before 1.1.0, > so it should not be required in order to keep the mesos v1 api compatibility > promise. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-6110) TASK_ERROR because of HealthCheck when using 1.1.0
[ https://issues.apache.org/jira/browse/MESOS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Wu reassigned MESOS-6110: Assignee: Alexander Rukletsov > TASK_ERROR because of HealthCheck when using 1.1.0 > -- > > Key: MESOS-6110 > URL: https://issues.apache.org/jira/browse/MESOS-6110 > Project: Mesos > Issue Type: Bug > Components: master >Affects Versions: 1.1.0 >Reporter: Silas Snider >Assignee: Alexander Rukletsov >Priority: Blocker > Labels: compatibility, health-check > > When sending a task launch using the 1.0.x protos and the legacy (non-http) > API, tasks with a healthcheck defined are rejected (TASK_ERROR) because the > 'type' field is not set. > This field is marked optional in the proto and is not available before 1.1.0, > so it should not be required in order to keep the compatibility consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6110) TASK_ERROR because of HealthCheck when using 1.1.0
Silas Snider created MESOS-6110: --- Summary: TASK_ERROR because of HealthCheck when using 1.1.0 Key: MESOS-6110 URL: https://issues.apache.org/jira/browse/MESOS-6110 Project: Mesos Issue Type: Bug Components: master Affects Versions: 1.1.0 Reporter: Silas Snider Priority: Blocker When sending a task launch using the 1.0.x protos and the legacy (non-http) API, tasks with a healthcheck defined are rejected (TASK_ERROR) because the 'type' field is not set. This field is marked optional in the proto and is not available before 1.1.0, so it should not be required in order to keep the compatibility consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6074) Master check failure if the metrics endpoint is polled soon after it starts
[
https://issues.apache.org/jira/browse/MESOS-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450211#comment-15450211
]
Yan Xu commented on MESOS-6074:
---
{noformat:title=}
commit 1364aa5617743f052f25b278d9ba931b9bb806da
Author: Jiang Yan Xu
Date: Tue Aug 30 09:35:06 2016 -0700
Added 'HierarchicalAllocatorTest.ResourceMetricsUninitialized' test.
To test the fix (https://reviews.apache.org/r/51529/) for a
CHECK failure in HierarchicalAllocatorProcess due to uninitialized
sorter pointers.
Review: https://reviews.apache.org/r/51528
commit f4e9631ca6c35625a9bea3b298ba5f9d30478d33
Author: Jiang Yan Xu
Date: Tue Aug 23 22:41:16 2016 -0700
Initialize sorter pointers in HierarchicalAllocatorProcess constructor.
Otherwise the sorter pointers can be uninitialized if the metrics
endpoint is polled before the master is initialized.
Review: https://reviews.apache.org/r/51529
{noformat}
> Master check failure if the metrics endpoint is polled soon after it starts
> ---
>
> Key: MESOS-6074
> URL: https://issues.apache.org/jira/browse/MESOS-6074
> Project: Mesos
> Issue Type: Bug
> Components: master
>Affects Versions: 1.0.0
>Reporter: Yan Xu
>Assignee: Yan Xu
>Priority: Critical
> Fix For: 1.1.0, 1.0.2
>
>
> We observed the following check failure
> {noformat:title=}
> F0822 22:27:10.364923 10489 owned.hpp:110] Check failed: 'get()' Must be non
> NULL
> {noformat}
> called from
> {{mesos::internal::master::allocator::internal::HierarchicalAllocatorProcess::_resources_total}}
>
> The code:
> {code}
> double HierarchicalAllocatorProcess::_resources_total(
> const string& resource)
> {
> Option total =
> roleSorter->totalScalarQuantities()
> .get(resource);
> return total.isSome() ? total->value() : 0;
> }
> {code}
> See
> [github|https://github.com/apache/mesos/blob/dcc8bd7d2a942889fe473c21ab64e863d0e6a13f/src/master/allocator/mesos/hierarchical.cpp#L1804]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-6109) Version 1.0.1 Debian package for Ubunty Xenial (16.04) appears to be broken
Ulrich Romahn created MESOS-6109: Summary: Version 1.0.1 Debian package for Ubunty Xenial (16.04) appears to be broken Key: MESOS-6109 URL: https://issues.apache.org/jira/browse/MESOS-6109 Project: Mesos Issue Type: Bug Components: build Affects Versions: 1.0.1 Environment: Ubuntu Xenial (16.04) Reporter: Ulrich Romahn The deb package published on the mesosphere repository for Ubuntu Xenial seems to be broken. I followed the instructions given in https://open.mesosphere.com/getting-started/install/ to install mesos and marathon on a cluster running Ubuntu Xenial. However, during the install of the mesos package, I am getting an error that it cannot unpack the file jquery.js and it errors out saying something like "unexpected end of file". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6107) Ubuntu installation and compilation instructions don't work (are out-of-date)
[ https://issues.apache.org/jira/browse/MESOS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449897#comment-15449897 ] Joseph Wu commented on MESOS-6107: -- Can you provide more details? Getting started on Ubuntu 14 works for me. > Ubuntu installation and compilation instructions don't work (are out-of-date) > - > > Key: MESOS-6107 > URL: https://issues.apache.org/jira/browse/MESOS-6107 > Project: Mesos > Issue Type: Bug >Reporter: Colbert Philippe > > I am new to Mesos. I read the installation documentation and compilation > instructions. This process as described in the documentation on the website > does not work when trying to install from Linux - Ubuntu. Compilation does > not work! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6108) Provide official Docker image for Mesos
Colbert Philippe created MESOS-6108: --- Summary: Provide official Docker image for Mesos Key: MESOS-6108 URL: https://issues.apache.org/jira/browse/MESOS-6108 Project: Mesos Issue Type: Improvement Reporter: Colbert Philippe Installing Mesos is a pain because we have to compile it. The instructions for compiling are sketchy and, in my experience, don’t work. We shouldn’t have to compile a framework like Mesos. It’s intimidating. I would suggest that we use new and modern tools like Docker to allow users to get started much more quicker in a fail-safe way.Yes, there should be Mesos image for each version published. The image should have good documentation to allow novice to use it and make the first steps into Mesos using the Docker image. Creating a Docker image is relatively easy. There is no good reason why it’s not done already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-6074) Master check failure if the metrics endpoint is polled soon after it starts
[
https://issues.apache.org/jira/browse/MESOS-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Xu reassigned MESOS-6074:
-
Assignee: Yan Xu
> Master check failure if the metrics endpoint is polled soon after it starts
> ---
>
> Key: MESOS-6074
> URL: https://issues.apache.org/jira/browse/MESOS-6074
> Project: Mesos
> Issue Type: Bug
> Components: master
>Affects Versions: 1.0.0
>Reporter: Yan Xu
>Assignee: Yan Xu
>Priority: Critical
> Fix For: 1.1.0, 1.0.2
>
>
> We observed the following check failure
> {noformat:title=}
> F0822 22:27:10.364923 10489 owned.hpp:110] Check failed: 'get()' Must be non
> NULL
> {noformat}
> called from
> {{mesos::internal::master::allocator::internal::HierarchicalAllocatorProcess::_resources_total}}
>
> The code:
> {code}
> double HierarchicalAllocatorProcess::_resources_total(
> const string& resource)
> {
> Option total =
> roleSorter->totalScalarQuantities()
> .get(resource);
> return total.isSome() ? total->value() : 0;
> }
> {code}
> See
> [github|https://github.com/apache/mesos/blob/dcc8bd7d2a942889fe473c21ab64e863d0e6a13f/src/master/allocator/mesos/hierarchical.cpp#L1804]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-6074) Master check failure if the metrics endpoint is polled soon after it starts
[
https://issues.apache.org/jira/browse/MESOS-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449530#comment-15449530
]
Yan Xu commented on MESOS-6074:
---
https://reviews.apache.org/r/51528/
https://reviews.apache.org/r/51529/
> Master check failure if the metrics endpoint is polled soon after it starts
> ---
>
> Key: MESOS-6074
> URL: https://issues.apache.org/jira/browse/MESOS-6074
> Project: Mesos
> Issue Type: Bug
> Components: master
>Affects Versions: 1.0.0
>Reporter: Yan Xu
>Priority: Critical
> Fix For: 1.1.0, 1.0.2
>
>
> We observed the following check failure
> {noformat:title=}
> F0822 22:27:10.364923 10489 owned.hpp:110] Check failed: 'get()' Must be non
> NULL
> {noformat}
> called from
> {{mesos::internal::master::allocator::internal::HierarchicalAllocatorProcess::_resources_total}}
>
> The code:
> {code}
> double HierarchicalAllocatorProcess::_resources_total(
> const string& resource)
> {
> Option total =
> roleSorter->totalScalarQuantities()
> .get(resource);
> return total.isSome() ? total->value() : 0;
> }
> {code}
> See
> [github|https://github.com/apache/mesos/blob/dcc8bd7d2a942889fe473c21ab64e863d0e6a13f/src/master/allocator/mesos/hierarchical.cpp#L1804]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4606) Add IPv6 support to net::IP and net::IPNetwork
[ https://issues.apache.org/jira/browse/MESOS-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449526#comment-15449526 ] Avinash Sridharan commented on MESOS-4606: -- Has there been any progress on this JIRA? > Add IPv6 support to net::IP and net::IPNetwork > -- > > Key: MESOS-4606 > URL: https://issues.apache.org/jira/browse/MESOS-4606 > Project: Mesos > Issue Type: Improvement > Components: stout >Reporter: Benno Evers >Assignee: Benno Evers >Priority: Minor > Labels: network, stout > > The classes net::IP and net::IPNetwork should to be able to store IPv6 > addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-6060) Add MOUNT or PATH disk type in logging resources.
[
https://issues.apache.org/jira/browse/MESOS-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448682#comment-15448682
]
Anindya Sinha edited comment on MESOS-6060 at 8/30/16 10:27 AM:
Here is an example of the output being added in this RR:
{{disk(alice)\[MOUNT:/mnt1:hadoop:/hdfs:/data:rw]:1}}
The newly added section is {{MOUNT:/mnt1}}.
was (Author: anindya.sinha):
Here is an example of the output being added in this RR:
{{disk(alice)\[MOUNT:/mnt1:hadoop:/hdfs:/data:rw]:1}}
The newly added section is {{MOUNT:/mnt1}}
RR published:
https://reviews.apache.org/r/51517/
> Add MOUNT or PATH disk type in logging resources.
> -
>
> Key: MESOS-6060
> URL: https://issues.apache.org/jira/browse/MESOS-6060
> Project: Mesos
> Issue Type: Improvement
> Components: general
>Reporter: Anindya Sinha
>Assignee: Anindya Sinha
>Priority: Minor
> Labels: persistent-volumes, resource
>
> While logging persistent volume disk resources, we should also log the source
> (if present), ie. if the disk type is MOUNT or PATH, and the corresponding
> root point. This would be helpful when the agent has multiple disk resources
> and having this information in the log would help identifying the disk in
> various scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-6060) Add MOUNT or PATH disk type in logging resources.
[
https://issues.apache.org/jira/browse/MESOS-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448682#comment-15448682
]
Anindya Sinha commented on MESOS-6060:
--
Here is an example of the output being added in this RR:
{{disk(alice)\[MOUNT:/mnt1:hadoop:/hdfs:/data:rw]:1}}
The newly added section is {{MOUNT:/mnt1}}
RR published:
https://reviews.apache.org/r/51517/
> Add MOUNT or PATH disk type in logging resources.
> -
>
> Key: MESOS-6060
> URL: https://issues.apache.org/jira/browse/MESOS-6060
> Project: Mesos
> Issue Type: Improvement
> Components: general
>Reporter: Anindya Sinha
>Assignee: Anindya Sinha
>Priority: Minor
> Labels: persistent-volumes, resource
>
> While logging persistent volume disk resources, we should also log the source
> (if present), ie. if the disk type is MOUNT or PATH, and the corresponding
> root point. This would be helpful when the agent has multiple disk resources
> and having this information in the log would help identifying the disk in
> various scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-6107) Ubuntu installation and compilation instructions don't work (are out-of-date)
Colbert Philippe created MESOS-6107: --- Summary: Ubuntu installation and compilation instructions don't work (are out-of-date) Key: MESOS-6107 URL: https://issues.apache.org/jira/browse/MESOS-6107 Project: Mesos Issue Type: Bug Reporter: Colbert Philippe I am new to Mesos. I read the installation documentation and compilation instructions. This process as described in the documentation on the website does not work when trying to install from Linux - Ubuntu. Compilation does not work! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6106) Validate the host ports which container wants to expose to are from the resources assigned to it
Qian Zhang created MESOS-6106:
-
Summary: Validate the host ports which container wants to expose
to are from the resources assigned to it
Key: MESOS-6106
URL: https://issues.apache.org/jira/browse/MESOS-6106
Project: Mesos
Issue Type: Task
Components: isolation
Reporter: Qian Zhang
Assignee: Qian Zhang
In CNI isolator, we need to validate the host ports which container wants to
expose to ({{NetworkInfo.PortMapping.host_port}}) are from the resources
assigned to it (i.e., from the resource offer used by framework to launch
container), so that we can ensure container will not expose to an arbitrary
host port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4440) Clean get/post/deleteRequest func and let the caller to use the general funcion.
[ https://issues.apache.org/jira/browse/MESOS-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448166#comment-15448166 ] Yongqiao Wang commented on MESOS-4440: -- Append the related RR to clean up the http::internal::get function: https://reviews.apache.org/r/51493/ https://reviews.apache.org/r/51495/ https://reviews.apache.org/r/51505/ https://reviews.apache.org/r/51508/ > Clean get/post/deleteRequest func and let the caller to use the general > funcion. > > > Key: MESOS-4440 > URL: https://issues.apache.org/jira/browse/MESOS-4440 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: tech-debt > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
