[jira] [Updated] (MESOS-5515) Implement READ_FILE Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-5515: -- Shepherd: Anand Mazumdar (was: Vinod Kone) > Implement READ_FILE Call in v1 agent API. > - > > Key: MESOS-5515 > URL: https://issues.apache.org/jira/browse/MESOS-5515 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: zhou xing > Fix For: 1.1.0 > > > Review Requests submitted: > https://reviews.apache.org/r/49242/ > https://reviews.apache.org/r/49243/ > https://reviews.apache.org/r/49244/ > https://reviews.apache.org/r/49245/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5465) Container image as a volume source should also include image manifest.
[ https://issues.apache.org/jira/browse/MESOS-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368742#comment-15368742 ] Gilbert Song commented on MESOS-5465: - Understand your proposal. You want to modify the rootfs a little bit to include the manifest file. It is a solution, but just seems a liitle not ideal to me, since the container can do anything in its rootfs, include erasing any file on purpose or by some other behavior. We may not want to make any change to the rootfs. I am currently thinking handle the manifest in diff cases. If the container path is a relative path, we can just write it to the sandbox. If it is the an absolute path, we need to do a --ready-only mount as a special case. This would include some refactoring in our code. A discussion is absolutely welcome. > Container image as a volume source should also include image manifest. > -- > > Key: MESOS-5465 > URL: https://issues.apache.org/jira/browse/MESOS-5465 > Project: Mesos > Issue Type: Bug >Reporter: Jie Yu >Assignee: Guangya Liu > > Currently, if a user specifies the source of a volume to be an image (e.g., > Docker image), we only prepare the rootfs and mount it at 'container_path' in > the container. > However, the rootfs itself is not sufficient to allow the executor to launch > the docker container. We need the docker manifest as well to get the env, > entry point, cmd information. > One solutions is to make container_path a directory containing two things: 1) > rootfs, 2) manifest. But this is a breaking change, we might need to > introduce a deprecation cycle for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5812) MasterAPITest.Subscribe is flaky
[
https://issues.apache.org/jira/browse/MESOS-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368733#comment-15368733
]
Anand Mazumdar commented on MESOS-5812:
---
Fix for one of the issues: https://reviews.apache.org/r/49837
> MasterAPITest.Subscribe is flaky
>
>
> Key: MESOS-5812
> URL: https://issues.apache.org/jira/browse/MESOS-5812
> Project: Mesos
> Issue Type: Bug
> Components: tests
> Environment: mac os X
> centos 7
>Reporter: Zhitao Li
>
> This test seems to be flaky, although on Mac OS X and CentOS 7 the error a
> bit different.
> On Mac OS X:
> {noformat}[ RUN ] ContentType/MasterAPITest.Subscribe/0
> I0708 11:42:48.474665 1927435008 cluster.cpp:155] Creating default 'local'
> authorizer
> I0708 11:42:48.480677 1927435008 leveldb.cpp:174] Opened db in 5727us
> I0708 11:42:48.481494 1927435008 leveldb.cpp:181] Compacted db in 722us
> I0708 11:42:48.481541 1927435008 leveldb.cpp:196] Created db iterator in 19us
> I0708 11:42:48.481572 1927435008 leveldb.cpp:202] Seeked to beginning of db
> in 9us
> I0708 11:42:48.481587 1927435008 leveldb.cpp:271] Iterated through 0 keys in
> the db in 7us
> I0708 11:42:48.481617 1927435008 replica.cpp:779] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0708 11:42:48.482030 350982144 recover.cpp:451] Starting replica recovery
> I0708 11:42:48.482203 350982144 recover.cpp:477] Replica is in EMPTY status
> I0708 11:42:48.484107 348299264 replica.cpp:673] Replica in EMPTY status
> received a broadcasted recover request from (3780)@127.0.0.1:50325
> I0708 11:42:48.484318 350982144 recover.cpp:197] Received a recover response
> from a replica in EMPTY status
> I0708 11:42:48.484750 348835840 master.cpp:382] Master
> e055d60c-05ff-487e-82da-d0a43e52605c (localhost) started on 127.0.0.1:50325
> I0708 11:42:48.484850 349908992 recover.cpp:568] Updating replica status to
> STARTING
> I0708 11:42:48.484788 348835840 master.cpp:384] Flags at startup: --acls=""
> --agent_ping_timeout="15secs" --agent_reregister_timeout="10mins"
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate_agents="true" --authenticate_frameworks="true"
> --authenticate_http="true" --authenticate_http_frameworks="true"
> --authenticators="crammd5" --authorizers="local"
> --credentials="/private/tmp/Sn2Kf4/credentials" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --http_authenticators="basic"
> --http_framework_authenticators="basic" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_agent_ping_timeouts="5" --max_completed_frameworks="50"
> --max_completed_tasks_per_framework="1000" --quiet="false"
> --recovery_agent_removal_limit="100%" --registry="replicated_log"
> --registry_fetch_timeout="1mins" --registry_store_timeout="100secs"
> --registry_strict="true" --root_submissions="true" --user_sorter="drf"
> --version="false" --webui_dir="/usr/local/share/mesos/webui"
> --work_dir="/private/tmp/Sn2Kf4/master" --zk_session_timeout="10secs"
> W0708 11:42:48.485263 348835840 master.cpp:387]
> **
> Master bound to loopback interface! Cannot communicate with remote schedulers
> or agents. You might want to set '--ip' flag to a routable IP address.
> **
> I0708 11:42:48.485291 348835840 master.cpp:434] Master only allowing
> authenticated frameworks to register
> I0708 11:42:48.485314 348835840 master.cpp:448] Master only allowing
> authenticated agents to register
> I0708 11:42:48.485335 348835840 master.cpp:461] Master only allowing
> authenticated HTTP frameworks to register
> I0708 11:42:48.485347 348835840 credentials.hpp:37] Loading credentials for
> authentication from '/private/tmp/Sn2Kf4/credentials'
> I0708 11:42:48.485373 349372416 leveldb.cpp:304] Persisting metadata (8
> bytes) to leveldb took 397us
> I0708 11:42:48.485414 349372416 replica.cpp:320] Persisted replica status to
> STARTING
> I0708 11:42:48.485608 350982144 recover.cpp:477] Replica is in STARTING status
> I0708 11:42:48.485749 348835840 master.cpp:506] Using default 'crammd5'
> authenticator
> I0708 11:42:48.485852 348835840 master.cpp:578] Using default 'basic' HTTP
> authenticator
> I0708 11:42:48.486018 348835840 master.cpp:658] Using default 'basic' HTTP
> framework authenticator
> I0708 11:42:48.486140 348835840 master.cpp:705] Authorization enabled
> I0708 11:42:48.486486 350982144 replica.cpp:673] Replica in STARTING status
> received a broadcasted recover request from (3783)@127.0.0.1:50325
> I0708 11:42:48.486758 352055296 recover.cpp:197] Received a recover response
> from a replica in STARTING status
> I0708 11:42:48.487176 350982144 recover.cpp:568] Updating
[jira] [Commented] (MESOS-5825) Support mounting image volume in mesos containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368712#comment-15368712 ] Gilbert Song commented on MESOS-5825: - Thanks for reminding this. Sorry I miss the existed ticket. > Support mounting image volume in mesos containerizer. > - > > Key: MESOS-5825 > URL: https://issues.apache.org/jira/browse/MESOS-5825 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Gilbert Song >Assignee: Gilbert Song > Labels: containerizer, filesystem, isolator, mesosphere > > Mesos containerizer should be able to support mounting image volume type. > Specifically, both image rootfs and default manifest should be reachable > inside container's mount namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5825) Support mounting image volume in mesos containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368671#comment-15368671 ] Guangya Liu commented on MESOS-5825: [~gilbert] is this duplicate with https://issues.apache.org/jira/browse/MESOS-5465 ? If so, can you please post some comments at MESOS-5465? ;-) > Support mounting image volume in mesos containerizer. > - > > Key: MESOS-5825 > URL: https://issues.apache.org/jira/browse/MESOS-5825 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Gilbert Song >Assignee: Gilbert Song > Labels: containerizer, filesystem, isolator, mesosphere > > Mesos containerizer should be able to support mounting image volume type. > Specifically, both image rootfs and default manifest should be reachable > inside container's mount namespace. -- 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=15368666#comment-15368666
]
Guangya Liu commented on MESOS-5700:
Based on investigation from [~jvanremoortere] and [~mcypark] , the founding is
that (1) copying of the protobufs was expensive (2) looping over and checking
.name() equality was expensive, for example. We may need to think more use
cases related to {{Resource}} and translate those to benchmark test.
> 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] [Updated] (MESOS-5824) Include disk source information in stringification
[
https://issues.apache.org/jira/browse/MESOS-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Harper updated MESOS-5824:
--
Attachment: 0001-Output-disk-resource-source-information.patch
Attached is the patch
> Include disk source information in stringification
> --
>
> Key: MESOS-5824
> URL: https://issues.apache.org/jira/browse/MESOS-5824
> Project: Mesos
> Issue Type: Improvement
> Components: stout
>Affects Versions: 0.28.2
>Reporter: Tim Harper
> Fix For: 0.28.3
>
> Attachments: 0001-Output-disk-resource-source-information.patch
>
>
> Some frameworks (like kafka_mesos) ignore the Source field when trying to
> reserve an offered mount or path persistent volume; the resulting error
> message is bewildering:
> {code:none}
> Task uses more resources
> cpus(*):4; mem(*):4096; ports(*):[31000-31000]; disk(kafka,
> kafka)[kafka_0:data]:960679
> than available
> cpus(*):32; mem(*):256819; ports(*):[31000-32000]; disk(kafka,
> kafka)[kafka_0:data]:960679; disk(*):240169;
> {code}
> The stringification of disk resources should include source information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5825) Support mounting image volume in mesos containerizer.
Gilbert Song created MESOS-5825: --- Summary: Support mounting image volume in mesos containerizer. Key: MESOS-5825 URL: https://issues.apache.org/jira/browse/MESOS-5825 Project: Mesos Issue Type: Improvement Components: containerization Reporter: Gilbert Song Assignee: Gilbert Song Mesos containerizer should be able to support mounting image volume type. Specifically, both image rootfs and default manifest should be reachable inside container's mount namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5823) Include disk source information in stringification
Tim Harper created MESOS-5823:
-
Summary: Include disk source information in stringification
Key: MESOS-5823
URL: https://issues.apache.org/jira/browse/MESOS-5823
Project: Mesos
Issue Type: Improvement
Components: stout
Affects Versions: 0.28.2
Reporter: Tim Harper
Fix For: 0.28.3
Some frameworks (like kafka_mesos) ignore the Source field when trying to
reserve an offered mount or path persistent volume; the resulting error message
is bewildering:
{code:none}
Task uses more resources
cpus(*):4; mem(*):4096; ports(*):[31000-31000]; disk(kafka,
kafka)[kafka_0:data]:960679
than available
cpus(*):32; mem(*):256819; ports(*):[31000-32000]; disk(kafka,
kafka)[kafka_0:data]:960679; disk(*):240169;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5824) Include disk source information in stringification
Tim Harper created MESOS-5824:
-
Summary: Include disk source information in stringification
Key: MESOS-5824
URL: https://issues.apache.org/jira/browse/MESOS-5824
Project: Mesos
Issue Type: Improvement
Components: stout
Affects Versions: 0.28.2
Reporter: Tim Harper
Fix For: 0.28.3
Some frameworks (like kafka_mesos) ignore the Source field when trying to
reserve an offered mount or path persistent volume; the resulting error message
is bewildering:
{code:none}
Task uses more resources
cpus(*):4; mem(*):4096; ports(*):[31000-31000]; disk(kafka,
kafka)[kafka_0:data]:960679
than available
cpus(*):32; mem(*):256819; ports(*):[31000-32000]; disk(kafka,
kafka)[kafka_0:data]:960679; disk(*):240169;
{code}
The stringification of disk resources should include source information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5388) MesosContainerizerLaunch flags execute arbitrary commands via shell
[ https://issues.apache.org/jira/browse/MESOS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-5388: -- Shepherd: Jie Yu Sprint: Mesosphere Sprint 39 Story Points: 3 > MesosContainerizerLaunch flags execute arbitrary commands via shell > --- > > Key: MESOS-5388 > URL: https://issues.apache.org/jira/browse/MESOS-5388 > Project: Mesos > Issue Type: Bug >Reporter: James DeFelice >Assignee: Gilbert Song > Labels: mesosphere, security > > For example, the docker volume isolator's containerPath is appended (without > sanitation) to a command that's executed in this manner. As such, it's > possible to inject arbitrary shell commands to be executed by mesos. > https://github.com/apache/mesos/blob/17260204c833c643adf3d8f36ad8a1a606ece809/src/slave/containerizer/mesos/launch.cpp#L206 > Perhaps instead of strings these commands could/should be sent as string > arrays that could be passed as argv arguments w/o shell interpretation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5388) MesosContainerizerLaunch flags execute arbitrary commands via shell
[ https://issues.apache.org/jira/browse/MESOS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-5388: -- Assignee: Gilbert Song > MesosContainerizerLaunch flags execute arbitrary commands via shell > --- > > Key: MESOS-5388 > URL: https://issues.apache.org/jira/browse/MESOS-5388 > Project: Mesos > Issue Type: Bug >Reporter: James DeFelice >Assignee: Gilbert Song > Labels: mesosphere, security > > For example, the docker volume isolator's containerPath is appended (without > sanitation) to a command that's executed in this manner. As such, it's > possible to inject arbitrary shell commands to be executed by mesos. > https://github.com/apache/mesos/blob/17260204c833c643adf3d8f36ad8a1a606ece809/src/slave/containerizer/mesos/launch.cpp#L206 > Perhaps instead of strings these commands could/should be sent as string > arrays that could be passed as argv arguments w/o shell interpretation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5822) Add a build script for the Windows CI
Joseph Wu created MESOS-5822: Summary: Add a build script for the Windows CI Key: MESOS-5822 URL: https://issues.apache.org/jira/browse/MESOS-5822 Project: Mesos Issue Type: Improvement Components: build Reporter: Joseph Wu Assignee: Joseph Wu The ASF CI for Mesos runs a script that lives inside the Mesos codebase: https://github.com/apache/mesos/blob/1cbfdc3c1e4b8498a67f8531ab264003c8c19fb1/support/docker_build.sh ASF Infrastructure have set up a machine that we can use for building Mesos on Windows. Considering the environment, we will need a separate script to build here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5812) MasterAPITest.Subscribe is flaky
[
https://issues.apache.org/jira/browse/MESOS-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368516#comment-15368516
]
Zhitao Li commented on MESOS-5812:
--
Updated snippet of Mac OS part, to reflect log for the first failure.
> MasterAPITest.Subscribe is flaky
>
>
> Key: MESOS-5812
> URL: https://issues.apache.org/jira/browse/MESOS-5812
> Project: Mesos
> Issue Type: Bug
> Components: tests
> Environment: mac os X
> centos 7
>Reporter: Zhitao Li
>
> This test seems to be flaky, although on Mac OS X and CentOS 7 the error a
> bit different.
> On Mac OS X:
> {noformat}[ RUN ] ContentType/MasterAPITest.Subscribe/0
> I0708 11:42:48.474665 1927435008 cluster.cpp:155] Creating default 'local'
> authorizer
> I0708 11:42:48.480677 1927435008 leveldb.cpp:174] Opened db in 5727us
> I0708 11:42:48.481494 1927435008 leveldb.cpp:181] Compacted db in 722us
> I0708 11:42:48.481541 1927435008 leveldb.cpp:196] Created db iterator in 19us
> I0708 11:42:48.481572 1927435008 leveldb.cpp:202] Seeked to beginning of db
> in 9us
> I0708 11:42:48.481587 1927435008 leveldb.cpp:271] Iterated through 0 keys in
> the db in 7us
> I0708 11:42:48.481617 1927435008 replica.cpp:779] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0708 11:42:48.482030 350982144 recover.cpp:451] Starting replica recovery
> I0708 11:42:48.482203 350982144 recover.cpp:477] Replica is in EMPTY status
> I0708 11:42:48.484107 348299264 replica.cpp:673] Replica in EMPTY status
> received a broadcasted recover request from (3780)@127.0.0.1:50325
> I0708 11:42:48.484318 350982144 recover.cpp:197] Received a recover response
> from a replica in EMPTY status
> I0708 11:42:48.484750 348835840 master.cpp:382] Master
> e055d60c-05ff-487e-82da-d0a43e52605c (localhost) started on 127.0.0.1:50325
> I0708 11:42:48.484850 349908992 recover.cpp:568] Updating replica status to
> STARTING
> I0708 11:42:48.484788 348835840 master.cpp:384] Flags at startup: --acls=""
> --agent_ping_timeout="15secs" --agent_reregister_timeout="10mins"
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate_agents="true" --authenticate_frameworks="true"
> --authenticate_http="true" --authenticate_http_frameworks="true"
> --authenticators="crammd5" --authorizers="local"
> --credentials="/private/tmp/Sn2Kf4/credentials" --framework_sorter="drf"
> --help="false" --hostname_lookup="true" --http_authenticators="basic"
> --http_framework_authenticators="basic" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_agent_ping_timeouts="5" --max_completed_frameworks="50"
> --max_completed_tasks_per_framework="1000" --quiet="false"
> --recovery_agent_removal_limit="100%" --registry="replicated_log"
> --registry_fetch_timeout="1mins" --registry_store_timeout="100secs"
> --registry_strict="true" --root_submissions="true" --user_sorter="drf"
> --version="false" --webui_dir="/usr/local/share/mesos/webui"
> --work_dir="/private/tmp/Sn2Kf4/master" --zk_session_timeout="10secs"
> W0708 11:42:48.485263 348835840 master.cpp:387]
> **
> Master bound to loopback interface! Cannot communicate with remote schedulers
> or agents. You might want to set '--ip' flag to a routable IP address.
> **
> I0708 11:42:48.485291 348835840 master.cpp:434] Master only allowing
> authenticated frameworks to register
> I0708 11:42:48.485314 348835840 master.cpp:448] Master only allowing
> authenticated agents to register
> I0708 11:42:48.485335 348835840 master.cpp:461] Master only allowing
> authenticated HTTP frameworks to register
> I0708 11:42:48.485347 348835840 credentials.hpp:37] Loading credentials for
> authentication from '/private/tmp/Sn2Kf4/credentials'
> I0708 11:42:48.485373 349372416 leveldb.cpp:304] Persisting metadata (8
> bytes) to leveldb took 397us
> I0708 11:42:48.485414 349372416 replica.cpp:320] Persisted replica status to
> STARTING
> I0708 11:42:48.485608 350982144 recover.cpp:477] Replica is in STARTING status
> I0708 11:42:48.485749 348835840 master.cpp:506] Using default 'crammd5'
> authenticator
> I0708 11:42:48.485852 348835840 master.cpp:578] Using default 'basic' HTTP
> authenticator
> I0708 11:42:48.486018 348835840 master.cpp:658] Using default 'basic' HTTP
> framework authenticator
> I0708 11:42:48.486140 348835840 master.cpp:705] Authorization enabled
> I0708 11:42:48.486486 350982144 replica.cpp:673] Replica in STARTING status
> received a broadcasted recover request from (3783)@127.0.0.1:50325
> I0708 11:42:48.486758 352055296 recover.cpp:197] Received a recover response
> from a replica in STARTING status
> I0708 11:42:48.487176 350982144 recover.cpp:568] Updating
[jira] [Updated] (MESOS-5821) Clean up the billions of compiler warnings on MSVC
[
https://issues.apache.org/jira/browse/MESOS-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-5821:
-
Description: Clean builds of Mesos on Windows will result in approximately
{{5800 Warning(s)}} or more.
> Clean up the billions of compiler warnings on MSVC
> --
>
> Key: MESOS-5821
> URL: https://issues.apache.org/jira/browse/MESOS-5821
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Alex Clemmer
>Assignee: Alex Clemmer
> Labels: mesosphere, slave
>
> Clean builds of Mesos on Windows will result in approximately {{5800
> Warning(s)}} or more.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5821) Clean up the billions of compiler warnings on MSVC
Alex Clemmer created MESOS-5821: --- Summary: Clean up the billions of compiler warnings on MSVC Key: MESOS-5821 URL: https://issues.apache.org/jira/browse/MESOS-5821 Project: Mesos Issue Type: Bug Components: slave Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5820) Investigate porting master; develop time estimates
Alex Clemmer created MESOS-5820: --- Summary: Investigate porting master; develop time estimates Key: MESOS-5820 URL: https://issues.apache.org/jira/browse/MESOS-5820 Project: Mesos Issue Type: Bug Components: master Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5817) Port libprocess process_tests.cpp
Alex Clemmer created MESOS-5817: --- Summary: Port libprocess process_tests.cpp Key: MESOS-5817 URL: https://issues.apache.org/jira/browse/MESOS-5817 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5818) Port libprocess reap_tests.cpp
Alex Clemmer created MESOS-5818: --- Summary: Port libprocess reap_tests.cpp Key: MESOS-5818 URL: https://issues.apache.org/jira/browse/MESOS-5818 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5819) Port libprocess sequence_tests.cpp
Alex Clemmer created MESOS-5819: --- Summary: Port libprocess sequence_tests.cpp Key: MESOS-5819 URL: https://issues.apache.org/jira/browse/MESOS-5819 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5815) Port libprocess io_tests.cpp
Alex Clemmer created MESOS-5815: --- Summary: Port libprocess io_tests.cpp Key: MESOS-5815 URL: https://issues.apache.org/jira/browse/MESOS-5815 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5816) Port libprocess metrics_tests.cpp
Alex Clemmer created MESOS-5816: --- Summary: Port libprocess metrics_tests.cpp Key: MESOS-5816 URL: https://issues.apache.org/jira/browse/MESOS-5816 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5814) Port libprocess http_tests.cpp
Alex Clemmer created MESOS-5814: --- Summary: Port libprocess http_tests.cpp Key: MESOS-5814 URL: https://issues.apache.org/jira/browse/MESOS-5814 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5813) Port stout tests to Windows
Artem Harutyunyan created MESOS-5813: Summary: Port stout tests to Windows Key: MESOS-5813 URL: https://issues.apache.org/jira/browse/MESOS-5813 Project: Mesos Issue Type: Epic Reporter: Artem Harutyunyan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3668) Port process/delay.hpp to Windows
[ https://issues.apache.org/jira/browse/MESOS-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368406#comment-15368406 ] Artem Harutyunyan commented on MESOS-3668: -- This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > Port process/delay.hpp to Windows > - > > Key: MESOS-3668 > URL: https://issues.apache.org/jira/browse/MESOS-3668 > Project: Mesos > Issue Type: Task > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, windows > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4972) Implement `os::rename`
[ https://issues.apache.org/jira/browse/MESOS-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4972: - Affects Version/s: 1.0.0 This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > Implement `os::rename` > -- > > Key: MESOS-4972 > URL: https://issues.apache.org/jira/browse/MESOS-4972 > Project: Mesos > Issue Type: Bug > Components: stout >Affects Versions: 1.0.0 >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, windows-mvp > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3685) Port process/io.hpp to Windows
[ https://issues.apache.org/jira/browse/MESOS-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-3685: - Fix Version/s: 1.0.0 Description: This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > Port process/io.hpp to Windows > -- > > Key: MESOS-3685 > URL: https://issues.apache.org/jira/browse/MESOS-3685 > Project: Mesos > Issue Type: Task > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, windows > Fix For: 1.0.0 > > > This was resolved over many commits leading up to review: > https://reviews.apache.org/r/48000/ at revision: > 6e199cc255cbf561fac575568b0594ac2b2c14f9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3737) `limiter.hpp` causes template specialization error on Windows 10/MSVC 1900
[ https://issues.apache.org/jira/browse/MESOS-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-3737: - Fix Version/s: 1.0.0 This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > `limiter.hpp` causes template specialization error on Windows 10/MSVC 1900 > -- > > Key: MESOS-3737 > URL: https://issues.apache.org/jira/browse/MESOS-3737 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: libprocess, mesosphere > Fix For: 1.0.0 > > > Manifests most clearly when you change `src/CMakeLists.txt` to compile > `monitor.cpp`. You get an error like this: > ``` > Severity CodeDescription Project FileLine > Error C2893 Failed to specialize function template 'unknown-type > std::invoke(_Callable &&,_Types &&...)'mesos-0.26.0C:\Program Files > (x86)\Microsoft Visual Studio 14.0\VC\include\type_traits 1529 > ``` > When you investigate you see that actually the error seems to come the > 3-argument `defer` call in `RateLimiterProcess::acquire` (which is in > `process/limiter.hpp`). If I'm not mistaken, that is one of the calls that > are created with the preprocessor in `defer.hpp`. > We will need to resolve this for (among other things) the monitor to move > forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4464) Implement cpu count facilities on Windows
[ https://issues.apache.org/jira/browse/MESOS-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368371#comment-15368371 ] Artem Harutyunyan commented on MESOS-4464: -- This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9. > Implement cpu count facilities on Windows > - > > Key: MESOS-4464 > URL: https://issues.apache.org/jira/browse/MESOS-4464 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4464) Implement cpu count facilities on Windows
[ https://issues.apache.org/jira/browse/MESOS-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4464: - Fix Version/s: 1.0.0 > Implement cpu count facilities on Windows > - > > Key: MESOS-4464 > URL: https://issues.apache.org/jira/browse/MESOS-4464 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4469) Implement memory querying in Windows
[ https://issues.apache.org/jira/browse/MESOS-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4469: - Fix Version/s: 1.0.0 This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > Implement memory querying in Windows > > > Key: MESOS-4469 > URL: https://issues.apache.org/jira/browse/MESOS-4469 > Project: Mesos > Issue Type: Bug >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4474) Implement `sendfile` in Windows
[ https://issues.apache.org/jira/browse/MESOS-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4474: - Fix Version/s: 1.0.0 Description: This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > Implement `sendfile` in Windows > --- > > Key: MESOS-4474 > URL: https://issues.apache.org/jira/browse/MESOS-4474 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > Fix For: 1.0.0 > > > This was resolved over many commits leading up to review: > https://reviews.apache.org/r/48000/ at revision: > 6e199cc255cbf561fac575568b0594ac2b2c14f9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4972) Implement `os::rename`
[ https://issues.apache.org/jira/browse/MESOS-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4972: - Fix Version/s: 1.0.0 This was resolved over many commits leading up to review: https://reviews.apache.org/r/48000/ at revision: 6e199cc255cbf561fac575568b0594ac2b2c14f9 > Implement `os::rename` > -- > > Key: MESOS-4972 > URL: https://issues.apache.org/jira/browse/MESOS-4972 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, windows-mvp > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5428) Update the mechanism to define flags in FlagsBase derived clases
[ https://issues.apache.org/jira/browse/MESOS-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park updated MESOS-5428: Assignee: Daniel Pravat > Update the mechanism to define flags in FlagsBase derived clases > > > Key: MESOS-5428 > URL: https://issues.apache.org/jira/browse/MESOS-5428 > Project: Mesos > Issue Type: Bug >Reporter: Daniel Pravat >Assignee: Daniel Pravat > Fix For: 1.0.0 > > > If a program exeposes flags, the recommendation from Mesos was to use a > derived class from FlagsBase, add the new flags in constructor. > As benefit the new `Flags` class `inherits` all the flags from the derived > classes. > Each derived calss calls the method `add` implemented in `FlagsBase` which > uses `dynamic_cast` to set the default value and other things. > To use `FlagsBase` derived classes in Visual Studio we should disable > construction displacements using `/vd2` compile option. > More info: https://msdn.microsoft.com/en-us/library/7sf3txa8.aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5428) Update the mechanism to define flags in FlagsBase derived clases
[ https://issues.apache.org/jira/browse/MESOS-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368311#comment-15368311 ] Michael Park commented on MESOS-5428: - https://reviews.apache.org/r/47671/ > Update the mechanism to define flags in FlagsBase derived clases > > > Key: MESOS-5428 > URL: https://issues.apache.org/jira/browse/MESOS-5428 > Project: Mesos > Issue Type: Bug >Reporter: Daniel Pravat > > If a program exeposes flags, the recommendation from Mesos was to use a > derived class from FlagsBase, add the new flags in constructor. > As benefit the new `Flags` class `inherits` all the flags from the derived > classes. > Each derived calss calls the method `add` implemented in `FlagsBase` which > uses `dynamic_cast` to set the default value and other things. > To use `FlagsBase` derived classes in Visual Studio we should disable > construction displacements using `/vd2` compile option. > More info: https://msdn.microsoft.com/en-us/library/7sf3txa8.aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-905) Remove Framework.id in favor of FrameworkInfo.id
[ https://issues.apache.org/jira/browse/MESOS-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368281#comment-15368281 ] Kapil Arya commented on MESOS-905: -- Oh wow, that has been lingering for a while. I'll rebase and publish new RRs. > Remove Framework.id in favor of FrameworkInfo.id > > > Key: MESOS-905 > URL: https://issues.apache.org/jira/browse/MESOS-905 > Project: Mesos > Issue Type: Story > Components: framework >Reporter: Adam B >Assignee: Kapil Arya > Labels: mesosphere > > Framework.id currently holds the correct FrameworkId, but Framework also > contains a FrameworkInfo, and the FrameworkInfo.id is not necessarily set. > I propose that we eliminate the Framework.id member variable and replace it > with a Framework.id() accessor that references Framework.FrameworkInfo.id and > ensure that it is correctly set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5812) MasterAPITest.Subscribe is flaky
Zhitao Li created MESOS-5812:
Summary: MasterAPITest.Subscribe is flaky
Key: MESOS-5812
URL: https://issues.apache.org/jira/browse/MESOS-5812
Project: Mesos
Issue Type: Bug
Components: tests
Environment: mac os X
centos 7
Reporter: Zhitao Li
This test seems to be flaky, although on Mac OS X and CentOS 7 the error a bit
different.
On Mac OS X:
{noformat}
[==] Running 2 tests from 1 test case.
[--] Global test environment set-up.
[--] 2 tests from ContentType/MasterAPITest
[ RUN ] ContentType/MasterAPITest.Subscribe/0
I0708 11:43:18.712148 1927435008 cluster.cpp:155] Creating default 'local'
authorizer
I0708 11:43:18.715232 1927435008 leveldb.cpp:174] Opened db in 2825us
I0708 11:43:18.715919 1927435008 leveldb.cpp:181] Compacted db in 623us
I0708 11:43:18.715968 1927435008 leveldb.cpp:196] Created db iterator in 16us
I0708 11:43:18.715994 1927435008 leveldb.cpp:202] Seeked to beginning of db in
13us
I0708 11:43:18.716038 1927435008 leveldb.cpp:271] Iterated through 0 keys in
the db in 16us
I0708 11:43:18.716107 1927435008 replica.cpp:779] Replica recovered with log
positions 0 -> 0 with 1 holes and 0 unlearned
I0708 11:43:18.716706 351518720 recover.cpp:451] Starting replica recovery
I0708 11:43:18.716948 351518720 recover.cpp:477] Replica is in EMPTY status
I0708 11:43:18.719182 349372416 replica.cpp:673] Replica in EMPTY status
received a broadcasted recover request from (3836)@127.0.0.1:50325
I0708 11:43:18.719526 349908992 master.cpp:382] Master
538a2836-92eb-4eae-85bb-4fb1a1e3b830 (localhost) started on 127.0.0.1:50325
I0708 11:43:18.719614 348299264 recover.cpp:197] Received a recover response
from a replica in EMPTY status
I0708 11:43:18.719593 349908992 master.cpp:384] Flags at startup: --acls=""
--agent_ping_timeout="15secs" --agent_reregister_timeout="10mins"
--allocation_interval="1secs" --allocator="HierarchicalDRF"
--authenticate_agents="true" --authenticate_frameworks="true"
--authenticate_http="true" --authenticate_http_frameworks="true"
--authenticators="crammd5" --authorizers="local"
--credentials="/private/tmp/phLdfh/credentials" --framework_sorter="drf"
--help="false" --hostname_lookup="true" --http_authenticators="basic"
--http_framework_authenticators="basic" --initialize_driver_logging="true"
--log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
--max_agent_ping_timeouts="5" --max_completed_frameworks="50"
--max_completed_tasks_per_framework="1000" --quiet="false"
--recovery_agent_removal_limit="100%" --registry="replicated_log"
--registry_fetch_timeout="1mins" --registry_store_timeout="100secs"
--registry_strict="true" --root_submissions="true" --user_sorter="drf"
--version="false" --webui_dir="/usr/local/share/mesos/webui"
--work_dir="/private/tmp/phLdfh/master" --zk_session_timeout="10secs"
W0708 11:43:18.720010 349908992 master.cpp:387]
**
Master bound to loopback interface! Cannot communicate with remote schedulers
or agents. You might want to set '--ip' flag to a routable IP address.
**
I0708 11:43:18.720057 349908992 master.cpp:434] Master only allowing
authenticated frameworks to register
I0708 11:43:18.720069 349908992 master.cpp:448] Master only allowing
authenticated agents to register
I0708 11:43:18.720079 349908992 master.cpp:461] Master only allowing
authenticated HTTP frameworks to register
I0708 11:43:18.720089 349908992 credentials.hpp:37] Loading credentials for
authentication from '/private/tmp/phLdfh/credentials'
I0708 11:43:18.720237 350982144 recover.cpp:568] Updating replica status to
STARTING
I0708 11:43:18.720361 349908992 master.cpp:506] Using default 'crammd5'
authenticator
I0708 11:43:18.720690 351518720 leveldb.cpp:304] Persisting metadata (8 bytes)
to leveldb took 296us
I0708 11:43:18.720743 351518720 replica.cpp:320] Persisted replica status to
STARTING
I0708 11:43:18.720746 349908992 master.cpp:578] Using default 'basic' HTTP
authenticator
I0708 11:43:18.720927 349908992 master.cpp:658] Using default 'basic' HTTP
framework authenticator
I0708 11:43:18.720979 350982144 recover.cpp:477] Replica is in STARTING status
I0708 11:43:18.721082 349908992 master.cpp:705] Authorization enabled
I0708 11:43:18.722473 349372416 replica.cpp:673] Replica in STARTING status
received a broadcasted recover request from (3839)@127.0.0.1:50325
I0708 11:43:18.722820 349372416 recover.cpp:197] Received a recover response
from a replica in STARTING status
I0708 11:43:18.723244 352055296 recover.cpp:568] Updating replica status to
VOTING
I0708 11:43:18.723666 352055296 leveldb.cpp:304] Persisting metadata (8 bytes)
to leveldb took 243us
I0708 11:43:18.723706 349372416 master.cpp:1973] The newly elected leader is
master@127.0.0.1:50325 with id
[jira] [Updated] (MESOS-5752) ROOT_GarbageCollectorUndeletableFilesTest.BusyMountPoint is flaky
[
https://issues.apache.org/jira/browse/MESOS-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Xu updated MESOS-5752:
--
Fix Version/s: 1.1.0
> ROOT_GarbageCollectorUndeletableFilesTest.BusyMountPoint is flaky
> -
>
> Key: MESOS-5752
> URL: https://issues.apache.org/jira/browse/MESOS-5752
> Project: Mesos
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.0.0
> Environment: Centos 7
>Reporter: Jie Yu
>Assignee: Megha
> Fix For: 1.1.0
>
>
> {noformat}
> [19:17:15] : [Step 10/10] [ RUN ]
> ROOT_GarbageCollectorUndeletableFilesTest.BusyMountPoint
> [19:17:15]W: [Step 10/10] I0630 19:17:15.084791 31223 cluster.cpp:155]
> Creating default 'local' authorizer
> [19:17:15]W: [Step 10/10] I0630 19:17:15.089606 31223 leveldb.cpp:174]
> Opened db in 4.713001ms
> [19:17:15]W: [Step 10/10] I0630 19:17:15.090878 31223 leveldb.cpp:181]
> Compacted db in 1.253446ms
> [19:17:15]W: [Step 10/10] I0630 19:17:15.090898 31223 leveldb.cpp:196]
> Created db iterator in 3553ns
> [19:17:15]W: [Step 10/10] I0630 19:17:15.090903 31223 leveldb.cpp:202]
> Seeked to beginning of db in 599ns
> [19:17:15]W: [Step 10/10] I0630 19:17:15.090909 31223 leveldb.cpp:271]
> Iterated through 0 keys in the db in 364ns
> [19:17:15]W: [Step 10/10] I0630 19:17:15.090920 31223 replica.cpp:779]
> Replica recovered with log positions 0 -> 0 with 1 holes and 0 unlearned
> [19:17:15]W: [Step 10/10] I0630 19:17:15.091115 31243 recover.cpp:451]
> Starting replica recovery
> [19:17:15]W: [Step 10/10] I0630 19:17:15.091217 31242 recover.cpp:477]
> Replica is in EMPTY status
> [19:17:15]W: [Step 10/10] I0630 19:17:15.091442 31243 replica.cpp:673]
> Replica in EMPTY status received a broadcasted recover request from
> (3210)@172.30.2.172:43264
> [19:17:15]W: [Step 10/10] I0630 19:17:15.091569 31240 recover.cpp:197]
> Received a recover response from a replica in EMPTY status
> [19:17:15]W: [Step 10/10] I0630 19:17:15.091693 31241 recover.cpp:568]
> Updating replica status to STARTING
> [19:17:15]W: [Step 10/10] I0630 19:17:15.091995 31237 master.cpp:382]
> Master 9c6bf850-2a66-41f8-a0ad-13c674886778 (ip-172-30-2-172.mesosphere.io)
> started on 172.30.2.172:43264
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092010 31237 master.cpp:384] Flags
> at startup: --acls="" --agent_ping_timeout="15secs"
> --agent_reregister_timeout="10mins" --allocation_interval="1secs"
> --allocator="HierarchicalDRF" --authenticate_agents="true"
> --authenticate_frameworks="true" --authenticate_http="true"
> --authenticate_http_frameworks="true" --authenticators="crammd5"
> --authorizers="local" --credentials="/tmp/BD92iQ/credentials"
> --framework_sorter="drf" --help="false" --hostname_lookup="true"
> --http_authenticators="basic" --http_framework_authenticators="basic"
> --initialize_driver_logging="true" --log_auto_initialize="true"
> --logbufsecs="0" --logging_level="INFO" --max_agent_ping_timeouts="5"
> --max_completed_frameworks="50" --max_completed_tasks_per_framework="1000"
> --quiet="false" --recovery_agent_removal_limit="100%"
> --registry="replicated_log" --registry_fetch_timeout="1mins"
> --registry_store_timeout="100secs" --registry_strict="true"
> --root_submissions="true" --user_sorter="drf" --version="false"
> --webui_dir="/usr/local/share/mesos/webui" --work_dir="/tmp/BD92iQ/master"
> --zk_session_timeout="10secs"
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092118 31237 master.cpp:434]
> Master only allowing authenticated frameworks to register
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092123 31237 master.cpp:448]
> Master only allowing authenticated agents to register
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092126 31237 master.cpp:461]
> Master only allowing authenticated HTTP frameworks to register
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092130 31237 credentials.hpp:37]
> Loading credentials for authentication from '/tmp/BD92iQ/credentials'
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092205 31237 master.cpp:506] Using
> default 'crammd5' authenticator
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092239 31237 master.cpp:578] Using
> default 'basic' HTTP authenticator
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092298 31237 master.cpp:658] Using
> default 'basic' HTTP framework authenticator
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092339 31237 master.cpp:705]
> Authorization enabled
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092438 31239
> whitelist_watcher.cpp:77] No whitelist given
> [19:17:15]W: [Step 10/10] I0630 19:17:15.092481 31244 hierarchical.cpp:142]
> Initialized hierarchical allocator process
> [19:17:15]W: [Step 10/10] I0630 19:17:15.093005 31243 leveldb.cpp:304]
> Persisting metadata (8 bytes) to leveldb took
[jira] [Updated] (MESOS-5802) SlaveAuthorizerTest/0.ViewFlags is flaky.
[
https://issues.apache.org/jira/browse/MESOS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-5802:
--
Shepherd: Vinod Kone
Sprint: Mesosphere Sprint 39
> SlaveAuthorizerTest/0.ViewFlags is flaky.
> -
>
> Key: MESOS-5802
> URL: https://issues.apache.org/jira/browse/MESOS-5802
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Jie Yu
>Assignee: Alexander Rojas
> Labels: mesosphere, race-condition, slave
>
> {noformat}
> [15:24:47] : [Step 10/10] [ RUN ] SlaveAuthorizerTest/0.ViewFlags
> [15:24:47]W: [Step 10/10] I0707 15:24:47.025609 25322
> containerizer.cpp:196] Using isolation:
> posix/cpu,posix/mem,filesystem/posix,network/cni
> [15:24:47]W: [Step 10/10] I0707 15:24:47.030421 25322
> linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
> for the Linux launcher
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032060 25339 slave.cpp:205] Agent
> started on 335)@172.30.2.7:43076
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032078 25339 slave.cpp:206] Flags
> at startup: --acls="" --appc_simple_discovery_uri_prefix="http://;
> --appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="true"
> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
> --authorizer="local" --cgroups_cpu_enable_pids_and_tids_count="false"
> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
> --cgroups_limit_swap="false" --cgroups_root="mesos"
> --container_disk_watch_interval="15secs" --containerizers="mesos"
> --credential="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential"
> --default_role="*" --disk_watch_interval="1mins" --docker="docker"
> --docker_kill_orphans="true" --docker_registry="https://registry-1.docker.io;
> --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock"
> --docker_stop_timeout="0ns" --docker_store_dir="/tmp/mesos/store/docker"
> --docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume"
> --enforce_container_disk_quota="false"
> --executor_registration_timeout="1mins"
> --executor_shutdown_grace_period="5secs"
> --fetcher_cache_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/fetch"
> --fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks"
> --gc_disk_headroom="0.1" --hadoop_home="" --help="true"
> --hostname_lookup="true" --http_authenticators="basic"
> --http_command_executor="false"
> --http_credentials="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials"
> --image_provisioner_backend="copy" --initialize_driver_logging="true"
> --isolation="posix/cpu,posix/mem"
> --launcher_dir="/mnt/teamcity/work/4240ba9ddd0997c3/build/src"
> --logbufsecs="0" --logging_level="INFO"
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
> --perf_interval="1mins" --qos_correction_interval_min="0ns" --quiet="false"
> --recover="reconnect" --recovery_timeout="15mins"
> --registration_backoff_factor="10ms"
> --resources="cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]"
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox"
> --strict="true" --switch_user="true" --systemd_enable_support="true"
> --systemd_runtime_directory="/run/systemd/system" --version="false"
> --work_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C"
> --xfs_project_range="[5000-1]"
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032306 25339 credentials.hpp:86]
> Loading credential for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032424 25339 slave.cpp:343] Agent
> using credential for: test-principal
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032441 25339 credentials.hpp:37]
> Loading credentials for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032528 25339 slave.cpp:395] Using
> default 'basic' HTTP authenticator
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032754 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032838 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032968 25339 slave.cpp:594] Agent
> resources: cpus(*):2; mem(*):1024; disk(*):1024; ports(*):[31000-32000]
> [15:24:47]W: [Step 10/10] I0707
[jira] [Updated] (MESOS-5802) SlaveAuthorizerTest/0.ViewFlags is flaky.
[
https://issues.apache.org/jira/browse/MESOS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-5802:
--
Story Points: 2
> SlaveAuthorizerTest/0.ViewFlags is flaky.
> -
>
> Key: MESOS-5802
> URL: https://issues.apache.org/jira/browse/MESOS-5802
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Jie Yu
>Assignee: Alexander Rojas
> Labels: mesosphere, race-condition, slave
>
> {noformat}
> [15:24:47] : [Step 10/10] [ RUN ] SlaveAuthorizerTest/0.ViewFlags
> [15:24:47]W: [Step 10/10] I0707 15:24:47.025609 25322
> containerizer.cpp:196] Using isolation:
> posix/cpu,posix/mem,filesystem/posix,network/cni
> [15:24:47]W: [Step 10/10] I0707 15:24:47.030421 25322
> linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
> for the Linux launcher
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032060 25339 slave.cpp:205] Agent
> started on 335)@172.30.2.7:43076
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032078 25339 slave.cpp:206] Flags
> at startup: --acls="" --appc_simple_discovery_uri_prefix="http://;
> --appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="true"
> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
> --authorizer="local" --cgroups_cpu_enable_pids_and_tids_count="false"
> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
> --cgroups_limit_swap="false" --cgroups_root="mesos"
> --container_disk_watch_interval="15secs" --containerizers="mesos"
> --credential="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential"
> --default_role="*" --disk_watch_interval="1mins" --docker="docker"
> --docker_kill_orphans="true" --docker_registry="https://registry-1.docker.io;
> --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock"
> --docker_stop_timeout="0ns" --docker_store_dir="/tmp/mesos/store/docker"
> --docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume"
> --enforce_container_disk_quota="false"
> --executor_registration_timeout="1mins"
> --executor_shutdown_grace_period="5secs"
> --fetcher_cache_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/fetch"
> --fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks"
> --gc_disk_headroom="0.1" --hadoop_home="" --help="true"
> --hostname_lookup="true" --http_authenticators="basic"
> --http_command_executor="false"
> --http_credentials="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials"
> --image_provisioner_backend="copy" --initialize_driver_logging="true"
> --isolation="posix/cpu,posix/mem"
> --launcher_dir="/mnt/teamcity/work/4240ba9ddd0997c3/build/src"
> --logbufsecs="0" --logging_level="INFO"
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
> --perf_interval="1mins" --qos_correction_interval_min="0ns" --quiet="false"
> --recover="reconnect" --recovery_timeout="15mins"
> --registration_backoff_factor="10ms"
> --resources="cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]"
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox"
> --strict="true" --switch_user="true" --systemd_enable_support="true"
> --systemd_runtime_directory="/run/systemd/system" --version="false"
> --work_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C"
> --xfs_project_range="[5000-1]"
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032306 25339 credentials.hpp:86]
> Loading credential for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032424 25339 slave.cpp:343] Agent
> using credential for: test-principal
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032441 25339 credentials.hpp:37]
> Loading credentials for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032528 25339 slave.cpp:395] Using
> default 'basic' HTTP authenticator
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032754 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032838 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032968 25339 slave.cpp:594] Agent
> resources: cpus(*):2; mem(*):1024; disk(*):1024; ports(*):[31000-32000]
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032994 25339 slave.cpp:602] Agent
>
[jira] [Updated] (MESOS-5788) Consider adding a Java Scheduler Shim/Adapter for the new/old API.
[ https://issues.apache.org/jira/browse/MESOS-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-5788: -- Sprint: Mesosphere Sprint 39 > Consider adding a Java Scheduler Shim/Adapter for the new/old API. > -- > > Key: MESOS-5788 > URL: https://issues.apache.org/jira/browse/MESOS-5788 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar >Assignee: Anand Mazumdar > Labels: mesosphere > > Currently, for existing JAVA based frameworks, moving to try out the new API > can be cumbersome. This change intends to introduce a shim/adapter interface > that makes this easier by allowing to toggle between the old/new API > (driver/new scheduler library) implementation via an environment variable. > This would allow framework developers to transition their older frameworks to > the new API rather seamlessly. > This would look similar to the work done for the executor shim for C++ > (command/docker executor). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5425) Consider using IntervalSet for Port range resource math
[
https://issues.apache.org/jira/browse/MESOS-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Wu updated MESOS-5425:
-
Shepherd: Joseph Wu
Story Points: 3
Labels: allocator mesosphere (was: mesosphere)
> Consider using IntervalSet for Port range resource math
> ---
>
> Key: MESOS-5425
> URL: https://issues.apache.org/jira/browse/MESOS-5425
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
>Reporter: Joseph Wu
>Assignee: Yanyan Hu
> Labels: allocator, mesosphere
> Attachments: graycol.gif
>
>
> Follow-up JIRA for comments raised in MESOS-3051 (see comments there).
> We should consider utilizing
> [{{IntervalSet}}|https://github.com/apache/mesos/blob/a0b798d2fac39445ce0545cfaf05a682cd393abe/3rdparty/stout/include/stout/interval.hpp]
> in [Port range resource
> math|https://github.com/apache/mesos/blob/a0b798d2fac39445ce0545cfaf05a682cd393abe/src/common/values.cpp#L143].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5228) Add tests for Capability API.
[ https://issues.apache.org/jira/browse/MESOS-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5228: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38) > Add tests for Capability API. > - > > Key: MESOS-5228 > URL: https://issues.apache.org/jira/browse/MESOS-5228 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Benjamin Bannier > Labels: mesosphere, unified-containerizer-mvp > > Add basic tests for the capability API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5582) Create a `cgroups/devices` isolator.
[ https://issues.apache.org/jira/browse/MESOS-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5582: - Sprint: Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38) > Create a `cgroups/devices` isolator. > > > Key: MESOS-5582 > URL: https://issues.apache.org/jira/browse/MESOS-5582 > Project: Mesos > Issue Type: Improvement >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: gpu, isolator, mesosphere > > Currently, all the logic for the `cgroups/devices` isolator is bundled into > the Nvidia GPU Isolator. We should abstract it out into it's own component > and remove the redundant logic from the Nvidia GPU Isolator. Assuming the > guaranteed ordering between isolators from MESOS-5581, we can be sure that > the dependency order between the `cgroups/devices` and `gpu/nvidia` isolators > is met. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4766) Improve allocator performance.
[ https://issues.apache.org/jira/browse/MESOS-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4766: - Sprint: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38) > Improve allocator performance. > -- > > Key: MESOS-4766 > URL: https://issues.apache.org/jira/browse/MESOS-4766 > Project: Mesos > Issue Type: Epic > Components: allocation >Reporter: Benjamin Mahler >Assignee: Michael Park >Priority: Critical > > This is an epic to track the various tickets around improving the performance > of the allocator, including the following: > * Preventing un-necessary backup of the allocator. > * Reducing the cost of allocations and allocator state updates. > * Improving performance of the DRF sorter. > * More benchmarking to simulate scenarios with performance issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5730) Sandbox access authorization should fail for non existing sandboxes.
[
https://issues.apache.org/jira/browse/MESOS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-5730:
-
Sprint: Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint
38)
> Sandbox access authorization should fail for non existing sandboxes.
>
>
> Key: MESOS-5730
> URL: https://issues.apache.org/jira/browse/MESOS-5730
> Project: Mesos
> Issue Type: Bug
> Components: security
>Affects Versions: 1.0.0
>Reporter: Till Toenshoff
> Labels: authorization, mesosphere, security
>
> The local authorizer currently tries to authorize {{ACCESS_SANDBOX}} even if
> no further object specification - e.g. {{framework_info}} or
> {{executor_info}}) where specified / available at that time.
> Given that there is likely no sandbox available if there was no
> {{executor_info}} provided, I think we should actually fail instead of allow
> or deny (403).
> A failure would result into an IMHO more appropriate ServiceUnavailable
> (503).
> See
> https://github.com/apache/mesos/commit/c8d67590064e35566274116cede9c6a733187b48#diff-dd692b1640b2628014feca01a94ba1e1R241
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5275) Add capabilities support for unified containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5275: - Sprint: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38) > Add capabilities support for unified containerizer. > --- > > Key: MESOS-5275 > URL: https://issues.apache.org/jira/browse/MESOS-5275 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Benjamin Bannier > Labels: mesosphere > > Add capabilities support for unified containerizer. > Requirements: > 1. Use the mesos capabilities API. > 2. Frameworks be able to add capability requests for containers. > 3. Agents be able to add maximum allowed capabilities for all containers > launched. > Design document: > https://docs.google.com/document/d/1YiTift8TQla2vq3upQr7K-riQ_pQ-FKOCOsysQJROGc/edit#heading=h.rgfwelqrskmd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5716) Document docker private registry with authentication support in Unified Containerizer.
[ https://issues.apache.org/jira/browse/MESOS-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5716: - Sprint: Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 38) > Document docker private registry with authentication support in Unified > Containerizer. > -- > > Key: MESOS-5716 > URL: https://issues.apache.org/jira/browse/MESOS-5716 > Project: Mesos > Issue Type: Improvement > Components: containerization, documentation >Reporter: Gilbert Song >Assignee: Gilbert Song > Labels: containerizer, docker, mesosphere > > Add documentation for docker private registry with authentication support in > unified containerizer. This is the basic support for docker private registry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5051) Create helpers for manipulating Linux capabilities.
[ https://issues.apache.org/jira/browse/MESOS-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5051: - Sprint: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38) > Create helpers for manipulating Linux capabilities. > --- > > Key: MESOS-5051 > URL: https://issues.apache.org/jira/browse/MESOS-5051 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Benjamin Bannier > Labels: mesosphere > > These helpers can either based on some existing library (e.g. libcap), or use > system calls directly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5759) ProcessRemoteLinkTest.RemoteUseStaleLink and RemoteStaleLinkRelink are flaky
[
https://issues.apache.org/jira/browse/MESOS-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-5759:
-
Sprint: Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint
38)
> ProcessRemoteLinkTest.RemoteUseStaleLink and RemoteStaleLinkRelink are flaky
>
>
> Key: MESOS-5759
> URL: https://issues.apache.org/jira/browse/MESOS-5759
> Project: Mesos
> Issue Type: Bug
> Components: libprocess, test
>Affects Versions: 1.0.0
>Reporter: Joseph Wu
>Assignee: Joseph Wu
> Labels: libprocess, mesosphere
>
> {{ProcessRemoteLinkTest.RemoteUseStaleLink}} and
> {{ProcessRemoteLinkTest.RemoteStaleLinkRelink}} are failing occasionally with
> the error:
> {code}
> [ RUN ] ProcessRemoteLinkTest.RemoteStaleLinkRelink
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> I0630 07:42:34.661110 1 process.cpp:1066] libprocess is initialized on
> 172.17.0.2:56294 with 16 worker threads
> E0630 07:42:34.666393 18765 process.cpp:2104] Failed to shutdown socket with
> fd 7: Transport endpoint is not connected
> /mesos/3rdparty/libprocess/src/tests/process_tests.cpp:1059: Failure
> Value of: exitedPid.isPending()
> Actual: false
> Expected: true
> [ FAILED ] ProcessRemoteLinkTest.RemoteStaleLinkRelink (56 ms)
> {code}
> There appears to be a race between establishing a socket connection and the
> test calling {{::shutdown}} on the socket. Under some circumstances, the
> {{::shutdown}} may actually result in failing the future in
> {{SocketManager::link_connect}} error and thereby trigger
> {{SocketManager::close}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4233) Logging is too verbose for sysadmins / syslog
[
https://issues.apache.org/jira/browse/MESOS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-4233:
-
Sprint: Mesosphere Sprint 26, Mesosphere Sprint 27, Mesosphere Sprint 28,
Mesosphere Sprint 29, Mesosphere Sprint 30, Mesosphere Sprint 31, Mesosphere
Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35,
Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere
Sprint 39 (was: Mesosphere Sprint 26, Mesosphere Sprint 27, Mesosphere Sprint
28, Mesosphere Sprint 29, Mesosphere Sprint 30, Mesosphere Sprint 31,
Mesosphere Sprint 32, Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere
Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38)
> Logging is too verbose for sysadmins / syslog
> -
>
> Key: MESOS-4233
> URL: https://issues.apache.org/jira/browse/MESOS-4233
> Project: Mesos
> Issue Type: Epic
>Reporter: Cody Maloney
>Assignee: Kapil Arya
> Labels: mesosphere
> Attachments: giant_port_range_logging
>
>
> Currently mesos logs a lot. When launching a thousand tasks in the space of
> 10 seconds it will print tens of thousands of log lines, overwhelming syslog
> (there is a max rate at which a process can send stuff over a unix socket)
> and not giving useful information to a sysadmin who cares about just the
> high-level activity and when something goes wrong.
> Note mesos also blocks writing to its log locations, so when writing a lot of
> log messages, it can fill up the write buffer in the kernel, and be suspended
> until the syslog agent catches up reading from the socket (GLOG does a
> blocking fwrite to stderr). GLOG also has a big mutex around logging so only
> one thing logs at a time.
> While for "internal debugging" it is useful to see things like "message went
> from internal compoent x to internal component y", from a sysadmin
> perspective I only care about the high level actions taken (launched task for
> framework x), sent offer to framework y, got task failed from host z. Note
> those are what I'd expect at the "INFO" level. At the "WARNING" level I'd
> expect very little to be logged / almost nothing in normal operation. Just
> things like "WARN: Repliacted log write took longer than expected". WARN
> would also get things like backtraces on crashes and abnormal exits / abort.
> When trying to launch 3k+ tasks inside a second, mesos logging currently
> overwhelms syslog with 100k+ messages, many of which are thousands of bytes.
> Sysadmins expect to be able to use syslog to monitor basic events in their
> system. This is too much.
> We can keep logging the messages to files, but the logging to stderr needs to
> be reduced significantly (stderr gets picked up and forwarded to syslog /
> central aggregation).
> What I would like is if I can set the stderr logging level to be different /
> independent from the file logging level (Syslog giving the "sysadmin"
> aggregated overview, files useful for debugging in depth what happened in a
> cluster). A lot of what mesos currently logs at info is really debugging info
> / should show up as debug log level.
> Some samples of mesos logging a lot more than a sysadmin would want / expect
> are attached, and some are below:
> - Every task gets printed multiple times for a basic launch:
> {noformat}
> Dec 15 22:58:30 ip-10-0-7-60.us-west-2.compute.internal mesos-master[1311]:
> I1215 22:58:29.382644 1315 master.cpp:3248] Launching task
> envy.5b19a713-a37f-11e5-8b3e-0251692d6109 of framework
> 5178f46d-71d6-422f-922c-5bbe82dff9cc- (marathon)
> Dec 15 22:58:30 ip-10-0-7-60.us-west-2.compute.internal mesos-master[1311]:
> I1215 22:58:29.382925 1315 master.hpp:176] Adding task
> envy.5b1958f2-a37f-11e5-8b3e-0251692d6109 with resources cpus(*):0.0001;
> mem(*):16; ports(*):[14047-14047]
> {noformat}
> - Every task status update prints many log lines, successful ones are part
> of normal operation and maybe should be logged at info / debug levels, but
> not to a sysadmin (Just show when things fail, and maybe aggregate counters
> to tell of the volume of working)
> - No log messagse should be really big / more than 1k characters (Would
> prevent the giant port list attached, make that easily discoverable / bug
> filable / fixable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5221) Add Documentation for Nvidia GPU support
[ https://issues.apache.org/jira/browse/MESOS-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5221: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 33, Mesosphere Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38) > Add Documentation for Nvidia GPU support > > > Key: MESOS-5221 > URL: https://issues.apache.org/jira/browse/MESOS-5221 > Project: Mesos > Issue Type: Documentation >Reporter: Kevin Klues >Assignee: Kevin Klues >Priority: Minor > > https://reviews.apache.org/r/46220/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5303) Add capabilities support for mesos execute cli.
[ https://issues.apache.org/jira/browse/MESOS-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5303: - Sprint: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38) > Add capabilities support for mesos execute cli. > --- > > Key: MESOS-5303 > URL: https://issues.apache.org/jira/browse/MESOS-5303 > Project: Mesos > Issue Type: Bug > Components: containerization >Reporter: Jojy Varghese >Assignee: Benjamin Bannier > Labels: mesosphere > > Add support for `user` and `capabilities` to execute cli. This will help in > testing the `capabilities` feature for unified containerizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5570) Improve CHANGELOG and upgrades.md
[ https://issues.apache.org/jira/browse/MESOS-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5570: - Sprint: Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 37, Mesosphere Sprint 38) > Improve CHANGELOG and upgrades.md > - > > Key: MESOS-5570 > URL: https://issues.apache.org/jira/browse/MESOS-5570 > Project: Mesos > Issue Type: Documentation >Reporter: Joerg Schad >Assignee: Joerg Schad > > Currently we have a lot of data duplication between the CHANGELOG and > upgrades.md. We should try to improve this and potentially make the CHANGLOG > a markdown file as well. For inspiration see the Hadoop changelog: > https://github.com/apache/hadoop/blob/2e1d0ff4e901b8313c8d71869735b94ed8bc40a0/hadoop-common-project/hadoop-common/src/site/markdown/release/1.2.0/CHANGES.1.2.0.md -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4690) Reorganize 3rdparty directory
[ https://issues.apache.org/jira/browse/MESOS-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-4690: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 36, Mesosphere Sprint 37, Mesosphere Sprint 38) > Reorganize 3rdparty directory > - > > Key: MESOS-4690 > URL: https://issues.apache.org/jira/browse/MESOS-4690 > Project: Mesos > Issue Type: Epic > Components: build, libprocess, stout >Reporter: Kapil Arya >Assignee: Kapil Arya > Labels: mesosphere > > This issues is currently being discussed in the dev mailing list: > http://www.mail-archive.com/dev@mesos.apache.org/msg34349.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5232) Add capability information to ContainerInfo protobuf message.
[ https://issues.apache.org/jira/browse/MESOS-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-5232: - Sprint: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38, Mesosphere Sprint 39 (was: Mesosphere Sprint 33, Mesosphere Sprint 34, Mesosphere Sprint 35, Mesosphere Sprint 37, Mesosphere Sprint 38) > Add capability information to ContainerInfo protobuf message. > - > > Key: MESOS-5232 > URL: https://issues.apache.org/jira/browse/MESOS-5232 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Jojy Varghese >Assignee: Benjamin Bannier > Labels: mesosphere > > To enable support for capability as first class framework entity, we need to > add capabilities related information to the ContainerInfo protobuf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5811) Implement GET_TASKS Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367895#comment-15367895 ] haosdent commented on MESOS-5811: - | Implemented 'GetTasks' call in v1 agent API. | https://reviews.apache.org/r/49759 | | Added test case for 'GetTasks' call in v1 agent API. | https://reviews.apache.org/r/49799 | > Implement GET_TASKS Call in v1 agent API. > - > > Key: MESOS-5811 > URL: https://issues.apache.org/jira/browse/MESOS-5811 > Project: Mesos > Issue Type: Task >Reporter: haosdent >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5811) Implement GET_TASKS Call in v1 agent API.
haosdent created MESOS-5811: --- Summary: Implement GET_TASKS Call in v1 agent API. Key: MESOS-5811 URL: https://issues.apache.org/jira/browse/MESOS-5811 Project: Mesos Issue Type: Task Reporter: haosdent Assignee: haosdent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5810) Implement GET_EXECUTORS Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367892#comment-15367892 ] haosdent commented on MESOS-5810: - | Implemented 'GetExecutors' call in v1 agent API. | https://reviews.apache.org/r/49758 | | Added test case for 'GetExecutors' call in v1 agent API. | https://reviews.apache.org/r/49798 | > Implement GET_EXECUTORS Call in v1 agent API. > - > > Key: MESOS-5810 > URL: https://issues.apache.org/jira/browse/MESOS-5810 > Project: Mesos > Issue Type: Task >Reporter: haosdent >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5810) Implement GET_EXECUTORS Call in v1 agent API.
haosdent created MESOS-5810: --- Summary: Implement GET_EXECUTORS Call in v1 agent API. Key: MESOS-5810 URL: https://issues.apache.org/jira/browse/MESOS-5810 Project: Mesos Issue Type: Task Reporter: haosdent Assignee: haosdent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5809) Implement GET_FRAMEWORKS Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5809: Fix Version/s: (was: 1.0.0) > Implement GET_FRAMEWORKS Call in v1 agent API. > -- > > Key: MESOS-5809 > URL: https://issues.apache.org/jira/browse/MESOS-5809 > Project: Mesos > Issue Type: Task >Reporter: haosdent >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5809) Implement GET_FRAMEWORKS Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5809: Description: (was: Review Request: https://reviews.apache.org/r/49136/ & https://reviews.apache.org/r/49137/) > Implement GET_FRAMEWORKS Call in v1 agent API. > -- > > Key: MESOS-5809 > URL: https://issues.apache.org/jira/browse/MESOS-5809 > Project: Mesos > Issue Type: Task >Reporter: haosdent >Assignee: haosdent > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5809) Implement GET_FRAMEWORKS Call in v1 agent API.
haosdent created MESOS-5809: --- Summary: Implement GET_FRAMEWORKS Call in v1 agent API. Key: MESOS-5809 URL: https://issues.apache.org/jira/browse/MESOS-5809 Project: Mesos Issue Type: Task Reporter: haosdent Assignee: zhou xing Fix For: 1.0.0 Review Request: https://reviews.apache.org/r/49136/ & https://reviews.apache.org/r/49137/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5809) Implement GET_FRAMEWORKS Call in v1 agent API.
[ https://issues.apache.org/jira/browse/MESOS-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-5809: --- Assignee: haosdent (was: zhou xing) > Implement GET_FRAMEWORKS Call in v1 agent API. > -- > > Key: MESOS-5809 > URL: https://issues.apache.org/jira/browse/MESOS-5809 > Project: Mesos > Issue Type: Task >Reporter: haosdent >Assignee: haosdent > Fix For: 1.0.0 > > > Review Request: > https://reviews.apache.org/r/49136/ > & > https://reviews.apache.org/r/49137/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3753) Test the HTTP Scheduler library with SSL enabled
[ https://issues.apache.org/jira/browse/MESOS-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-3753: - Sprint: Mesosphere Sprint 39 > Test the HTTP Scheduler library with SSL enabled > > > Key: MESOS-3753 > URL: https://issues.apache.org/jira/browse/MESOS-3753 > Project: Mesos > Issue Type: Story > Components: framework, HTTP API, test >Reporter: Joseph Wu >Assignee: Greg Mann > Labels: mesosphere, security > > Currently, the HTTP Scheduler library does not support SSL-enabled Mesos. > (You can manually test this by spinning up an SSL-enabled master and attempt > to run the event-call framework example against it.) > We need to add tests that check the HTTP Scheduler library against > SSL-enabled Mesos: > * with downgrade support, > * with required framework/client-side certifications, > * with/without verification of certificates (master-side), > * with/without verification of certificates (framework-side), > * with a custom certificate authority (CA) > These options should be controlled by the same environment variables found on > the [SSL user doc|http://mesos.apache.org/documentation/latest/ssl/]. > Note: This issue will be broken down into smaller sub-issues as bugs/problems > are discovered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3753) Test the HTTP Scheduler library with SSL enabled
[ https://issues.apache.org/jira/browse/MESOS-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann updated MESOS-3753: - Shepherd: Vinod Kone > Test the HTTP Scheduler library with SSL enabled > > > Key: MESOS-3753 > URL: https://issues.apache.org/jira/browse/MESOS-3753 > Project: Mesos > Issue Type: Story > Components: framework, HTTP API, test >Reporter: Joseph Wu >Assignee: Greg Mann > Labels: mesosphere, security > > Currently, the HTTP Scheduler library does not support SSL-enabled Mesos. > (You can manually test this by spinning up an SSL-enabled master and attempt > to run the event-call framework example against it.) > We need to add tests that check the HTTP Scheduler library against > SSL-enabled Mesos: > * with downgrade support, > * with required framework/client-side certifications, > * with/without verification of certificates (master-side), > * with/without verification of certificates (framework-side), > * with a custom certificate authority (CA) > These options should be controlled by the same environment variables found on > the [SSL user doc|http://mesos.apache.org/documentation/latest/ssl/]. > Note: This issue will be broken down into smaller sub-issues as bugs/problems > are discovered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-3753) Test the HTTP Scheduler library with SSL enabled
[ https://issues.apache.org/jira/browse/MESOS-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Mann reassigned MESOS-3753: Assignee: Greg Mann (was: Anand Mazumdar) > Test the HTTP Scheduler library with SSL enabled > > > Key: MESOS-3753 > URL: https://issues.apache.org/jira/browse/MESOS-3753 > Project: Mesos > Issue Type: Story > Components: framework, HTTP API, test >Reporter: Joseph Wu >Assignee: Greg Mann > Labels: mesosphere, security > > Currently, the HTTP Scheduler library does not support SSL-enabled Mesos. > (You can manually test this by spinning up an SSL-enabled master and attempt > to run the event-call framework example against it.) > We need to add tests that check the HTTP Scheduler library against > SSL-enabled Mesos: > * with downgrade support, > * with required framework/client-side certifications, > * with/without verification of certificates (master-side), > * with/without verification of certificates (framework-side), > * with a custom certificate authority (CA) > These options should be controlled by the same environment variables found on > the [SSL user doc|http://mesos.apache.org/documentation/latest/ssl/]. > Note: This issue will be broken down into smaller sub-issues as bugs/problems > are discovered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5802) SlaveAuthorizerTest/0.ViewFlags is flaky.
[
https://issues.apache.org/jira/browse/MESOS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367726#comment-15367726
]
Alexander Rojas commented on MESOS-5802:
After investigation, the problem is that this code:
{code}
Try agent = this->StartSlave(,
authorizer.get());
ASSERT_SOME(agent);
{code}
Does not guarantees that the {{agent}} is ready to be used. In certain
situations, the HTTP request to {{/state}} gets scheduled before
{{Slave::__recover()}} and since the {{/state}} handler first checks that the
agent is not in a recovering state, the test fails.
This is more a test bug than a functionality test, and an easy fix is to start
a master and don't do HTTP requests to {{/state}} until the agent is connected.
This guarantees that the agent is in a useful state at that point.
> SlaveAuthorizerTest/0.ViewFlags is flaky.
> -
>
> Key: MESOS-5802
> URL: https://issues.apache.org/jira/browse/MESOS-5802
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Jie Yu
>Assignee: Alexander Rojas
> Labels: mesosphere, race-condition, slave
>
> {noformat}
> [15:24:47] : [Step 10/10] [ RUN ] SlaveAuthorizerTest/0.ViewFlags
> [15:24:47]W: [Step 10/10] I0707 15:24:47.025609 25322
> containerizer.cpp:196] Using isolation:
> posix/cpu,posix/mem,filesystem/posix,network/cni
> [15:24:47]W: [Step 10/10] I0707 15:24:47.030421 25322
> linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
> for the Linux launcher
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032060 25339 slave.cpp:205] Agent
> started on 335)@172.30.2.7:43076
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032078 25339 slave.cpp:206] Flags
> at startup: --acls="" --appc_simple_discovery_uri_prefix="http://;
> --appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="true"
> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
> --authorizer="local" --cgroups_cpu_enable_pids_and_tids_count="false"
> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
> --cgroups_limit_swap="false" --cgroups_root="mesos"
> --container_disk_watch_interval="15secs" --containerizers="mesos"
> --credential="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential"
> --default_role="*" --disk_watch_interval="1mins" --docker="docker"
> --docker_kill_orphans="true" --docker_registry="https://registry-1.docker.io;
> --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock"
> --docker_stop_timeout="0ns" --docker_store_dir="/tmp/mesos/store/docker"
> --docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume"
> --enforce_container_disk_quota="false"
> --executor_registration_timeout="1mins"
> --executor_shutdown_grace_period="5secs"
> --fetcher_cache_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/fetch"
> --fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks"
> --gc_disk_headroom="0.1" --hadoop_home="" --help="true"
> --hostname_lookup="true" --http_authenticators="basic"
> --http_command_executor="false"
> --http_credentials="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials"
> --image_provisioner_backend="copy" --initialize_driver_logging="true"
> --isolation="posix/cpu,posix/mem"
> --launcher_dir="/mnt/teamcity/work/4240ba9ddd0997c3/build/src"
> --logbufsecs="0" --logging_level="INFO"
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
> --perf_interval="1mins" --qos_correction_interval_min="0ns" --quiet="false"
> --recover="reconnect" --recovery_timeout="15mins"
> --registration_backoff_factor="10ms"
> --resources="cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]"
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox"
> --strict="true" --switch_user="true" --systemd_enable_support="true"
> --systemd_runtime_directory="/run/systemd/system" --version="false"
> --work_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C"
> --xfs_project_range="[5000-1]"
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032306 25339 credentials.hpp:86]
> Loading credential for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032424 25339 slave.cpp:343] Agent
> using credential for: test-principal
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032441 25339 credentials.hpp:37]
> Loading credentials for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032528 25339 slave.cpp:395] Using
> default 'basic' HTTP authenticator
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032754 25339
[jira] [Updated] (MESOS-5802) SlaveAuthorizerTest/0.ViewFlags is flaky.
[
https://issues.apache.org/jira/browse/MESOS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas updated MESOS-5802:
---
Component/s: slave
> SlaveAuthorizerTest/0.ViewFlags is flaky.
> -
>
> Key: MESOS-5802
> URL: https://issues.apache.org/jira/browse/MESOS-5802
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Jie Yu
>Assignee: Alexander Rojas
> Labels: mesosphere, race-condition, slave
>
> {noformat}
> [15:24:47] : [Step 10/10] [ RUN ] SlaveAuthorizerTest/0.ViewFlags
> [15:24:47]W: [Step 10/10] I0707 15:24:47.025609 25322
> containerizer.cpp:196] Using isolation:
> posix/cpu,posix/mem,filesystem/posix,network/cni
> [15:24:47]W: [Step 10/10] I0707 15:24:47.030421 25322
> linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
> for the Linux launcher
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032060 25339 slave.cpp:205] Agent
> started on 335)@172.30.2.7:43076
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032078 25339 slave.cpp:206] Flags
> at startup: --acls="" --appc_simple_discovery_uri_prefix="http://;
> --appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="true"
> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
> --authorizer="local" --cgroups_cpu_enable_pids_and_tids_count="false"
> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
> --cgroups_limit_swap="false" --cgroups_root="mesos"
> --container_disk_watch_interval="15secs" --containerizers="mesos"
> --credential="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential"
> --default_role="*" --disk_watch_interval="1mins" --docker="docker"
> --docker_kill_orphans="true" --docker_registry="https://registry-1.docker.io;
> --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock"
> --docker_stop_timeout="0ns" --docker_store_dir="/tmp/mesos/store/docker"
> --docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume"
> --enforce_container_disk_quota="false"
> --executor_registration_timeout="1mins"
> --executor_shutdown_grace_period="5secs"
> --fetcher_cache_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/fetch"
> --fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks"
> --gc_disk_headroom="0.1" --hadoop_home="" --help="true"
> --hostname_lookup="true" --http_authenticators="basic"
> --http_command_executor="false"
> --http_credentials="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials"
> --image_provisioner_backend="copy" --initialize_driver_logging="true"
> --isolation="posix/cpu,posix/mem"
> --launcher_dir="/mnt/teamcity/work/4240ba9ddd0997c3/build/src"
> --logbufsecs="0" --logging_level="INFO"
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
> --perf_interval="1mins" --qos_correction_interval_min="0ns" --quiet="false"
> --recover="reconnect" --recovery_timeout="15mins"
> --registration_backoff_factor="10ms"
> --resources="cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]"
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox"
> --strict="true" --switch_user="true" --systemd_enable_support="true"
> --systemd_runtime_directory="/run/systemd/system" --version="false"
> --work_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C"
> --xfs_project_range="[5000-1]"
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032306 25339 credentials.hpp:86]
> Loading credential for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032424 25339 slave.cpp:343] Agent
> using credential for: test-principal
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032441 25339 credentials.hpp:37]
> Loading credentials for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032528 25339 slave.cpp:395] Using
> default 'basic' HTTP authenticator
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032754 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032838 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032968 25339 slave.cpp:594] Agent
> resources: cpus(*):2; mem(*):1024; disk(*):1024; ports(*):[31000-32000]
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032994 25339 slave.cpp:602]
[jira] [Updated] (MESOS-5802) SlaveAuthorizerTest/0.ViewFlags is flaky.
[
https://issues.apache.org/jira/browse/MESOS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas updated MESOS-5802:
---
Labels: mesosphere race-condition slave (was: )
> SlaveAuthorizerTest/0.ViewFlags is flaky.
> -
>
> Key: MESOS-5802
> URL: https://issues.apache.org/jira/browse/MESOS-5802
> Project: Mesos
> Issue Type: Bug
> Components: slave
>Reporter: Jie Yu
>Assignee: Alexander Rojas
> Labels: mesosphere, race-condition, slave
>
> {noformat}
> [15:24:47] : [Step 10/10] [ RUN ] SlaveAuthorizerTest/0.ViewFlags
> [15:24:47]W: [Step 10/10] I0707 15:24:47.025609 25322
> containerizer.cpp:196] Using isolation:
> posix/cpu,posix/mem,filesystem/posix,network/cni
> [15:24:47]W: [Step 10/10] I0707 15:24:47.030421 25322
> linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
> for the Linux launcher
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032060 25339 slave.cpp:205] Agent
> started on 335)@172.30.2.7:43076
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032078 25339 slave.cpp:206] Flags
> at startup: --acls="" --appc_simple_discovery_uri_prefix="http://;
> --appc_store_dir="/tmp/mesos/store/appc" --authenticate_http="true"
> --authenticatee="crammd5" --authentication_backoff_factor="1secs"
> --authorizer="local" --cgroups_cpu_enable_pids_and_tids_count="false"
> --cgroups_enable_cfs="false" --cgroups_hierarchy="/sys/fs/cgroup"
> --cgroups_limit_swap="false" --cgroups_root="mesos"
> --container_disk_watch_interval="15secs" --containerizers="mesos"
> --credential="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential"
> --default_role="*" --disk_watch_interval="1mins" --docker="docker"
> --docker_kill_orphans="true" --docker_registry="https://registry-1.docker.io;
> --docker_remove_delay="6hrs" --docker_socket="/var/run/docker.sock"
> --docker_stop_timeout="0ns" --docker_store_dir="/tmp/mesos/store/docker"
> --docker_volume_checkpoint_dir="/var/run/mesos/isolators/docker/volume"
> --enforce_container_disk_quota="false"
> --executor_registration_timeout="1mins"
> --executor_shutdown_grace_period="5secs"
> --fetcher_cache_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/fetch"
> --fetcher_cache_size="2GB" --frameworks_home="" --gc_delay="1weeks"
> --gc_disk_headroom="0.1" --hadoop_home="" --help="true"
> --hostname_lookup="true" --http_authenticators="basic"
> --http_command_executor="false"
> --http_credentials="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials"
> --image_provisioner_backend="copy" --initialize_driver_logging="true"
> --isolation="posix/cpu,posix/mem"
> --launcher_dir="/mnt/teamcity/work/4240ba9ddd0997c3/build/src"
> --logbufsecs="0" --logging_level="INFO"
> --oversubscribed_resources_interval="15secs" --perf_duration="10secs"
> --perf_interval="1mins" --qos_correction_interval_min="0ns" --quiet="false"
> --recover="reconnect" --recovery_timeout="15mins"
> --registration_backoff_factor="10ms"
> --resources="cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]"
> --revocable_cpu_low_priority="true" --sandbox_directory="/mnt/mesos/sandbox"
> --strict="true" --switch_user="true" --systemd_enable_support="true"
> --systemd_runtime_directory="/run/systemd/system" --version="false"
> --work_dir="/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C"
> --xfs_project_range="[5000-1]"
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032306 25339 credentials.hpp:86]
> Loading credential for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/credential'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032424 25339 slave.cpp:343] Agent
> using credential for: test-principal
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032441 25339 credentials.hpp:37]
> Loading credentials for authentication from
> '/mnt/teamcity/temp/buildTmp/SlaveAuthorizerTest_0_ViewFlags_OsJb5C/http_credentials'
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032528 25339 slave.cpp:395] Using
> default 'basic' HTTP authenticator
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032754 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032838 25339 resources.cpp:572]
> Parsing resources as JSON failed:
> cpus:2;gpus:0;mem:1024;disk:1024;ports:[31000-32000]
> [15:24:47]W: [Step 10/10] Trying semicolon-delimited string format instead
> [15:24:47]W: [Step 10/10] I0707 15:24:47.032968 25339 slave.cpp:594] Agent
> resources: cpus(*):2; mem(*):1024; disk(*):1024; ports(*):[31000-32000]
> [15:24:47]W: [Step 10/10] I0707
[jira] [Commented] (MESOS-3505) Support specifying Docker image by Image ID.
[
https://issues.apache.org/jira/browse/MESOS-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367475#comment-15367475
]
Jay Guo commented on MESOS-3505:
ping [~gyliu] [~jieyu] [~xujyan]
> Support specifying Docker image by Image ID.
>
>
> Key: MESOS-3505
> URL: https://issues.apache.org/jira/browse/MESOS-3505
> Project: Mesos
> Issue Type: Story
>Reporter: Yan Xu
>Assignee: Jay Guo
> Labels: mesosphere
>
> A common way to specify a Docker image with the docker engine is through
> {{repo:tag}}, which is convenient and sufficient for most people in most
> scenarios. However this combination is neither precise nor immutable.
> For this reason, it's possible when an image with a {{repo:tag}} already
> cached locally on an agent host and a task requiring this {{repo:tag}}
> arrives, it's using an image that's different than the one the user intended.
> Docker CLI already supports referring to an image by {{repo@id}}, where the
> ID can have two forms:
> * v1 Image ID
> * digest
> Native Mesos provisioner should support the same for Docker images. IMO it's
> fine if image discovery by ID is not supported (and thus still requiring
> {{repo:tag}} to be specified) (looks like [v2
> registry|http://docs.docker.com/registry/spec/api/] does support it) but the
> user can optionally specify an image ID and match it against the cached /
> newly pulled image. If the ID doesn't match the cached image, the store can
> re-pull it; if the ID doesn't match the newly pulled image (manifest), the
> provisioner can fail the request without having the user unknowingly running
> its task on the wrong image.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5708) Add authz to /files/debug
[ https://issues.apache.org/jira/browse/MESOS-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367411#comment-15367411 ] Abhishek Dasgupta commented on MESOS-5708: -- We missed to update '/files/debug' endpoint document for authorization. Posted a trivial patch for this : https://reviews.apache.org/r/49794/ > Add authz to /files/debug > - > > Key: MESOS-5708 > URL: https://issues.apache.org/jira/browse/MESOS-5708 > Project: Mesos > Issue Type: Task > Components: security >Reporter: Adam B >Assignee: Abhishek Dasgupta >Priority: Minor > Labels: mesosphere, security > Fix For: 1.0.0 > > > The /files/debug endpoint exposes the attached master/agent log paths and > every attached sandbox path, which includes the frameworkId and executorId. > Even if sandboxes are protected, we still don't want to expose this > information to unauthorized users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5425) Consider using IntervalSet for Port range resource math
[
https://issues.apache.org/jira/browse/MESOS-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367328#comment-15367328
]
Yanyan Hu commented on MESOS-5425:
--
Yes, will apply 49381 to make a test and post the result. Thanks.
> Consider using IntervalSet for Port range resource math
> ---
>
> Key: MESOS-5425
> URL: https://issues.apache.org/jira/browse/MESOS-5425
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
>Reporter: Joseph Wu
>Assignee: Yanyan Hu
> Labels: mesosphere
> Attachments: graycol.gif
>
>
> Follow-up JIRA for comments raised in MESOS-3051 (see comments there).
> We should consider utilizing
> [{{IntervalSet}}|https://github.com/apache/mesos/blob/a0b798d2fac39445ce0545cfaf05a682cd393abe/3rdparty/stout/include/stout/interval.hpp]
> in [Port range resource
> math|https://github.com/apache/mesos/blob/a0b798d2fac39445ce0545cfaf05a682cd393abe/src/common/values.cpp#L143].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-905) Remove Framework.id in favor of FrameworkInfo.id
[ https://issues.apache.org/jira/browse/MESOS-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367324#comment-15367324 ] Adam B commented on MESOS-905: -- Discarded stale review: https://reviews.apache.org/r/32700/ Should we pick this up again soon [~karya]? > Remove Framework.id in favor of FrameworkInfo.id > > > Key: MESOS-905 > URL: https://issues.apache.org/jira/browse/MESOS-905 > Project: Mesos > Issue Type: Story > Components: framework >Reporter: Adam B >Assignee: Kapil Arya > Labels: mesosphere > > Framework.id currently holds the correct FrameworkId, but Framework also > contains a FrameworkInfo, and the FrameworkInfo.id is not necessarily set. > I propose that we eliminate the Framework.id member variable and replace it > with a Framework.id() accessor that references Framework.FrameworkInfo.id and > ensure that it is correctly set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5781) Benchmark allocation with framework suppression.
[ https://issues.apache.org/jira/browse/MESOS-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Janco updated MESOS-5781: --- Description: Benchmarks effects of framework suppression on allocation time. Frameworks are suppressed and resources recovered each iteration and allocation time is measured as we move to suppress all frameworks in the test case. Referencing MESOS-4694. Sample run at top of tree: [ RUN ] SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 Using 5000 agents and 6000 frameworks allocate() took 3.7728787mins to make 5000 offers with 1200 out of 6000 frameworks suppressing offers allocate() took 3.8739297333mins to make 5000 offers with 2400 out of 6000 frameworks suppressing offers allocate() took 3.7972409833mins to make 5000 offers with 3600 out of 6000 frameworks suppressing offers allocate() took 3.85926955mins to make 5000 offers with 4800 out of 6000 frameworks suppressing offers allocate() took 23.114991secs to make 0 offers with 6000 out of 6000 frameworks suppressing offers [ OK ] SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 (1157073 ms) Sample run with MESOS-4694 (https://reviews.apache.org/r/43666/): [ RUN ] SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 Using 5000 agents and 6000 frameworks allocate() took 2.8807476167mins to make 5000 offers with 1200 out of 6000 frameworks suppressing offers allocate() took 2.0985669833mins to make 5000 offers with 2400 out of 6000 frameworks suppressing offers allocate() took 1.3209152mins to make 5000 offers with 3600 out of 6000 frameworks suppressing offers allocate() took 36.852357secs to make 5000 offers with 4800 out of 6000 frameworks suppressing offers allocate() took 76064us to make 0 offers with 6000 out of 6000 frameworks suppressing offers [ OK ] SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 (624856 ms) was: Benchmarks effects of framework suppression on allocation time. Frameworks are suppressed and resources recovered each iteration and allocation time is measured as we move to suppress all frameworks in the test case. Referencing MESOS-4694. Sample run at top of tree: Using 2000 agents and 200 frameworks round 0 allocate took 2.630963secs to make 199 offers round 1 allocate took 2.640694secs to make 198 offers round 2 allocate took 2.642664secs to make 197 offers ... round 197 allocate took 2.433047secs to make 2 offers round 198 allocate took 2.409804secs to make 1 offers round 199 allocate took 252270us to make 0 offers Sample run with MESOS-4694 (https://reviews.apache.org/r/43666/): Using 2000 agents and 200 frameworks round 0 allocate took 2.626182secs to make 199 offers round 1 allocate took 2.62286secs to make 198 offers round 2 allocate took 2.591389secs to make 197 offers ... round 101 allocate took 1.494164secs to make 98 offers round 102 allocate took 1.491371secs to make 97 offers round 103 allocate took 1.491969secs to make 96 offers ... round 197 allocate took 534780us to make 2 offers round 198 allocate took 501947us to make 1 offers round 199 allocate took 24929us to make 0 offers > Benchmark allocation with framework suppression. > > > Key: MESOS-5781 > URL: https://issues.apache.org/jira/browse/MESOS-5781 > Project: Mesos > Issue Type: Improvement >Reporter: Jacob Janco >Assignee: Jacob Janco > Labels: allocator, benchmark > > Benchmarks effects of framework suppression on allocation time. Frameworks > are suppressed and resources recovered each iteration and allocation time is > measured as we move to suppress all frameworks in the test case. Referencing > MESOS-4694. > Sample run at top of tree: > [ RUN ] > SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 > Using 5000 agents and 6000 frameworks > allocate() took 3.7728787mins to make 5000 offers with 1200 out of 6000 > frameworks suppressing offers > allocate() took 3.8739297333mins to make 5000 offers with 2400 out of > 6000 frameworks suppressing offers > allocate() took 3.7972409833mins to make 5000 offers with 3600 out of > 6000 frameworks suppressing offers > allocate() took 3.85926955mins to make 5000 offers with 4800 out of 6000 > frameworks suppressing offers > allocate() took 23.114991secs to make 0 offers with 6000 out of 6000 > frameworks suppressing offers > [ OK ] > SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 > (1157073 ms) > Sample run with MESOS-4694 (https://reviews.apache.org/r/43666/): > [ RUN ] > SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.SuppressOffers/35 > Using 5000 agents and 6000 frameworks > allocate() took
[jira] [Commented] (MESOS-5425) Consider using IntervalSet for Port range resource math
[
https://issues.apache.org/jira/browse/MESOS-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367301#comment-15367301
]
Guangya Liu commented on MESOS-5425:
I'm linking MESOS-5700 here cause there is a patch
https://reviews.apache.org/r/49381 which can help you doing some benchmark test.
> Consider using IntervalSet for Port range resource math
> ---
>
> Key: MESOS-5425
> URL: https://issues.apache.org/jira/browse/MESOS-5425
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
>Reporter: Joseph Wu
>Assignee: Yanyan Hu
> Labels: mesosphere
> Attachments: graycol.gif
>
>
> Follow-up JIRA for comments raised in MESOS-3051 (see comments there).
> We should consider utilizing
> [{{IntervalSet}}|https://github.com/apache/mesos/blob/a0b798d2fac39445ce0545cfaf05a682cd393abe/3rdparty/stout/include/stout/interval.hpp]
> in [Port range resource
> math|https://github.com/apache/mesos/blob/a0b798d2fac39445ce0545cfaf05a682cd393abe/src/common/values.cpp#L143].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
