[jira] [Updated] (MESOS-4726) Document scheduler driver calls in framework development guide.
[ https://issues.apache.org/jira/browse/MESOS-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4726: -- Story Points: 2 > Document scheduler driver calls in framework development guide. > --- > > Key: MESOS-4726 > URL: https://issues.apache.org/jira/browse/MESOS-4726 > Project: Mesos > Issue Type: Documentation >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: mesosphere > > The interface examples are slightly out of sync with scheduler.hpp, most > notably missing the new acceptOffers call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4726) Document scheduler driver calls in framework development guide.
[ https://issues.apache.org/jira/browse/MESOS-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4726: -- Labels: mesosphere (was: ) > Document scheduler driver calls in framework development guide. > --- > > Key: MESOS-4726 > URL: https://issues.apache.org/jira/browse/MESOS-4726 > Project: Mesos > Issue Type: Documentation >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: mesosphere > > The interface examples are slightly out of sync with scheduler.hpp, most > notably missing the new acceptOffers call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4797) Add a couple of registrar tests for /weights endpoint
[ https://issues.apache.org/jira/browse/MESOS-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4797: -- Story Points: 2 > Add a couple of registrar tests for /weights endpoint > - > > Key: MESOS-4797 > URL: https://issues.apache.org/jira/browse/MESOS-4797 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4316) Support get non-default weights by /weights
[ https://issues.apache.org/jira/browse/MESOS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4316: -- Story Points: 5 > Support get non-default weights by /weights > --- > > Key: MESOS-4316 > URL: https://issues.apache.org/jira/browse/MESOS-4316 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere > > Like /quota, we should also add query logic for /weights to keep consistent. > Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4726) Document scheduler driver calls in framework development guide.
[ https://issues.apache.org/jira/browse/MESOS-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4726: -- Sprint: Mesosphere Sprint 31 > Document scheduler driver calls in framework development guide. > --- > > Key: MESOS-4726 > URL: https://issues.apache.org/jira/browse/MESOS-4726 > Project: Mesos > Issue Type: Documentation >Reporter: Joerg Schad >Assignee: Joerg Schad > > The interface examples are slightly out of sync with scheduler.hpp, most > notably missing the new acceptOffers call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4797) Add a couple of registrar tests for /weights endpoint
[ https://issues.apache.org/jira/browse/MESOS-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4797: -- Sprint: Mesosphere Sprint 31 > Add a couple of registrar tests for /weights endpoint > - > > Key: MESOS-4797 > URL: https://issues.apache.org/jira/browse/MESOS-4797 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4316) Support get non-default weights by /weights
[ https://issues.apache.org/jira/browse/MESOS-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4316: -- Sprint: Mesosphere Sprint 31 > Support get non-default weights by /weights > --- > > Key: MESOS-4316 > URL: https://issues.apache.org/jira/browse/MESOS-4316 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang >Priority: Minor > Labels: mesosphere > > Like /quota, we should also add query logic for /weights to keep consistent. > Then /roles no longer needs to show weight information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4881) Rescind all outstanding offers after changing some weights.
[ https://issues.apache.org/jira/browse/MESOS-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4881: -- Story Points: 2 > Rescind all outstanding offers after changing some weights. > --- > > Key: MESOS-4881 > URL: https://issues.apache.org/jira/browse/MESOS-4881 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4902) Add authentication to remaining agent endpoints
[
https://issues.apache.org/jira/browse/MESOS-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-4902:
--
Sprint: Mesosphere Sprint 31
> Add authentication to remaining agent endpoints
> ---
>
> Key: MESOS-4902
> URL: https://issues.apache.org/jira/browse/MESOS-4902
> Project: Mesos
> Issue Type: Improvement
> Components: HTTP API
>Reporter: Greg Mann
> Labels: authentication, http, mesosphere, security
>
> In addition to the endpoints addressed by MESOS-4850, the following endpoints
> would also benefit from HTTP authentication:
> * {{/files/*}}
> * {{/profiler/*}}
> * {{/logging/toggle}}
> * {{/metrics/snapshot}}
> * {{/monitor/statistics}}
> * {{/system/stats.json}}
> Adding HTTP authentication to these endpoints is a bit more complicated: some
> endpoints are defined at the libprocess level, while others are defined in
> code that is shared by the master and agent.
> While working on MESOS-4850, it became apparent that since our tests use the
> same instance of libprocess for both master and agent, different default
> authentication realms must be used for master/agent so that HTTP
> authentication can be independently enabled/disabled for each.
> We should establish a mechanism for making an endpoint authenticated that
> allows us to:
> 1) Install an endpoint like {{/files}}, whose code is shared by the master
> and agent, with different authentication realms for the master and agent
> 2) Avoid hard-coding a default authentication realm into libprocess, to
> permit the use of different authentication realms for the master and agent
> and to keep application-level concerns from leaking into libprocess
> Another option would be to use a single default authentication realm and
> always enable or disable HTTP authentication for *both* the master and agent
> in tests. However, this wouldn't allow us to test scenarios where HTTP
> authentication is enabled on one but disabled on the other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4881) Rescind all outstanding offers after changing some weights.
[ https://issues.apache.org/jira/browse/MESOS-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4881: -- Sprint: Mesosphere Sprint 31 > Rescind all outstanding offers after changing some weights. > --- > > Key: MESOS-4881 > URL: https://issues.apache.org/jira/browse/MESOS-4881 > Project: Mesos > Issue Type: Task >Reporter: Yongqiao Wang >Assignee: Yongqiao Wang > Labels: mesosphere > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-4923) Add a new sorter for revocable resources in allocator
[
https://issues.apache.org/jira/browse/MESOS-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Ma reassigned MESOS-4923:
---
Assignee: Klaus Ma
> Add a new sorter for revocable resources in allocator
> -
>
> Key: MESOS-4923
> URL: https://issues.apache.org/jira/browse/MESOS-4923
> Project: Mesos
> Issue Type: Bug
>Reporter: Guangya Liu
>Assignee: Klaus Ma
>
> The current logic of roleSorter is that when it do role sorter, the resources
> in it will include both regular resources and revocable resources, and this
> may not accurate for some cases, take the following case as an instance:
> 1) framework1 and framework2.
> 2) framework1 got 1 reserved cpu and 9 revocable cpu. cpu(r1):1;cpu(*){REV}:9
> 3) framework2 got 9 reserved cpus: cpu(r1):9
> When allocator allocate resources in next cycle, framework2 will be handled
> first as it has less SCALAR resources than framework1, but this may not be
> right for some cases as framework1 is using only 1 reserved resources and
> other resources are revocable which can be easily got evicted.
> A proposal here is introducing a new sorter for revocable resources so as to
> distinguish the sorter for regular resources and revocable resources. To the
> built in allocator, the logic would be as this:
> 1) Quota Role Sorter
> 2) non-revocable Role Sorter
> 3) Revocable Role Sorter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4877) Mesos containerizer can't handle top level docker image like "alpine" (must use "library/alpine")
[
https://issues.apache.org/jira/browse/MESOS-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192135#comment-15192135
]
Guangya Liu commented on MESOS-4877:
There is a patch chain here https://reviews.apache.org/r/44672/
> Mesos containerizer can't handle top level docker image like "alpine" (must
> use "library/alpine")
> -
>
> Key: MESOS-4877
> URL: https://issues.apache.org/jira/browse/MESOS-4877
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker
>Affects Versions: 0.27.0, 0.27.1
>Reporter: Shuai Lin
>Assignee: Shuai Lin
>
> This can be demonstrated with the {{mesos-execute}} command:
> # Docker containerizer with image {{alpine}}: success
> {code}
> sudo ./build/src/mesos-execute --docker_image=alpine --containerizer=docker
> --name=just-a-test --command="sleep 1000" --master=localhost:5050
> {code}
> # Mesos containerizer with image {{alpine}}: failure
> {code}
> sudo ./build/src/mesos-execute --docker_image=alpine --containerizer=mesos
> --name=just-a-test --command="sleep 1000" --master=localhost:5050
> {code}
> # Mesos containerizer with image {{library/alpine}}: success
> {code}
> sudo ./build/src/mesos-execute --docker_image=library/alpine
> --containerizer=mesos --name=just-a-test --command="sleep 1000"
> --master=localhost:5050
> {code}
> In the slave logs:
> {code}
> ea-4460-83
> 9c-838da86af34c-0007'
> I0306 16:32:41.418269 3403 metadata_manager.cpp:159] Looking for image
> 'alpine:latest'
> I0306 16:32:41.418699 3403 registry_puller.cpp:194] Pulling image
> 'alpine:latest' from
> 'docker-manifest://registry-1.docker.io:443alpine?latest#https' to
> '/tmp/mesos-test
> /store/docker/staging/ka7MlQ'
> E0306 16:32:43.098131 3400 slave.cpp:3773] Container
> '4bf9132d-9a57-4baa-a78c-e7164e93ace6' for executor 'just-a-test' of
> framework 4f055c6f-1bea-4460-839c-838da86af34c-0
> 007 failed to start: Collect failed: Unexpected HTTP response '401
> Unauthorized
> {code}
> curl command executed:
> {code}
> $ sudo sysdig -A -p "*%evt.time %proc.cmdline" evt.type=execve and
> proc.name=curl
>16:42:53.198998042 curl -s -S -L -D -
> https://registry-1.docker.io:443/v2/alpine/manifests/latest
> 16:42:53.784958541 curl -s -S -L -D -
> https://auth.docker.io/token?service=registry.docker.io&scope=repository:alpine:pull
> 16:42:54.294192024 curl -s -S -L -D - -H Authorization: Bearer
> eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCIsIng1YyI6WyJNSUlDTHpDQ0FkU2dBd0lCQWdJQkFEQUtCZ2dxaGtqT1BRUURBakJHTVVRd1FnWURWUVFERXp0Uk5Gb3pPa2RYTjBrNldGUlFSRHBJVFRSUk9rOVVWRmc2TmtGRlF6cFNUVE5ET2tGU01rTTZUMFkzTnpwQ1ZrVkJPa2xHUlVrNlExazFTekFlRncweE5UQTJNalV4T1RVMU5EWmFGdzB4TmpBMk1qUXhPVFUxTkRaYU1FWXhSREJDQmdOVkJBTVRPMGhHU1UwNldGZFZWam8yUVZkSU9sWlpUVEk2TTFnMVREcFNWREkxT2s5VFNrbzZTMVExUmpwWVRsSklPbFJMTmtnNlMxUkxOanBCUVV0VU1Ga3dFd1lIS29aSXpqMENBUVlJS29aSXpqMERBUWNEUWdBRXl2UzIvdEI3T3JlMkVxcGRDeFdtS1NqV1N2VmJ2TWUrWGVFTUNVMDByQjI0akNiUVhreFdmOSs0MUxQMlZNQ29BK0RMRkIwVjBGZGdwajlOWU5rL2pxT0JzakNCcnpBT0JnTlZIUThCQWY4RUJBTUNBSUF3RHdZRFZSMGxCQWd3QmdZRVZSMGxBREJFQmdOVkhRNEVQUVE3U0VaSlRUcFlWMVZXT2paQlYwZzZWbGxOTWpveldEVk1PbEpVTWpVNlQxTktTanBMVkRWR09saE9Va2c2VkVzMlNEcExWRXMyT2tGQlMxUXdSZ1lEVlIwakJEOHdQWUE3VVRSYU16cEhWemRKT2xoVVVFUTZTRTAwVVRwUFZGUllPalpCUlVNNlVrMHpRenBCVWpKRE9rOUdOemM2UWxaRlFUcEpSa1ZKT2tOWk5Vc3dDZ1lJS29aSXpqMEVBd0lEU1FBd1JnSWhBTXZiT2h4cHhrTktqSDRhMFBNS0lFdXRmTjZtRDFvMWs4ZEJOVGxuWVFudkFpRUF0YVJGSGJSR2o4ZlVSSzZ4UVJHRURvQm1ZZ3dZelR3Z3BMaGJBZzNOUmFvPSJdfQ.eyJhY2Nlc3MiOltdLCJhdWQiOiJyZWdpc3RyeS5kb2NrZXIuaW8iLCJleHAiOjE0NTcyODI4NzQsImlhdCI6MTQ1NzI4MjU3NCwiaXNzIjoiYXV0aC5kb2NrZXIuaW8iLCJqdGkiOiJaOGtyNXZXNEJMWkNIRS1IcVJIaCIsIm5iZiI6MTQ1NzI4MjU3NCwic3ViIjoiIn0.C2wtJq_P-m0buPARhmQjDfh6ztIAhcvgN3tfWIZEClSgXlVQ_sAQXAALNZKwAQL2Chj7NpHX--0GW-aeL_28Aw
> https://registry-1.docker.io:443/v2/alpine/manifests/latest
> {code}
> Also got the same result with {{ubuntu}} docker image.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4906) Upgrade to clang-format-3.8.
[
https://issues.apache.org/jira/browse/MESOS-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192118#comment-15192118
]
Yong Tang commented on MESOS-4906:
--
Hi [~mcypark] just added a review request:
https://reviews.apache.org/r/44758/
Please let me know if there are any issues.
> Upgrade to clang-format-3.8.
>
>
> Key: MESOS-4906
> URL: https://issues.apache.org/jira/browse/MESOS-4906
> Project: Mesos
> Issue Type: Task
> Components: technical debt
>Reporter: Michael Park
>Assignee: Yong Tang
>
> The newly introduced {{AlignAfterOpenBracket: AlwaysBreak}} option in
> {{clang-format-3.8}} closes the largest gap we have between ClangFormat and
> our style guide. That is, avoiding "jaggedness" in function calls. This is a
> big win, and is definitely worth migrating for.
> As part of this ticket, we should:
> 1. Announce to the dev list that our default {{clang-format}} configuration,
> as well as the recommended version is being upgraded.
> 2. Update the {{clang-format}} configuration.
> 3. Update the
> [ClangFormat|http://mesos.apache.org/documentation/latest/clang-format/]
> documentation for Mesos
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4355) Implement isolator for Docker volume
[
https://issues.apache.org/jira/browse/MESOS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192115#comment-15192115
]
Guangya Liu commented on MESOS-4355:
Yes, it should support all external storage drivers from here
https://github.com/docker/docker/blob/master/docs/extend/plugins.md
> Implement isolator for Docker volume
>
>
> Key: MESOS-4355
> URL: https://issues.apache.org/jira/browse/MESOS-4355
> Project: Mesos
> Issue Type: Improvement
> Components: docker, isolation
>Reporter: Qian Zhang
>Assignee: Guangya Liu
>
> In Docker, user can create a volume with Docker CLI, e.g., {{docker volume
> create --name my-volume}}, we need to implement an isolator to make the
> container launched by MesosContainerizer can use such volume.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-4906) Upgrade to clang-format-3.8.
[
https://issues.apache.org/jira/browse/MESOS-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yong Tang reassigned MESOS-4906:
Assignee: Yong Tang
> Upgrade to clang-format-3.8.
>
>
> Key: MESOS-4906
> URL: https://issues.apache.org/jira/browse/MESOS-4906
> Project: Mesos
> Issue Type: Task
> Components: technical debt
>Reporter: Michael Park
>Assignee: Yong Tang
>
> The newly introduced {{AlignAfterOpenBracket: AlwaysBreak}} option in
> {{clang-format-3.8}} closes the largest gap we have between ClangFormat and
> our style guide. That is, avoiding "jaggedness" in function calls. This is a
> big win, and is definitely worth migrating for.
> As part of this ticket, we should:
> 1. Announce to the dev list that our default {{clang-format}} configuration,
> as well as the recommended version is being upgraded.
> 2. Update the {{clang-format}} configuration.
> 3. Update the
> [ClangFormat|http://mesos.apache.org/documentation/latest/clang-format/]
> documentation for Mesos
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4447) Renamed reserved() API to reservations()
[
https://issues.apache.org/jira/browse/MESOS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangya Liu updated MESOS-4447:
---
Description:
There are some problems for current {{reserve}} API. The problem is as
following:
{code}
hashmap Resources::reserved() const
{
hashmap result;
foreach (const Resource& resource, resources) {
if (isReserved(resource)) {
result[resource.role()] += resource;
}
}
return result;
}
Resources Resources::reserved(const string& role) const
{
return filter(lambda::bind(isReserved, lambda::_1, role));
}
bool Resources::isReserved(
const Resource& resource,
const Option& role)
{
if (role.isSome()) {
return !isUnreserved(resource) && role.get() == resource.role();
} else {
return !isUnreserved(resource);
}
}
{code}
This caused the {{reserved(const string& role) }} has no chance to transfer a
None() parameter to get all reserved resources in flatten mode.
The solution is rename {{reserved()}} to {{reservations}}
was:
There are some problems for current {{reserve}} API. The problem is as
following:
{code}
hashmap Resources::reserved() const
{
hashmap result;
foreach (const Resource& resource, resources) {
if (isReserved(resource)) {
result[resource.role()] += resource;
}
}
return result;
}
Resources Resources::reserved(const string& role) const
{
return filter(lambda::bind(isReserved, lambda::_1, role));
}
bool Resources::isReserved(
const Resource& resource,
const Option& role)
{
if (role.isSome()) {
return !isUnreserved(resource) && role.get() == resource.role();
} else {
return !isUnreserved(resource);
}
}
{code}
This caused the {{reserved(const string& role) }} has no chance to transfer a
None() parameter to get all reserved resources in flatten mode.
The solution is remove {{reserved()}} and update {{reserved(const string& role)
}} to {{reserved(const Option& role = None()) }}
> Renamed reserved() API to reservations()
>
>
> Key: MESOS-4447
> URL: https://issues.apache.org/jira/browse/MESOS-4447
> Project: Mesos
> Issue Type: Bug
>Reporter: Guangya Liu
>Assignee: Guangya Liu
>
> There are some problems for current {{reserve}} API. The problem is as
> following:
> {code}
> hashmap Resources::reserved() const
> {
> hashmap result;
> foreach (const Resource& resource, resources) {
> if (isReserved(resource)) {
> result[resource.role()] += resource;
> }
> }
> return result;
> }
> Resources Resources::reserved(const string& role) const
> {
> return filter(lambda::bind(isReserved, lambda::_1, role));
> }
> bool Resources::isReserved(
> const Resource& resource,
> const Option& role)
> {
> if (role.isSome()) {
> return !isUnreserved(resource) && role.get() == resource.role();
> } else {
> return !isUnreserved(resource);
> }
> }
> {code}
> This caused the {{reserved(const string& role) }} has no chance to transfer a
> None() parameter to get all reserved resources in flatten mode.
> The solution is rename {{reserved()}} to {{reservations}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4447) Renamed reserved() API to reservations()
[
https://issues.apache.org/jira/browse/MESOS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangya Liu updated MESOS-4447:
---
Summary: Renamed reserved() API to reservations() (was: Updated reserved()
API)
> Renamed reserved() API to reservations()
>
>
> Key: MESOS-4447
> URL: https://issues.apache.org/jira/browse/MESOS-4447
> Project: Mesos
> Issue Type: Bug
>Reporter: Guangya Liu
>Assignee: Guangya Liu
>
> There are some problems for current {{reserve}} API. The problem is as
> following:
> {code}
> hashmap Resources::reserved() const
> {
> hashmap result;
> foreach (const Resource& resource, resources) {
> if (isReserved(resource)) {
> result[resource.role()] += resource;
> }
> }
> return result;
> }
> Resources Resources::reserved(const string& role) const
> {
> return filter(lambda::bind(isReserved, lambda::_1, role));
> }
> bool Resources::isReserved(
> const Resource& resource,
> const Option& role)
> {
> if (role.isSome()) {
> return !isUnreserved(resource) && role.get() == resource.role();
> } else {
> return !isUnreserved(resource);
> }
> }
> {code}
> This caused the {{reserved(const string& role) }} has no chance to transfer a
> None() parameter to get all reserved resources in flatten mode.
> The solution is remove {{reserved()}} and update {{reserved(const string&
> role) }} to {{reserved(const Option& role = None()) }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4923) Add a new sorter for revocable resources in allocator
Guangya Liu created MESOS-4923:
--
Summary: Add a new sorter for revocable resources in allocator
Key: MESOS-4923
URL: https://issues.apache.org/jira/browse/MESOS-4923
Project: Mesos
Issue Type: Bug
Reporter: Guangya Liu
The current logic of roleSorter is that when it do role sorter, the resources
in it will include both regular resources and revocable resources, and this may
not accurate for some cases, take the following case as an instance:
1) framework1 and framework2.
2) framework1 got 1 reserved cpu and 9 revocable cpu. cpu(r1):1;cpu(*){REV}:9
3) framework2 got 9 reserved cpus: cpu(r1):9
When allocator allocate resources in next cycle, framework2 will be handled
first as it has less SCALAR resources than framework1, but this may not be
right for some cases as framework1 is using only 1 reserved resources and other
resources are revocable which can be easily got evicted.
A proposal here is introducing a new sorter for revocable resources so as to
distinguish the sorter for regular resources and revocable resources. To the
built in allocator, the logic would be as this:
1) Quota Role Sorter
2) non-revocable Role Sorter
3) Revocable Role Sorter
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4858) Make changes to executor v1 library around managing connections.
[
https://issues.apache.org/jira/browse/MESOS-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-4858:
--
Fix Version/s: (was: 0.28.0)
0.29.0
> Make changes to executor v1 library around managing connections.
>
>
> Key: MESOS-4858
> URL: https://issues.apache.org/jira/browse/MESOS-4858
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
> Fix For: 0.29.0
>
>
> While implementing pipelining changes for the scheduler library (MESOS-3570),
> we noticed a couple of small bugs that we would like to fix in the executor
> library:
> - Don't pass {{Connection}} objects to {{defer}} callbacks as they can
> sometimes lead to deadlocks.
> - Minor cleanups around not accepting {{SUBSCRIBE}} call if one is currently
> in progress.
> - Create a random UUID (connectionId) before we initiate a connection to the
> agent, as in some scenarios, we can accept connection attempts from stale
> connections.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4922) Setup proper /etc/hostname and /etc/hosts for containers in network/cni isolator.
Qian Zhang created MESOS-4922: - Summary: Setup proper /etc/hostname and /etc/hosts for containers in network/cni isolator. Key: MESOS-4922 URL: https://issues.apache.org/jira/browse/MESOS-4922 Project: Mesos Issue Type: Bug Components: isolation Reporter: Qian Zhang Assignee: Qian Zhang The network/cni isolator needs to properly setup /etc/hostname and /etc/hosts for the container with a hostname (e.g., randomly generated) and the assigned IP returned by CNI plugin. We should consider the following cases: 1) container is using host filesystem 2) container is using a different filesystem 3) custom executor and command executor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4629) Implement fault tolerance tests for the HTTP Scheduler API.
[
https://issues.apache.org/jira/browse/MESOS-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-4629:
--
Sprint: Mesosphere Sprint 31
> Implement fault tolerance tests for the HTTP Scheduler API.
> ---
>
> Key: MESOS-4629
> URL: https://issues.apache.org/jira/browse/MESOS-4629
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
>
> Currently, the HTTP V1 API does not have fault tolerance tests similar to the
> one in {{src/tests/fault_tolerance_tests.cpp}}.
> For more information see MESOS-3355.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4630) Implement partition tests for the HTTP Scheduler API.
[ https://issues.apache.org/jira/browse/MESOS-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-4630: -- Sprint: Mesosphere Sprint 31 > Implement partition tests for the HTTP Scheduler API. > - > > Key: MESOS-4630 > URL: https://issues.apache.org/jira/browse/MESOS-4630 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar > Labels: mesosphere > > Currently, the HTTP V1 API does not have partition tests similar to the one > in src/tests/partition_tests.cpp. > For more information see MESOS-3355. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-4629) Implement fault tolerance tests for the HTTP Scheduler API.
[
https://issues.apache.org/jira/browse/MESOS-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar reassigned MESOS-4629:
-
Assignee: Anand Mazumdar (was: Shuai Lin)
> Implement fault tolerance tests for the HTTP Scheduler API.
> ---
>
> Key: MESOS-4629
> URL: https://issues.apache.org/jira/browse/MESOS-4629
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
>
> Currently, the HTTP V1 API does not have fault tolerance tests similar to the
> one in {{src/tests/fault_tolerance_tests.cpp}}.
> For more information see MESOS-3355.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
