[jira] [Updated] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.
[ https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-: -- Sprint: (was: Mesosphere Sprint 34) > Add ACLs for the maintenance HTTP endpoints. > > > Key: MESOS- > URL: https://issues.apache.org/jira/browse/MESOS- > Project: Mesos > Issue Type: Task > Components: master, security >Affects Versions: 0.25.0 >Reporter: Benjamin Mahler > Labels: authorization, maintenance, mesosphere, security > > In order to authorize the HTTP endpoints for maintenance (to be added in > MESOS-2067), we will need to add an ACL definition for performing maintenance > operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2222) Add ACLs for the maintenance HTTP endpoints.
[ https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-: -- Assignee: (was: Benjamin Bannier) > Add ACLs for the maintenance HTTP endpoints. > > > Key: MESOS- > URL: https://issues.apache.org/jira/browse/MESOS- > Project: Mesos > Issue Type: Task > Components: master, security >Affects Versions: 0.25.0 >Reporter: Benjamin Mahler > Labels: authorization, maintenance, mesosphere, security > > In order to authorize the HTTP endpoints for maintenance (to be added in > MESOS-2067), we will need to add an ACL definition for performing maintenance > operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5289) Basic Authentication for Mesos
[ https://issues.apache.org/jira/browse/MESOS-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259505#comment-15259505 ] rajeshwerrao madoori commented on MESOS-5289: - Sure i will get in touch with u...@mesos.apache.org . > Basic Authentication for Mesos > --- > > Key: MESOS-5289 > URL: https://issues.apache.org/jira/browse/MESOS-5289 > Project: Mesos > Issue Type: Bug > Components: framework, HTTP API, master, webui >Affects Versions: 0.27.0 > Environment: mesos framework production environment developer > environment >Reporter: rajeshwerrao madoori >Priority: Critical > Labels: documentation, features, mesosphere > > I have tried to use basic auth for Mesos-master used --authenticate=true > --authenticate_http=true --http_authenticators=basic > --credentials=/home/cloud-user/credentials > dint work for me also tried > --authenticate --authenticate_http --http_authenticators > --credentials=/home/cloud-user/credentials > using crammd5 as default .. > created credentials in a file with username password set file permissions to > 600 > logs show > I0427 01:52:32.988502 25032 logging.cpp:188] INFO level logging started! > I0427 01:52:32.988922 25032 main.cpp:230] Build: 2016-02-01 17:12:13 by root > I0427 01:52:32.988936 25032 main.cpp:232] Version: 0.27.0 > I0427 01:52:32.988943 25032 main.cpp:235] Git tag: 0.27.0 > I0427 01:52:32.988950 25032 main.cpp:239] Git SHA: > c29b3b6801846cda270aab17a670542ec5d238f5 > I0427 01:52:32.988992 25032 main.cpp:253] Using 'HierarchicalDRF' allocator > I0427 01:52:33.016451 25032 leveldb.cpp:174] Opened db in 27.390206ms > I0427 01:52:33.038904 25032 leveldb.cpp:181] Compacted db in 22.386325ms > I0427 01:52:33.038946 25032 leveldb.cpp:196] Created db iterator in 8799ns > I0427 01:52:33.038978 25032 leveldb.cpp:202] Seeked to beginning of db in > 6289ns > I0427 01:52:33.039058 25032 leveldb.cpp:271] Iterated through 3 keys in the > db in 68062ns > I0427 01:52:33.039103 25032 replica.cpp:779] Replica recovered with log > positions 283 -> 284 with 0 holes and 0 unlearned > I0427 01:52:33.039850 25032 main.cpp:464] Starting Mesos master > I0427 01:52:33.040645 25032 master.cpp:374] Master > 49edc997-fbd4-4382-a043-dd7d18c8e517 (cluster01) started on > 192.168.50.167:5050 > I0427 01:52:33.040671 25032 master.cpp:376] Flags at startup: > --allocation_interval="1secs" --allocator="HierarchicalDRF" > --authenticate="true" --authenticate_http="true" > --authenticate_slaves="false" --authenticators="crammd5" > --authorizers="local" --cluster="mesos_cluster" > --credentials="/home/cloud-user/credentials" --framework_sorter="drf" > --help="false" --hostname="cluster01" --hostname_lookup="true" > --http_authenticators="basic" --initialize_driver_logging="true" > --ip="192.168.50.167" --log_auto_initialize="true" --log_dir="/var/log/mesos" > --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50" > --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5" > --port="5050" --quiet="false" --quorum="1" > --recovery_slave_removal_limit="100%" --registry="replicated_log" > --registry_fetch_timeout="1mins" --registry_store_timeout="5secs" > --registry_strict="false" --root_submissions="true" > --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins" > --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui" > --work_dir="/var/lib/mesos" --zk="zk://cluster01:2181/mesos" > --zk_session_timeout="10secs" > I0427 01:52:33.040864 25032 master.cpp:421] Master only allowing > authenticated frameworks to register > I0427 01:52:33.040876 25032 master.cpp:428] Master allowing unauthenticated > slaves to register > I0427 01:52:33.040885 25032 credentials.hpp:35] Loading credentials for > authentication from '/home/cloud-user/credentials' > I0427 01:52:33.040973 25032 master.cpp:466] Using default 'crammd5' > authenticator > I0427 01:52:33.041005 25032 authenticator.cpp:518] Initializing server SASL > I0427 01:52:33.041497 25032 master.cpp:535] Using default 'basic' HTTP > authenticator > I0427 01:52:33.044121 25037 log.cpp:236] Attempting to join replica to > ZooKeeper group > 2016-04-27 01:52:33,044:25032(0x7fa494c90700):ZOO_INFO@log_env@712: Client > environment:zookeeper.version=zookeeper C client 3.4.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5289) Basic Authentication for Mesos
[ https://issues.apache.org/jira/browse/MESOS-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259504#comment-15259504 ] rajeshwerrao madoori commented on MESOS-5289: - i have already found the documentation updated one which you have sent but not sure where its disconnecting everything looks fine in logs as of my knowledge but some how mesos-master is not picking up the credentials that i provide ..logs show that mesos is starting with the flags and the credentials file ... > Basic Authentication for Mesos > --- > > Key: MESOS-5289 > URL: https://issues.apache.org/jira/browse/MESOS-5289 > Project: Mesos > Issue Type: Bug > Components: framework, HTTP API, master, webui >Affects Versions: 0.27.0 > Environment: mesos framework production environment developer > environment >Reporter: rajeshwerrao madoori >Priority: Critical > Labels: documentation, features, mesosphere > > I have tried to use basic auth for Mesos-master used --authenticate=true > --authenticate_http=true --http_authenticators=basic > --credentials=/home/cloud-user/credentials > dint work for me also tried > --authenticate --authenticate_http --http_authenticators > --credentials=/home/cloud-user/credentials > using crammd5 as default .. > created credentials in a file with username password set file permissions to > 600 > logs show > I0427 01:52:32.988502 25032 logging.cpp:188] INFO level logging started! > I0427 01:52:32.988922 25032 main.cpp:230] Build: 2016-02-01 17:12:13 by root > I0427 01:52:32.988936 25032 main.cpp:232] Version: 0.27.0 > I0427 01:52:32.988943 25032 main.cpp:235] Git tag: 0.27.0 > I0427 01:52:32.988950 25032 main.cpp:239] Git SHA: > c29b3b6801846cda270aab17a670542ec5d238f5 > I0427 01:52:32.988992 25032 main.cpp:253] Using 'HierarchicalDRF' allocator > I0427 01:52:33.016451 25032 leveldb.cpp:174] Opened db in 27.390206ms > I0427 01:52:33.038904 25032 leveldb.cpp:181] Compacted db in 22.386325ms > I0427 01:52:33.038946 25032 leveldb.cpp:196] Created db iterator in 8799ns > I0427 01:52:33.038978 25032 leveldb.cpp:202] Seeked to beginning of db in > 6289ns > I0427 01:52:33.039058 25032 leveldb.cpp:271] Iterated through 3 keys in the > db in 68062ns > I0427 01:52:33.039103 25032 replica.cpp:779] Replica recovered with log > positions 283 -> 284 with 0 holes and 0 unlearned > I0427 01:52:33.039850 25032 main.cpp:464] Starting Mesos master > I0427 01:52:33.040645 25032 master.cpp:374] Master > 49edc997-fbd4-4382-a043-dd7d18c8e517 (cluster01) started on > 192.168.50.167:5050 > I0427 01:52:33.040671 25032 master.cpp:376] Flags at startup: > --allocation_interval="1secs" --allocator="HierarchicalDRF" > --authenticate="true" --authenticate_http="true" > --authenticate_slaves="false" --authenticators="crammd5" > --authorizers="local" --cluster="mesos_cluster" > --credentials="/home/cloud-user/credentials" --framework_sorter="drf" > --help="false" --hostname="cluster01" --hostname_lookup="true" > --http_authenticators="basic" --initialize_driver_logging="true" > --ip="192.168.50.167" --log_auto_initialize="true" --log_dir="/var/log/mesos" > --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50" > --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5" > --port="5050" --quiet="false" --quorum="1" > --recovery_slave_removal_limit="100%" --registry="replicated_log" > --registry_fetch_timeout="1mins" --registry_store_timeout="5secs" > --registry_strict="false" --root_submissions="true" > --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins" > --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui" > --work_dir="/var/lib/mesos" --zk="zk://cluster01:2181/mesos" > --zk_session_timeout="10secs" > I0427 01:52:33.040864 25032 master.cpp:421] Master only allowing > authenticated frameworks to register > I0427 01:52:33.040876 25032 master.cpp:428] Master allowing unauthenticated > slaves to register > I0427 01:52:33.040885 25032 credentials.hpp:35] Loading credentials for > authentication from '/home/cloud-user/credentials' > I0427 01:52:33.040973 25032 master.cpp:466] Using default 'crammd5' > authenticator > I0427 01:52:33.041005 25032 authenticator.cpp:518] Initializing server SASL > I0427 01:52:33.041497 25032 master.cpp:535] Using default 'basic' HTTP > authenticator > I0427 01:52:33.044121 25037 log.cpp:236] Attempting to join replica to > ZooKeeper group > 2016-04-27 01:52:33,044:25032(0x7fa494c90700):ZOO_INFO@log_env@712: Client > environment:zookeeper.version=zookeeper C client 3.4.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5289) Basic Authentication for Mesos
[ https://issues.apache.org/jira/browse/MESOS-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rajeshwerrao madoori updated MESOS-5289: Issue Type: Bug (was: Improvement) > Basic Authentication for Mesos > --- > > Key: MESOS-5289 > URL: https://issues.apache.org/jira/browse/MESOS-5289 > Project: Mesos > Issue Type: Bug > Components: framework, HTTP API, master, webui >Affects Versions: 0.27.0 > Environment: mesos framework production environment developer > environment >Reporter: rajeshwerrao madoori >Priority: Critical > Labels: documentation, features, mesosphere > > I have tried to use basic auth for Mesos-master used --authenticate=true > --authenticate_http=true --http_authenticators=basic > --credentials=/home/cloud-user/credentials > dint work for me also tried > --authenticate --authenticate_http --http_authenticators > --credentials=/home/cloud-user/credentials > using crammd5 as default .. > created credentials in a file with username password set file permissions to > 600 > logs show > I0427 01:52:32.988502 25032 logging.cpp:188] INFO level logging started! > I0427 01:52:32.988922 25032 main.cpp:230] Build: 2016-02-01 17:12:13 by root > I0427 01:52:32.988936 25032 main.cpp:232] Version: 0.27.0 > I0427 01:52:32.988943 25032 main.cpp:235] Git tag: 0.27.0 > I0427 01:52:32.988950 25032 main.cpp:239] Git SHA: > c29b3b6801846cda270aab17a670542ec5d238f5 > I0427 01:52:32.988992 25032 main.cpp:253] Using 'HierarchicalDRF' allocator > I0427 01:52:33.016451 25032 leveldb.cpp:174] Opened db in 27.390206ms > I0427 01:52:33.038904 25032 leveldb.cpp:181] Compacted db in 22.386325ms > I0427 01:52:33.038946 25032 leveldb.cpp:196] Created db iterator in 8799ns > I0427 01:52:33.038978 25032 leveldb.cpp:202] Seeked to beginning of db in > 6289ns > I0427 01:52:33.039058 25032 leveldb.cpp:271] Iterated through 3 keys in the > db in 68062ns > I0427 01:52:33.039103 25032 replica.cpp:779] Replica recovered with log > positions 283 -> 284 with 0 holes and 0 unlearned > I0427 01:52:33.039850 25032 main.cpp:464] Starting Mesos master > I0427 01:52:33.040645 25032 master.cpp:374] Master > 49edc997-fbd4-4382-a043-dd7d18c8e517 (cluster01) started on > 192.168.50.167:5050 > I0427 01:52:33.040671 25032 master.cpp:376] Flags at startup: > --allocation_interval="1secs" --allocator="HierarchicalDRF" > --authenticate="true" --authenticate_http="true" > --authenticate_slaves="false" --authenticators="crammd5" > --authorizers="local" --cluster="mesos_cluster" > --credentials="/home/cloud-user/credentials" --framework_sorter="drf" > --help="false" --hostname="cluster01" --hostname_lookup="true" > --http_authenticators="basic" --initialize_driver_logging="true" > --ip="192.168.50.167" --log_auto_initialize="true" --log_dir="/var/log/mesos" > --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50" > --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5" > --port="5050" --quiet="false" --quorum="1" > --recovery_slave_removal_limit="100%" --registry="replicated_log" > --registry_fetch_timeout="1mins" --registry_store_timeout="5secs" > --registry_strict="false" --root_submissions="true" > --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins" > --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui" > --work_dir="/var/lib/mesos" --zk="zk://cluster01:2181/mesos" > --zk_session_timeout="10secs" > I0427 01:52:33.040864 25032 master.cpp:421] Master only allowing > authenticated frameworks to register > I0427 01:52:33.040876 25032 master.cpp:428] Master allowing unauthenticated > slaves to register > I0427 01:52:33.040885 25032 credentials.hpp:35] Loading credentials for > authentication from '/home/cloud-user/credentials' > I0427 01:52:33.040973 25032 master.cpp:466] Using default 'crammd5' > authenticator > I0427 01:52:33.041005 25032 authenticator.cpp:518] Initializing server SASL > I0427 01:52:33.041497 25032 master.cpp:535] Using default 'basic' HTTP > authenticator > I0427 01:52:33.044121 25037 log.cpp:236] Attempting to join replica to > ZooKeeper group > 2016-04-27 01:52:33,044:25032(0x7fa494c90700):ZOO_INFO@log_env@712: Client > environment:zookeeper.version=zookeeper C client 3.4.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5270) Replace Master/Slave Terminology Phase I - Duplicate slave field in JSON responses.
[ https://issues.apache.org/jira/browse/MESOS-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259487#comment-15259487 ] Vinod Kone commented on MESOS-5270: --- We will do this is part of the operator v1 API. > Replace Master/Slave Terminology Phase I - Duplicate slave field in JSON > responses. > --- > > Key: MESOS-5270 > URL: https://issues.apache.org/jira/browse/MESOS-5270 > Project: Mesos > Issue Type: Task >Reporter: Jay Guo > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3778) Slave/Agent Rename Phase I - Add duplicate HTTP endpoints
[ https://issues.apache.org/jira/browse/MESOS-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259485#comment-15259485 ] Vinod Kone commented on MESOS-3778: --- We will do this is as part of the v1 Operator API. > Slave/Agent Rename Phase I - Add duplicate HTTP endpoints > - > > Key: MESOS-3778 > URL: https://issues.apache.org/jira/browse/MESOS-3778 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5283) LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox is flaky.
[
https://issues.apache.org/jira/browse/MESOS-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilbert Song updated MESOS-5283:
Environment: CentOS 7 without SSL (was: CentOS without SSL)
> LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox is flaky.
>
>
> Key: MESOS-5283
> URL: https://issues.apache.org/jira/browse/MESOS-5283
> Project: Mesos
> Issue Type: Bug
> Components: tests
> Environment: CentOS 7 without SSL
>Reporter: Gilbert Song
> Labels: mesosphere
>
> Observed on the internal Mesosphere CI:
> {code}
> [23:10:03] : [Step 10/10] [ RUN ]
> LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
> [23:10:05]W: [Step 10/10] I0425 23:10:05.061769 32151 linux.cpp:81] Making
> '/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC'
> a shared mount
> [23:10:05]W: [Step 10/10] I0425 23:10:05.074729 32151
> linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
> for the Linux launcher
> [23:10:05]W: [Step 10/10] I0425 23:10:05.075099 32170
> containerizer.cpp:703] Starting container
> '14a48c04-9157-4796-8743-f37ad5da05d1' for executor 'test_executor' of
> framework ''
> [23:10:05]W: [Step 10/10] I0425 23:10:05.075275 32168 provisioner.cpp:285]
> Provisioning image rootfs
> '/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC/provisioner/containers/14a48c04-9157-4796-8743-f37ad5da05d1/backends/copy/rootfses/f47a2ca8-b8bc-4bfa-bfaf-788c2eb33b49'
> for container 14a48c04-9157-4796-8743-f37ad5da05d1
> [23:10:05]W: [Step 10/10] I0425 23:10:05.075589 32166 copy.cpp:128] Copying
> layer path '/tmp/uK310o/test_image' to rootfs
> '/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC/provisioner/containers/14a48c04-9157-4796-8743-f37ad5da05d1/backends/copy/rootfses/f47a2ca8-b8bc-4bfa-bfaf-788c2eb33b49'
> [23:10:09]W: [Step 10/10] I0425 23:10:09.184612 32165 linux.cpp:355] Bind
> mounting work directory from '/tmp/uK310o/sandbox' to
> '/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC/provisioner/containers/14a48c04-9157-4796-8743-f37ad5da05d1/backends/copy/rootfses/f47a2ca8-b8bc-4bfa-bfaf-788c2eb33b49/mnt/mesos/sandbox'
> for container 14a48c04-9157-4796-8743-f37ad5da05d1
> [23:10:09]W: [Step 10/10] I0425 23:10:09.185264 32167
> linux_launcher.cpp:281] Cloning child process with flags = CLONE_NEWNS
> [23:10:09]W: [Step 10/10] +
> /mnt/teamcity/work/4240ba9ddd0997c3/build/src/mesos-containerizer mount
> --help=false --operation=make-rslave --path=/
> [23:10:09]W: [Step 10/10] + grep -E
> /mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC/.+
> /proc/self/mountinfo
> [23:10:09]W: [Step 10/10] + grep -v 14a48c04-9157-4796-8743-f37ad5da05d1
> [23:10:09]W: [Step 10/10] + cut '-d ' -f5
> [23:10:09]W: [Step 10/10] + xargs --no-run-if-empty umount -l
> [23:10:09]W: [Step 10/10] + mount -n --rbind /tmp/uK310o/sandbox/tmp
> /mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC/provisioner/containers/14a48c04-9157-4796-8743-f37ad5da05d1/backends/copy/rootfses/f47a2ca8-b8bc-4bfa-bfaf-788c2eb33b49/tmp
> [23:10:09] : [Step 10/10] Changing root to
> /mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_VolumeFromSandbox_vndkVC/provisioner/containers/14a48c04-9157-4796-8743-f37ad5da05d1/backends/copy/rootfses/f47a2ca8-b8bc-4bfa-bfaf-788c2eb33b49
> [23:10:09]W: [Step 10/10] I0425 23:10:09.284610 32170
> containerizer.cpp:1717] Executor for container
> '14a48c04-9157-4796-8743-f37ad5da05d1' has exited
> [23:10:09]W: [Step 10/10] I0425 23:10:09.284638 32170
> containerizer.cpp:1481] Destroying container
> '14a48c04-9157-4796-8743-f37ad5da05d1'
> [23:10:09]W: [Step 10/10] I0425 23:10:09.286339 32172 cgroups.cpp:2676]
> Freezing cgroup
> /sys/fs/cgroup/freezer/mesos/14a48c04-9157-4796-8743-f37ad5da05d1
> [23:10:09]W: [Step 10/10] I0425 23:10:09.287952 32169 cgroups.cpp:1409]
> Successfully froze cgroup
> /sys/fs/cgroup/freezer/mesos/14a48c04-9157-4796-8743-f37ad5da05d1 after
> 1.587712ms
> [23:10:09]W: [Step 10/10] I0425 23:10:09.289566 32171 cgroups.cpp:2694]
> Thawing cgroup
> /sys/fs/cgroup/freezer/mesos/14a48c04-9157-4796-8743-f37ad5da05d1
> [23:10:09]W: [Step 10/10] I0425 23:10:09.290956 32171 cgroups.cpp:1438]
> Successfully thawed cgroup
> /sys/fs/cgroup/freezer/mesos/14a48c04-9157-4796-8743-f37ad5da05d1 after
> 1.371904ms
> [23:10:09]W: [Step 10/10] I0425 23:10:09.292289 32167 linux.cpp:825]
> Unmounting sandbox/work directory
>
[jira] [Created] (MESOS-5291) LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable is flaky.
Gilbert Song created MESOS-5291:
---
Summary:
LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable is flaky.
Key: MESOS-5291
URL: https://issues.apache.org/jira/browse/MESOS-5291
Project: Mesos
Issue Type: Bug
Components: tests
Environment: CentOS 7 without SSL
Reporter: Gilbert Song
Observed on the internal Mesosphere CI:
{code}
[03:05:29] : [Step 10/10] [ RUN ]
LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
[03:05:30]W: [Step 10/10] I0427 03:05:30.880957 32158 linux.cpp:81] Making
'/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900'
a shared mount
[03:05:30]W: [Step 10/10] I0427 03:05:30.893527 32158
linux_launcher.cpp:101] Using /sys/fs/cgroup/freezer as the freezer hierarchy
for the Linux launcher
[03:05:30]W: [Step 10/10] I0427 03:05:30.893870 32176
containerizer.cpp:703] Starting container
'5c2eecfd-75a4-416a-b8e9-fba620274c97' for executor 'test_executor' of
framework ''
[03:05:30]W: [Step 10/10] I0427 03:05:30.894084 32172 provisioner.cpp:285]
Provisioning image rootfs
'/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/provisioner/containers/5c2eecfd-75a4-416a-b8e9-fba620274c97/backends/copy/rootfses/0e8c0218-6551-4dea-abf5-20e9f729dcf9'
for container 5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:30]W: [Step 10/10] I0427 03:05:30.894450 32177 copy.cpp:128] Copying
layer path '/tmp/dKE6qq/test_image' to rootfs
'/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/provisioner/containers/5c2eecfd-75a4-416a-b8e9-fba620274c97/backends/copy/rootfses/0e8c0218-6551-4dea-abf5-20e9f729dcf9'
[03:05:35]W: [Step 10/10] I0427 03:05:35.358980 32172 linux.cpp:355] Bind
mounting work directory from '/tmp/dKE6qq/sandbox' to
'/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/provisioner/containers/5c2eecfd-75a4-416a-b8e9-fba620274c97/backends/copy/rootfses/0e8c0218-6551-4dea-abf5-20e9f729dcf9/mnt/mesos/sandbox'
for container 5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:35]W: [Step 10/10] I0427 03:05:35.359519 32174
linux_launcher.cpp:281] Cloning child process with flags = CLONE_NEWNS
[03:05:35]W: [Step 10/10] +
/mnt/teamcity/work/4240ba9ddd0997c3/build/src/mesos-containerizer mount
--help=false --operation=make-rslave --path=/
[03:05:35]W: [Step 10/10] + grep -E
/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/.+
/proc/self/mountinfo
[03:05:35]W: [Step 10/10] + grep -v 5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:35]W: [Step 10/10] + cut '-d ' -f5
[03:05:35]W: [Step 10/10] + xargs --no-run-if-empty umount -l
[03:05:35] : [Step 10/10] Changing root to
/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/provisioner/containers/5c2eecfd-75a4-416a-b8e9-fba620274c97/backends/copy/rootfses/0e8c0218-6551-4dea-abf5-20e9f729dcf9
[03:05:35]W: [Step 10/10] I0427 03:05:35.459079 32173
containerizer.cpp:1717] Executor for container
'5c2eecfd-75a4-416a-b8e9-fba620274c97' has exited
[03:05:35]W: [Step 10/10] I0427 03:05:35.459105 32173
containerizer.cpp:1481] Destroying container
'5c2eecfd-75a4-416a-b8e9-fba620274c97'
[03:05:35]W: [Step 10/10] I0427 03:05:35.460752 32173 cgroups.cpp:2676]
Freezing cgroup
/sys/fs/cgroup/freezer/mesos/5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:35]W: [Step 10/10] I0427 03:05:35.462360 32172 cgroups.cpp:1409]
Successfully froze cgroup
/sys/fs/cgroup/freezer/mesos/5c2eecfd-75a4-416a-b8e9-fba620274c97 after
1.578752ms
[03:05:35]W: [Step 10/10] I0427 03:05:35.463892 32176 cgroups.cpp:2694]
Thawing cgroup /sys/fs/cgroup/freezer/mesos/5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:35]W: [Step 10/10] I0427 03:05:35.465405 32173 cgroups.cpp:1438]
Successfully thawed cgroup
/sys/fs/cgroup/freezer/mesos/5c2eecfd-75a4-416a-b8e9-fba620274c97 after
1.494272ms
[03:05:35]W: [Step 10/10] I0427 03:05:35.466672 32177 linux.cpp:825]
Unmounting sandbox/work directory
'/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/provisioner/containers/5c2eecfd-75a4-416a-b8e9-fba620274c97/backends/copy/rootfses/0e8c0218-6551-4dea-abf5-20e9f729dcf9/mnt/mesos/sandbox'
for container 5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:35]W: [Step 10/10] I0427 03:05:35.466837 32176 provisioner.cpp:338]
Destroying container rootfs at
'/mnt/teamcity/temp/buildTmp/LinuxFilesystemIsolatorTest_ROOT_SandboxEnvironmentVariable_TU5900/provisioner/containers/5c2eecfd-75a4-416a-b8e9-fba620274c97/backends/copy/rootfses/0e8c0218-6551-4dea-abf5-20e9f729dcf9'
for container 5c2eecfd-75a4-416a-b8e9-fba620274c97
[03:05:50] : [Step 10/10]
[jira] [Updated] (MESOS-1478) Slave to Agent rename.
[ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-1478: -- Shepherd: Vinod Kone (was: Dave Lester) Assignee: (was: Benjamin Hindman) > Slave to Agent rename. > -- > > Key: MESOS-1478 > URL: https://issues.apache.org/jira/browse/MESOS-1478 > Project: Mesos > Issue Type: Epic >Reporter: Clark Breyman >Priority: Minor > Labels: mesosphere > > Inspired by the comments on this PR: > https://github.com/django/django/pull/2692 > TL;DR - Computers sharing work should be a good thing. Using the language of > human bondage and suffering is inappropriate in this context. It also has the > potential to alienate users and community members. > Working document: > https://docs.google.com/document/d/1P8_4wdk29I6NoVTjbFkRl05-tfxV9PY4WLoRNvExupM/edit#heading=h.9g7fqjh6652v -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3777) Replace Master/Slave Terminology Phase I - Modify public interfaces
[ https://issues.apache.org/jira/browse/MESOS-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259476#comment-15259476 ] Vinod Kone commented on MESOS-3777: --- [~darroyo] unassigning you since you no longer seems active on this project. This will let someone else pick it up. > Replace Master/Slave Terminology Phase I - Modify public interfaces > > > Key: MESOS-3777 > URL: https://issues.apache.org/jira/browse/MESOS-3777 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3777) Replace Master/Slave Terminology Phase I - Modify public interfaces
[ https://issues.apache.org/jira/browse/MESOS-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-3777: -- Description: (was: [~darroyo] unassigning you since you no longer seems active on this project. This will let someone else pick it up.) > Replace Master/Slave Terminology Phase I - Modify public interfaces > > > Key: MESOS-3777 > URL: https://issues.apache.org/jira/browse/MESOS-3777 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5269) Replace Master/Slave Terminology Phase I - Update Metrics
[ https://issues.apache.org/jira/browse/MESOS-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259467#comment-15259467 ] Vinod Kone commented on MESOS-5269: --- The WebUI can still use slave/uptime_seconds. I was just expecting the externally visible elements to say agent instead of slave. Does that make sense? Or am I missing something? > Replace Master/Slave Terminology Phase I - Update Metrics > - > > Key: MESOS-5269 > URL: https://issues.apache.org/jira/browse/MESOS-5269 > Project: Mesos > Issue Type: Task >Reporter: Jay Guo > > process::metrics::Gauge slaves_connected; > process::metrics::Gauge slaves_disconnected; > process::metrics::Gauge slaves_active; > process::metrics::Gauge slaves_inactive; > process::metrics::Counter messages_register_slave; > process::metrics::Counter messages_reregister_slave; > process::metrics::Counter messages_unregister_slave; > process::metrics::Counter messages_update_slave; > process::metrics::Counter recovery_slave_removals; > process::metrics::Counter slave_registrations; > process::metrics::Counter slave_reregistrations; > process::metrics::Counter slave_removals; > process::metrics::Counter slave_removals_reason_unhealthy; > process::metrics::Counter slave_removals_reason_unregistered; > process::metrics::Counter slave_removals_reason_registered; > process::metrics::Counter slave_shutdowns_scheduled; > process::metrics::Counter slave_shutdowns_completed; > process::metrics::Counter slave_shutdowns_canceled; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5289) Basic Authentication for Mesos
[ https://issues.apache.org/jira/browse/MESOS-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259463#comment-15259463 ] Gilbert Song commented on MESOS-5289: - Hi [~rmadoori], it seems to me that this is not an `improvement` issue. Understand that this is critical to you, but we usually file a JIRA for a specific issue (e.g., a bug, a task etc.). For user related issues, we encourage users to email their questions/concerns to mesos user mailing list (u...@mesos.apache.org), which may be seem by more users/developers, so it is more possibly to get help:). >From the description above, it seems you are blocked when using mesos >authentication. The authentication document may be helpful >(http://mesos.apache.org/documentation/latest/authentication/). > Basic Authentication for Mesos > --- > > Key: MESOS-5289 > URL: https://issues.apache.org/jira/browse/MESOS-5289 > Project: Mesos > Issue Type: Improvement > Components: framework, HTTP API, master, webui >Affects Versions: 0.27.0 > Environment: mesos framework production environment developer > environment >Reporter: rajeshwerrao madoori >Priority: Critical > Labels: documentation, features, mesosphere > > I have tried to use basic auth for Mesos-master used --authenticate=true > --authenticate_http=true --http_authenticators=basic > --credentials=/home/cloud-user/credentials > dint work for me also tried > --authenticate --authenticate_http --http_authenticators > --credentials=/home/cloud-user/credentials > using crammd5 as default .. > created credentials in a file with username password set file permissions to > 600 > logs show > I0427 01:52:32.988502 25032 logging.cpp:188] INFO level logging started! > I0427 01:52:32.988922 25032 main.cpp:230] Build: 2016-02-01 17:12:13 by root > I0427 01:52:32.988936 25032 main.cpp:232] Version: 0.27.0 > I0427 01:52:32.988943 25032 main.cpp:235] Git tag: 0.27.0 > I0427 01:52:32.988950 25032 main.cpp:239] Git SHA: > c29b3b6801846cda270aab17a670542ec5d238f5 > I0427 01:52:32.988992 25032 main.cpp:253] Using 'HierarchicalDRF' allocator > I0427 01:52:33.016451 25032 leveldb.cpp:174] Opened db in 27.390206ms > I0427 01:52:33.038904 25032 leveldb.cpp:181] Compacted db in 22.386325ms > I0427 01:52:33.038946 25032 leveldb.cpp:196] Created db iterator in 8799ns > I0427 01:52:33.038978 25032 leveldb.cpp:202] Seeked to beginning of db in > 6289ns > I0427 01:52:33.039058 25032 leveldb.cpp:271] Iterated through 3 keys in the > db in 68062ns > I0427 01:52:33.039103 25032 replica.cpp:779] Replica recovered with log > positions 283 -> 284 with 0 holes and 0 unlearned > I0427 01:52:33.039850 25032 main.cpp:464] Starting Mesos master > I0427 01:52:33.040645 25032 master.cpp:374] Master > 49edc997-fbd4-4382-a043-dd7d18c8e517 (cluster01) started on > 192.168.50.167:5050 > I0427 01:52:33.040671 25032 master.cpp:376] Flags at startup: > --allocation_interval="1secs" --allocator="HierarchicalDRF" > --authenticate="true" --authenticate_http="true" > --authenticate_slaves="false" --authenticators="crammd5" > --authorizers="local" --cluster="mesos_cluster" > --credentials="/home/cloud-user/credentials" --framework_sorter="drf" > --help="false" --hostname="cluster01" --hostname_lookup="true" > --http_authenticators="basic" --initialize_driver_logging="true" > --ip="192.168.50.167" --log_auto_initialize="true" --log_dir="/var/log/mesos" > --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50" > --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5" > --port="5050" --quiet="false" --quorum="1" > --recovery_slave_removal_limit="100%" --registry="replicated_log" > --registry_fetch_timeout="1mins" --registry_store_timeout="5secs" > --registry_strict="false" --root_submissions="true" > --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins" > --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui" > --work_dir="/var/lib/mesos" --zk="zk://cluster01:2181/mesos" > --zk_session_timeout="10secs" > I0427 01:52:33.040864 25032 master.cpp:421] Master only allowing > authenticated frameworks to register > I0427 01:52:33.040876 25032 master.cpp:428] Master allowing unauthenticated > slaves to register > I0427 01:52:33.040885 25032 credentials.hpp:35] Loading credentials for > authentication from '/home/cloud-user/credentials' > I0427 01:52:33.040973 25032 master.cpp:466] Using default 'crammd5' > authenticator > I0427 01:52:33.041005 25032 authenticator.cpp:518] Initializing server SASL > I0427 01:52:33.041497 25032 master.cpp:535] Using default 'basic' HTTP > authenticator > I0427 01:52:33.044121 25037 log.cpp:236] Attempting to join replica to > ZooKeeper group > 2016-04-27 01:52:33,044:25032(0x7fa494c90700):ZOO_INFO@log_env@712: Client
[jira] [Created] (MESOS-5290) WebUI shows the active task is launched 46 years ago
zhou xing created MESOS-5290: Summary: WebUI shows the active task is launched 46 years ago Key: MESOS-5290 URL: https://issues.apache.org/jira/browse/MESOS-5290 Project: Mesos Issue Type: Bug Components: webui Reporter: zhou xing Assignee: zhou xing Priority: Minor When running the long-lived-framework, the active tasks column on webUI shows the task is launched 46 years ago, which should be launched just now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5269) Replace Master/Slave Terminology Phase I - Update Metrics
[
https://issues.apache.org/jira/browse/MESOS-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259440#comment-15259440
]
Jay Guo commented on MESOS-5269:
Agreed. However, WebUI currently relies on JSON attributes returned by endpoint
/metrics/snapshot, e.g. {{slave/uptime_secs}}. We have two options to duplicate
returned attributes:
1. Duplicate the metric itself. Although this results in possible inconsistency
of {{slave/XXX: valueX}} and {{agent/YYY: valueY}}, since metric->value() is
called twice.
2. Duplicate the field in JSON before return. This simply manipulates JSON
string before returning it. Although it's in libprocess and having this kinda
operation there is quite awkward.
Ideas?
> Replace Master/Slave Terminology Phase I - Update Metrics
> -
>
> Key: MESOS-5269
> URL: https://issues.apache.org/jira/browse/MESOS-5269
> Project: Mesos
> Issue Type: Task
>Reporter: Jay Guo
>
> process::metrics::Gauge slaves_connected;
> process::metrics::Gauge slaves_disconnected;
> process::metrics::Gauge slaves_active;
> process::metrics::Gauge slaves_inactive;
> process::metrics::Counter messages_register_slave;
> process::metrics::Counter messages_reregister_slave;
> process::metrics::Counter messages_unregister_slave;
> process::metrics::Counter messages_update_slave;
> process::metrics::Counter recovery_slave_removals;
> process::metrics::Counter slave_registrations;
> process::metrics::Counter slave_reregistrations;
> process::metrics::Counter slave_removals;
> process::metrics::Counter slave_removals_reason_unhealthy;
> process::metrics::Counter slave_removals_reason_unregistered;
> process::metrics::Counter slave_removals_reason_registered;
> process::metrics::Counter slave_shutdowns_scheduled;
> process::metrics::Counter slave_shutdowns_completed;
> process::metrics::Counter slave_shutdowns_canceled;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-5289) Basic Authentication for Mesos
rajeshwerrao madoori created MESOS-5289: --- Summary: Basic Authentication for Mesos Key: MESOS-5289 URL: https://issues.apache.org/jira/browse/MESOS-5289 Project: Mesos Issue Type: Improvement Components: framework, HTTP API, master, webui Affects Versions: 0.27.0 Environment: mesos framework production environment developer environment Reporter: rajeshwerrao madoori Priority: Critical I have tried to use basic auth for Mesos-master used --authenticate=true --authenticate_http=true --http_authenticators=basic --credentials=/home/cloud-user/credentials dint work for me also tried --authenticate --authenticate_http --http_authenticators --credentials=/home/cloud-user/credentials using crammd5 as default .. created credentials in a file with username password set file permissions to 600 logs show I0427 01:52:32.988502 25032 logging.cpp:188] INFO level logging started! I0427 01:52:32.988922 25032 main.cpp:230] Build: 2016-02-01 17:12:13 by root I0427 01:52:32.988936 25032 main.cpp:232] Version: 0.27.0 I0427 01:52:32.988943 25032 main.cpp:235] Git tag: 0.27.0 I0427 01:52:32.988950 25032 main.cpp:239] Git SHA: c29b3b6801846cda270aab17a670542ec5d238f5 I0427 01:52:32.988992 25032 main.cpp:253] Using 'HierarchicalDRF' allocator I0427 01:52:33.016451 25032 leveldb.cpp:174] Opened db in 27.390206ms I0427 01:52:33.038904 25032 leveldb.cpp:181] Compacted db in 22.386325ms I0427 01:52:33.038946 25032 leveldb.cpp:196] Created db iterator in 8799ns I0427 01:52:33.038978 25032 leveldb.cpp:202] Seeked to beginning of db in 6289ns I0427 01:52:33.039058 25032 leveldb.cpp:271] Iterated through 3 keys in the db in 68062ns I0427 01:52:33.039103 25032 replica.cpp:779] Replica recovered with log positions 283 -> 284 with 0 holes and 0 unlearned I0427 01:52:33.039850 25032 main.cpp:464] Starting Mesos master I0427 01:52:33.040645 25032 master.cpp:374] Master 49edc997-fbd4-4382-a043-dd7d18c8e517 (cluster01) started on 192.168.50.167:5050 I0427 01:52:33.040671 25032 master.cpp:376] Flags at startup: --allocation_interval="1secs" --allocator="HierarchicalDRF" --authenticate="true" --authenticate_http="true" --authenticate_slaves="false" --authenticators="crammd5" --authorizers="local" --cluster="mesos_cluster" --credentials="/home/cloud-user/credentials" --framework_sorter="drf" --help="false" --hostname="cluster01" --hostname_lookup="true" --http_authenticators="basic" --initialize_driver_logging="true" --ip="192.168.50.167" --log_auto_initialize="true" --log_dir="/var/log/mesos" --logbufsecs="0" --logging_level="INFO" --max_completed_frameworks="50" --max_completed_tasks_per_framework="1000" --max_slave_ping_timeouts="5" --port="5050" --quiet="false" --quorum="1" --recovery_slave_removal_limit="100%" --registry="replicated_log" --registry_fetch_timeout="1mins" --registry_store_timeout="5secs" --registry_strict="false" --root_submissions="true" --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins" --user_sorter="drf" --version="false" --webui_dir="/usr/share/mesos/webui" --work_dir="/var/lib/mesos" --zk="zk://cluster01:2181/mesos" --zk_session_timeout="10secs" I0427 01:52:33.040864 25032 master.cpp:421] Master only allowing authenticated frameworks to register I0427 01:52:33.040876 25032 master.cpp:428] Master allowing unauthenticated slaves to register I0427 01:52:33.040885 25032 credentials.hpp:35] Loading credentials for authentication from '/home/cloud-user/credentials' I0427 01:52:33.040973 25032 master.cpp:466] Using default 'crammd5' authenticator I0427 01:52:33.041005 25032 authenticator.cpp:518] Initializing server SASL I0427 01:52:33.041497 25032 master.cpp:535] Using default 'basic' HTTP authenticator I0427 01:52:33.044121 25037 log.cpp:236] Attempting to join replica to ZooKeeper group 2016-04-27 01:52:33,044:25032(0x7fa494c90700):ZOO_INFO@log_env@712: Client environment:zookeeper.version=zookeeper C client 3.4.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3779) Slave/Agent Rename Phase I - Update webui
[ https://issues.apache.org/jira/browse/MESOS-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259408#comment-15259408 ] Vinod Kone commented on MESOS-3779: --- As discussed offline, lets do the changes purely in the webui code for 1,2 and 3. > Slave/Agent Rename Phase I - Update webui > - > > Key: MESOS-3779 > URL: https://issues.apache.org/jira/browse/MESOS-3779 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3784) Replace Master/Slave Terminology Phase I - Update mesos-cli
[ https://issues.apache.org/jira/browse/MESOS-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-3784: -- [~darroyo] unassigning you since you no longer seems active on this project. This will let someone else pick it up. > Replace Master/Slave Terminology Phase I - Update mesos-cli > > > Key: MESOS-3784 > URL: https://issues.apache.org/jira/browse/MESOS-3784 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3784) Replace Master/Slave Terminology Phase I - Update mesos-cli
[ https://issues.apache.org/jira/browse/MESOS-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-3784: -- Description: (was: [~darroyo] unassigning you since you no longer seems active on this project. This will let someone else pick it up.) > Replace Master/Slave Terminology Phase I - Update mesos-cli > > > Key: MESOS-3784 > URL: https://issues.apache.org/jira/browse/MESOS-3784 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5269) Replace Master/Slave Terminology Phase I - Update Metrics
[ https://issues.apache.org/jira/browse/MESOS-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259403#comment-15259403 ] Vinod Kone commented on MESOS-5269: --- I think gauges and counters having aliases is a bit weird. I would rather we fix this as part of the v1 operator API rather than having duplicates in some operator endpoints (e.g., metrics). > Replace Master/Slave Terminology Phase I - Update Metrics > - > > Key: MESOS-5269 > URL: https://issues.apache.org/jira/browse/MESOS-5269 > Project: Mesos > Issue Type: Task >Reporter: Jay Guo > > process::metrics::Gauge slaves_connected; > process::metrics::Gauge slaves_disconnected; > process::metrics::Gauge slaves_active; > process::metrics::Gauge slaves_inactive; > process::metrics::Counter messages_register_slave; > process::metrics::Counter messages_reregister_slave; > process::metrics::Counter messages_unregister_slave; > process::metrics::Counter messages_update_slave; > process::metrics::Counter recovery_slave_removals; > process::metrics::Counter slave_registrations; > process::metrics::Counter slave_reregistrations; > process::metrics::Counter slave_removals; > process::metrics::Counter slave_removals_reason_unhealthy; > process::metrics::Counter slave_removals_reason_unregistered; > process::metrics::Counter slave_removals_reason_registered; > process::metrics::Counter slave_shutdowns_scheduled; > process::metrics::Counter slave_shutdowns_completed; > process::metrics::Counter slave_shutdowns_canceled; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5278) Add a CLI allowing a user to enter a container.
[
https://issues.apache.org/jira/browse/MESOS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259388#comment-15259388
]
haosdent commented on MESOS-5278:
-
I use homebrew to install mesos, and could find it. mesos-ps maps to
{{src/cli/mesos-ps}} in Mesos code.
{code}
mesos help
Usage: mesos [OPTIONS]
Available commands:
help
cat
execute
local
log
ps
resolve
scp
tail
daemon.sh
master
slave
start-cluster.sh
start-masters.sh
start-slaves.sh
stop-cluster.sh
stop-masters.sh
stop-slaves.sh
cat
execute
local
log
ps
resolve
scp
tail
{code}
> Add a CLI allowing a user to enter a container.
> ---
>
> Key: MESOS-5278
> URL: https://issues.apache.org/jira/browse/MESOS-5278
> Project: Mesos
> Issue Type: Improvement
>Reporter: Jie Yu
>Assignee: Guangya Liu
>
> Containers created by the unified containerizer (Mesos containerizer) uses
> various namespaces (e.g., mount, network, etc.).
> To improve debugability, we should create a CLI that allows an operator or a
> user to enter the namespaces associated with the container, and execute an
> arbitrary command in that container (similar to `docker exec`).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3778) Slave/Agent Rename Phase I - Add duplicate HTTP endpoints
[ https://issues.apache.org/jira/browse/MESOS-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing updated MESOS-3778: - Summary: Slave/Agent Rename Phase I - Add duplicate HTTP endpoints (was: Replace Master/Slave Terminology Phase I - Add duplicate HTTP endpoints) > Slave/Agent Rename Phase I - Add duplicate HTTP endpoints > - > > Key: MESOS-3778 > URL: https://issues.apache.org/jira/browse/MESOS-3778 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3779) Slave/Agent Rename Phase I - Update webui
[ https://issues.apache.org/jira/browse/MESOS-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing updated MESOS-3779: - Summary: Slave/Agent Rename Phase I - Update webui (was: Replace Master/Slave Terminology Phase I - Update webui) > Slave/Agent Rename Phase I - Update webui > - > > Key: MESOS-3779 > URL: https://issues.apache.org/jira/browse/MESOS-3779 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo >Assignee: zhou xing > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-5278) Add a CLI allowing a user to enter a container.
[ https://issues.apache.org/jira/browse/MESOS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangya Liu reassigned MESOS-5278: -- Assignee: Guangya Liu > Add a CLI allowing a user to enter a container. > --- > > Key: MESOS-5278 > URL: https://issues.apache.org/jira/browse/MESOS-5278 > Project: Mesos > Issue Type: Improvement >Reporter: Jie Yu >Assignee: Guangya Liu > > Containers created by the unified containerizer (Mesos containerizer) uses > various namespaces (e.g., mount, network, etc.). > To improve debugability, we should create a CLI that allows an operator or a > user to enter the namespaces associated with the container, and execute an > arbitrary command in that container (similar to `docker exec`). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5278) Add a CLI allowing a user to enter a container.
[
https://issues.apache.org/jira/browse/MESOS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259339#comment-15259339
]
Guangya Liu commented on MESOS-5278:
[~idownes] Which mesos command are you using? I tried `mesos` command but found
that it does not have the `ps` option.
{code}
root@mesos002:~/src/mesos/m3/mesos/build/src# ./mesos --help
Not expecting '--help' before command
Usage: lt-mesos [OPTIONS]
Available commands:
help
health-check
execute
docker-executor
resolve
containerizer
executor
logrotate-logger
usage
master
fetcher
agent
log
tests
slave
http-executor
local
{code}
> Add a CLI allowing a user to enter a container.
> ---
>
> Key: MESOS-5278
> URL: https://issues.apache.org/jira/browse/MESOS-5278
> Project: Mesos
> Issue Type: Improvement
>Reporter: Jie Yu
>
> Containers created by the unified containerizer (Mesos containerizer) uses
> various namespaces (e.g., mount, network, etc.).
> To improve debugability, we should create a CLI that allows an operator or a
> user to enter the namespaces associated with the container, and execute an
> arbitrary command in that container (similar to `docker exec`).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5057) Slave/Agent Rename Phase I - Update strings in error messages and other strings
[ https://issues.apache.org/jira/browse/MESOS-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing updated MESOS-5057: - Summary: Slave/Agent Rename Phase I - Update strings in error messages and other strings (was: Replace Master/Slave Terminology Phase I - Update strings in error messages and other strings) > Slave/Agent Rename Phase I - Update strings in error messages and other > strings > --- > > Key: MESOS-5057 > URL: https://issues.apache.org/jira/browse/MESOS-5057 > Project: Mesos > Issue Type: Task >Reporter: zhou xing >Assignee: zhou xing > Fix For: 0.29.0 > > Original Estimate: 1m > Remaining Estimate: 1m > > This is a sub ticket of MESOS-3780. In this ticket, we will update all the > slave to agent in the error messages and other strings in the code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5055) Slave/Agent Rename Phase I - Update strings in the log message and standard output
[ https://issues.apache.org/jira/browse/MESOS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhou xing updated MESOS-5055: - Summary: Slave/Agent Rename Phase I - Update strings in the log message and standard output (was: Replace Master/Slave Terminology Phase I - Update strings in the log message and standard output) > Slave/Agent Rename Phase I - Update strings in the log message and standard > output > -- > > Key: MESOS-5055 > URL: https://issues.apache.org/jira/browse/MESOS-5055 > Project: Mesos > Issue Type: Task >Reporter: zhou xing >Assignee: zhou xing > Fix For: 0.29.0 > > > This is a sub ticket of MESOS-3780. In this ticket, we will rename all the > slave to agent in the log messages and standard output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4760) Expose metrics and gauges for fetcher cache usage and hit rate
[
https://issues.apache.org/jira/browse/MESOS-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259267#comment-15259267
]
Michael Browning commented on MESOS-4760:
-
Diff (note, this is a sketch, not intended for merging) of what the changes
would look like:
https://reviews.apache.org/r/46717/
Most of these depend pretty heavily on unification with {{uri::Fetcher}}, since
a lot of the relevant information is only accessible to the {{mesos-fetcher}}
binary, which is the only entity that knows whether the URI is being fetched
from the cache or not. To that end, I think they'll have to wait for further
progress on the work that [~kaysoky] is doing, after which I can proceed with
making the Fetcher an injected property in the Slave process, which will allow
it to expose methods for the new metrics added in {{slave/metrics.cpp}}.
> Expose metrics and gauges for fetcher cache usage and hit rate
> --
>
> Key: MESOS-4760
> URL: https://issues.apache.org/jira/browse/MESOS-4760
> Project: Mesos
> Issue Type: Improvement
> Components: fetcher, statistics
>Reporter: Michael Browning
>Assignee: Michael Browning
>Priority: Minor
> Labels: features, fetcher, statistics, uber
>
> To evaluate the fetcher cache and calibrate the value of the
> fetcher_cache_size flag, it would be useful to have metrics and gauges on
> agents that expose operational statistics like cache hit rate, occupied cache
> size, and time spent downloading resources that were not present.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5278) Add a CLI allowing a user to enter a container.
[
https://issues.apache.org/jira/browse/MESOS-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259250#comment-15259250
]
Ian Downes commented on MESOS-5278:
---
[~xujyan] yeah :-) it's got some code specific to Aurora's Thermos executor
where it verifies the calling uid has access permission on the sandbox
directory to implement crude access control when run under setuid root. It's
only a small part though which could be generalized if people agreed with the
broader approach.
[~vinodkone] I just tried various mesos subcommands and they seem to be broken
on at least 0.26.x and 0.27.x...?
{code}
$ mesos ps
File "/usr/local/bin/mesos-ps", line 194
with ThreadingExecutor() as executor:
^
SyntaxError: invalid syntax
{code}
> Add a CLI allowing a user to enter a container.
> ---
>
> Key: MESOS-5278
> URL: https://issues.apache.org/jira/browse/MESOS-5278
> Project: Mesos
> Issue Type: Improvement
>Reporter: Jie Yu
>
> Containers created by the unified containerizer (Mesos containerizer) uses
> various namespaces (e.g., mount, network, etc.).
> To improve debugability, we should create a CLI that allows an operator or a
> user to enter the namespaces associated with the container, and execute an
> arbitrary command in that container (similar to `docker exec`).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-3241) Update FrameworkInfo.user on framework reregistration
[ https://issues.apache.org/jira/browse/MESOS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb updated MESOS-3241: --- Comment: was deleted (was: This ticket seems to be a duplicate of https://issues.apache.org/jira/browse/MESOS-3240. Can it be closed? ) > Update FrameworkInfo.user on framework reregistration > - > > Key: MESOS-3241 > URL: https://issues.apache.org/jira/browse/MESOS-3241 > Project: Mesos > Issue Type: Improvement >Reporter: Aditi Dixit >Assignee: Aditi Dixit > > Part 1 - Add user to master's state and update user in all slaves that have > the registered framework. > Part 2 - Add test and also user to slave's internal state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3241) Update FrameworkInfo.user on framework reregistration
[ https://issues.apache.org/jira/browse/MESOS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259026#comment-15259026 ] Stephan Erb commented on MESOS-3241: This ticket seems to be a duplicate of https://issues.apache.org/jira/browse/MESOS-3240. Can it be closed? > Update FrameworkInfo.user on framework reregistration > - > > Key: MESOS-3241 > URL: https://issues.apache.org/jira/browse/MESOS-3241 > Project: Mesos > Issue Type: Improvement >Reporter: Aditi Dixit >Assignee: Aditi Dixit > > Part 1 - Add user to master's state and update user in all slaves that have > the registered framework. > Part 2 - Add test and also user to slave's internal state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4135) Labels are not return in statusUpdate TaskStatus
[ https://issues.apache.org/jira/browse/MESOS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258983#comment-15258983 ] Srinivas commented on MESOS-4135: - Requesting Shepherd, I would like to work on it. > Labels are not return in statusUpdate TaskStatus > > > Key: MESOS-4135 > URL: https://issues.apache.org/jira/browse/MESOS-4135 > Project: Mesos > Issue Type: Bug > Components: framework, master >Affects Versions: 0.25.0 >Reporter: Felix Hupfeld >Assignee: Srinivas >Priority: Minor > > Labels that were set in the task's TaskInfo upon creation are not returned in > statusUpdate TaskStatus messages. > This restricts their usefulness. Use case would be maintaining the container > version of a running task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5263) pivot_root is not available on ARM
[
https://issues.apache.org/jira/browse/MESOS-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-5263:
---
Shepherd: Benjamin Mahler
> pivot_root is not available on ARM
> --
>
> Key: MESOS-5263
> URL: https://issues.apache.org/jira/browse/MESOS-5263
> Project: Mesos
> Issue Type: Bug
>Reporter: Tomasz Janiszewski
>Assignee: Tomasz Janiszewski
> Fix For: 0.29.0
>
>
> When compile on ARM, it will through error.
> The current code logic in src/linux/fs.cpp is:
> {code}
> #ifdef __NR_pivot_root
> int ret = ::syscall(__NR_pivot_root, newRoot.c_str(), putOld.c_str());
> #elif __x86_64__
> // A workaround for systems that have an old glib but have a new
> // kernel. The magic number '155' is the syscall number for
> // 'pivot_root' on the x86_64 architecture, see
> // arch/x86/syscalls/syscall_64.tbl
> int ret = ::syscall(155, newRoot.c_str(), putOld.c_str());
> #elif __powerpc__ || __ppc__ || __powerpc64__ || __ppc64__
> // A workaround for powerpc. The magic number '203' is the syscall
> // number for 'pivot_root' on the powerpc architecture, see
> // https://w3challs.com/syscalls/?arch=powerpc_64
> int ret = ::syscall(203, newRoot.c_str(), putOld.c_str());
> #else
> #error "pivot_root is not available"
> #endif
> {code}
> Possible sollution is to add `unistd.h` header
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3777) Replace Master/Slave Terminology Phase I - Modify public interfaces
[ https://issues.apache.org/jira/browse/MESOS-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-3777: -- Assignee: (was: Diana Arroyo) Description: [~darroyo] unassigning you since you no longer seems active on this project. This will let someone else pick it up. > Replace Master/Slave Terminology Phase I - Modify public interfaces > > > Key: MESOS-3777 > URL: https://issues.apache.org/jira/browse/MESOS-3777 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo > > [~darroyo] unassigning you since you no longer seems active on this project. > This will let someone else pick it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3784) Replace Master/Slave Terminology Phase I - Update mesos-cli
[ https://issues.apache.org/jira/browse/MESOS-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-3784: -- Assignee: (was: Diana Arroyo) Description: [~darroyo] unassigning you since you no longer seems active on this project. This will let someone else pick it up. > Replace Master/Slave Terminology Phase I - Update mesos-cli > > > Key: MESOS-3784 > URL: https://issues.apache.org/jira/browse/MESOS-3784 > Project: Mesos > Issue Type: Task >Reporter: Diana Arroyo > > [~darroyo] unassigning you since you no longer seems active on this project. > This will let someone else pick it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5288) Update leveldb patch file to suport s390x
Bing Li created MESOS-5288: -- Summary: Update leveldb patch file to suport s390x Key: MESOS-5288 URL: https://issues.apache.org/jira/browse/MESOS-5288 Project: Mesos Issue Type: Bug Reporter: Bing Li Assignee: Bing Li There're 2 issues in leveldb-1.4. 1. Leveldb didn't build. Have to define MemoryBarrier() for s390x. I got the patch form https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644336 . 2. A number of unit tests failed due to 1.4 doesn't detect endianness properly. And s390x is big-endian. Got error messages like "Failed to recover the log: Corruption: checksum mismatch". I have a backport patch which is part of the leveldb commit https://github.com/google/leveldb/commit/075a35a6d390167b77b687e067dd0ba593e7f624 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4887) Design doc for Slave/Agent rename
[ https://issues.apache.org/jira/browse/MESOS-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258670#comment-15258670 ] Vinod Kone commented on MESOS-4887: --- [~darroyo] can you resolve this ticket please? > Design doc for Slave/Agent rename > - > > Key: MESOS-4887 > URL: https://issues.apache.org/jira/browse/MESOS-4887 > Project: Mesos > Issue Type: Task >Reporter: Vinod Kone >Assignee: Diana Arroyo > > Design doc: > https://docs.google.com/document/d/1P8_4wdk29I6NoVTjbFkRl05-tfxV9PY4WLoRNvExupM/edit#heading=h.9g7fqjh6652v -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1478) Slave to Agent rename
[ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-1478: -- Summary: Slave to Agent rename (was: Replace Master/Slave terminology) > Slave to Agent rename > - > > Key: MESOS-1478 > URL: https://issues.apache.org/jira/browse/MESOS-1478 > Project: Mesos > Issue Type: Epic >Reporter: Clark Breyman >Assignee: Benjamin Hindman >Priority: Minor > Labels: mesosphere > > Inspired by the comments on this PR: > https://github.com/django/django/pull/2692 > TL;DR - Computers sharing work should be a good thing. Using the language of > human bondage and suffering is inappropriate in this context. It also has the > potential to alienate users and community members. > Working document: > https://docs.google.com/document/d/1P8_4wdk29I6NoVTjbFkRl05-tfxV9PY4WLoRNvExupM/edit#heading=h.9g7fqjh6652v -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1478) Slave to Agent rename.
[ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-1478: -- Summary: Slave to Agent rename. (was: Slave to Agent rename) > Slave to Agent rename. > -- > > Key: MESOS-1478 > URL: https://issues.apache.org/jira/browse/MESOS-1478 > Project: Mesos > Issue Type: Epic >Reporter: Clark Breyman >Assignee: Benjamin Hindman >Priority: Minor > Labels: mesosphere > > Inspired by the comments on this PR: > https://github.com/django/django/pull/2692 > TL;DR - Computers sharing work should be a good thing. Using the language of > human bondage and suffering is inappropriate in this context. It also has the > potential to alienate users and community members. > Working document: > https://docs.google.com/document/d/1P8_4wdk29I6NoVTjbFkRl05-tfxV9PY4WLoRNvExupM/edit#heading=h.9g7fqjh6652v -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1739) Allow slave reconfiguration on restart
[ https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258458#comment-15258458 ] Vinod Kone commented on MESOS-1739: --- Not just tasks, but reservations/volumes/outstanding-offers. > Allow slave reconfiguration on restart > -- > > Key: MESOS-1739 > URL: https://issues.apache.org/jira/browse/MESOS-1739 > Project: Mesos > Issue Type: Epic >Reporter: Patrick Reilly > Labels: external-volumes, mesosphere, myriad > > Make it so that either via a slave restart or a out of process "reconfigure" > ping, the attributes and resources of a slave can be updated to be a superset > of what they used to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5287) boto is no longer a Mesos dependency.
[ https://issues.apache.org/jira/browse/MESOS-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5287: Labels: easyfix newbie (was: ) > boto is no longer a Mesos dependency. > - > > Key: MESOS-5287 > URL: https://issues.apache.org/jira/browse/MESOS-5287 > Project: Mesos > Issue Type: Bug >Reporter: Yan Xu > Labels: easyfix, newbie > > Since 'mesos-ec2' has been removed from the repo in MESOS-2640. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1802) HealthCheckTest.HealthStatusChange is flaky on jenkins.
[
https://issues.apache.org/jira/browse/MESOS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258435#comment-15258435
]
haosdent commented on MESOS-1802:
-
I prefer to drop the http status check in the test cases, because I still don't
have any clues to guarantee the http queries order match the statusUpdate
order. [~neilc] [~bmahler] [~tnachen] Do you think this proposal is doable?
> HealthCheckTest.HealthStatusChange is flaky on jenkins.
> ---
>
> Key: MESOS-1802
> URL: https://issues.apache.org/jira/browse/MESOS-1802
> Project: Mesos
> Issue Type: Bug
> Components: test, tests
>Affects Versions: 0.26.0
>Reporter: Benjamin Mahler
>Assignee: haosdent
> Labels: flaky, health-check, mesosphere
> Attachments: health_check_flaky_test_log.txt
>
>
> https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-Out-Of-Src-Disable-Java-Disable-Python-Disable-Webui/2374/consoleFull
> {noformat}
> [ RUN ] HealthCheckTest.HealthStatusChange
> Using temporary directory '/tmp/HealthCheckTest_HealthStatusChange_IYnlu2'
> I0916 22:56:14.034612 21026 leveldb.cpp:176] Opened db in 2.155713ms
> I0916 22:56:14.034965 21026 leveldb.cpp:183] Compacted db in 332489ns
> I0916 22:56:14.034984 21026 leveldb.cpp:198] Created db iterator in 3710ns
> I0916 22:56:14.034996 21026 leveldb.cpp:204] Seeked to beginning of db in
> 642ns
> I0916 22:56:14.035006 21026 leveldb.cpp:273] Iterated through 0 keys in the
> db in 343ns
> I0916 22:56:14.035023 21026 replica.cpp:741] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0916 22:56:14.035200 21054 recover.cpp:425] Starting replica recovery
> I0916 22:56:14.035403 21041 recover.cpp:451] Replica is in EMPTY status
> I0916 22:56:14.035888 21045 replica.cpp:638] Replica in EMPTY status received
> a broadcasted recover request
> I0916 22:56:14.035969 21052 recover.cpp:188] Received a recover response from
> a replica in EMPTY status
> I0916 22:56:14.036118 21042 recover.cpp:542] Updating replica status to
> STARTING
> I0916 22:56:14.036603 21046 master.cpp:286] Master
> 20140916-225614-3125920579-47865-21026 (penates.apache.org) started on
> 67.195.81.186:47865
> I0916 22:56:14.036634 21046 master.cpp:332] Master only allowing
> authenticated frameworks to register
> I0916 22:56:14.036648 21046 master.cpp:337] Master only allowing
> authenticated slaves to register
> I0916 22:56:14.036659 21046 credentials.hpp:36] Loading credentials for
> authentication from
> '/tmp/HealthCheckTest_HealthStatusChange_IYnlu2/credentials'
> I0916 22:56:14.036686 21045 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 480322ns
> I0916 22:56:14.036700 21045 replica.cpp:320] Persisted replica status to
> STARTING
> I0916 22:56:14.036769 21046 master.cpp:366] Authorization enabled
> I0916 22:56:14.036826 21045 recover.cpp:451] Replica is in STARTING status
> I0916 22:56:14.036944 21052 master.cpp:120] No whitelist given. Advertising
> offers for all slaves
> I0916 22:56:14.036968 21049 hierarchical_allocator_process.hpp:299]
> Initializing hierarchical allocator process with master :
> master@67.195.81.186:47865
> I0916 22:56:14.037284 21054 replica.cpp:638] Replica in STARTING status
> received a broadcasted recover request
> I0916 22:56:14.037312 21046 master.cpp:1212] The newly elected leader is
> master@67.195.81.186:47865 with id 20140916-225614-3125920579-47865-21026
> I0916 22:56:14.037333 21046 master.cpp:1225] Elected as the leading master!
> I0916 22:56:14.037345 21046 master.cpp:1043] Recovering from registrar
> I0916 22:56:14.037504 21040 registrar.cpp:313] Recovering registrar
> I0916 22:56:14.037505 21053 recover.cpp:188] Received a recover response from
> a replica in STARTING status
> I0916 22:56:14.037681 21047 recover.cpp:542] Updating replica status to VOTING
> I0916 22:56:14.038072 21052 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 330251ns
> I0916 22:56:14.038087 21052 replica.cpp:320] Persisted replica status to
> VOTING
> I0916 22:56:14.038127 21053 recover.cpp:556] Successfully joined the Paxos
> group
> I0916 22:56:14.038202 21053 recover.cpp:440] Recover process terminated
> I0916 22:56:14.038364 21048 log.cpp:656] Attempting to start the writer
> I0916 22:56:14.038812 21053 replica.cpp:474] Replica received implicit
> promise request with proposal 1
> I0916 22:56:14.038925 21053 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 92623ns
> I0916 22:56:14.038944 21053 replica.cpp:342] Persisted promised to 1
> I0916 22:56:14.039201 21052 coordinator.cpp:230] Coordinator attemping to
> fill missing position
> I0916 22:56:14.039676 21047 replica.cpp:375] Replica received explicit
> promise request for position 0 with proposal 2
> I0916 22:56:14.039836 21047
[jira] [Commented] (MESOS-5287) boto is no longer a Mesos dependency.
[ https://issues.apache.org/jira/browse/MESOS-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258421#comment-15258421 ] Yan Xu commented on MESOS-5287: --- Yes this is a simple task. > boto is no longer a Mesos dependency. > - > > Key: MESOS-5287 > URL: https://issues.apache.org/jira/browse/MESOS-5287 > Project: Mesos > Issue Type: Bug >Reporter: Yan Xu > > Since 'mesos-ec2' has been removed from the repo in MESOS-2640. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5287) boto is no longer a Mesos dependency.
[ https://issues.apache.org/jira/browse/MESOS-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258411#comment-15258411 ] haosdent commented on MESOS-5287: - We could remove this and update document safely, right? I saw mesos [homebrew file | https://github.com/Homebrew/homebrew-core/blob/master/Formula/mesos.rb] contains this dependency as well. > boto is no longer a Mesos dependency. > - > > Key: MESOS-5287 > URL: https://issues.apache.org/jira/browse/MESOS-5287 > Project: Mesos > Issue Type: Bug >Reporter: Yan Xu > > Since 'mesos-ec2' has been removed from the repo in MESOS-2640. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5287) boto is no longer a Mesos dependency.
Yan Xu created MESOS-5287: - Summary: boto is no longer a Mesos dependency. Key: MESOS-5287 URL: https://issues.apache.org/jira/browse/MESOS-5287 Project: Mesos Issue Type: Bug Reporter: Yan Xu Since 'mesos-ec2' has been removed from the repo in MESOS-2640. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5286) Add authorization to libprocess HTTP endpoints
Greg Mann created MESOS-5286: Summary: Add authorization to libprocess HTTP endpoints Key: MESOS-5286 URL: https://issues.apache.org/jira/browse/MESOS-5286 Project: Mesos Issue Type: Improvement Components: libprocess Reporter: Greg Mann Fix For: 0.29.0 Now that the libprocess-level HTTP endpoints have had authentication added to them in MESOS-4902, we can add authorization to them as well. As a first step, we can implement a "coarse-grained" approach, in which a principal is granted or denied access to a given endpoint. We will likely need to register an authorizer with libprocess. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5242) pivot_root is not available on System z (s390x)
[ https://issues.apache.org/jira/browse/MESOS-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258144#comment-15258144 ] Bing Li commented on MESOS-5242: Hi haosdent, I had a look at MESOS-5263. And yes, the definition of syscall pivot_root won't be needed when we have "+#include " . I'll keep an eye on 5263. Once the 5263 fix is approved, I'll try it out and close this issue. Thanks, > pivot_root is not available on System z (s390x) > --- > > Key: MESOS-5242 > URL: https://issues.apache.org/jira/browse/MESOS-5242 > Project: Mesos > Issue Type: Bug > Environment: Hardward: IBM System z > OS: Linux on z SLES12SP1 >Reporter: Bing Li >Assignee: Bing Li > > Got error "pivot_root is not available" which is similar to MESOS-5121 . > Added syscall pivot_root definition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-5285) Allow agent to periodically collect dynamic attributes
Qian Zhang created MESOS-5285:
-
Summary: Allow agent to periodically collect dynamic attributes
Key: MESOS-5285
URL: https://issues.apache.org/jira/browse/MESOS-5285
Project: Mesos
Issue Type: Improvement
Components: slave
Reporter: Qian Zhang
Assignee: Qian Zhang
The user story is, framework may want to schedule its tasks based on some
dynamically changed attributes (e.g., CPU utilization) of agent. For example,
framework receives 3 offers and each offer is corresponding to an agent, and
each agent's CPU utilization is different, framework may want to launch a task
on the agent with lowest CPU utilization.
Currently, agent will send its resources and attributes to master only on
startup, and will not update it afterward. To support the above user story, we
may need to introduce a new mechanism to agent for periodically update its
dynamically changed attributes to master. There is already a hook in agent:
{{Hook::slaveAttributesDecorator()}}, but this hook will only be called on
agent startup, we may need to enhance it to make it called periodically, or
introduce a new periodical hook mechanism. And we may also need to introduce a
new message between agent and master such agent can send the latest attributes
collected by the hook to master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3235) FetcherCacheHttpTest.HttpCachedSerialized and FetcherCacheHttpTest.HttpCachedConcurrent are flaky
[
https://issues.apache.org/jira/browse/MESOS-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257751#comment-15257751
]
Bernd Mathiske commented on MESOS-3235:
---
So far I could not reproduce the behavior. Also, a few weeks ago I still saw
this test failing on several occasions, but lately it has been stable with no
failures.
Looking at the log, it seems that all tasks got executed normally. The only
thing that looks a bit strange is that TASK_KILLED is mentioned after
TASK_FINISHED. I'll look into that, but on the backburner.
> FetcherCacheHttpTest.HttpCachedSerialized and
> FetcherCacheHttpTest.HttpCachedConcurrent are flaky
> -
>
> Key: MESOS-3235
> URL: https://issues.apache.org/jira/browse/MESOS-3235
> Project: Mesos
> Issue Type: Bug
> Components: fetcher, tests
>Affects Versions: 0.23.0
>Reporter: Joseph Wu
>Assignee: Bernd Mathiske
> Labels: mesosphere
> Fix For: 0.27.0
>
> Attachments: fetchercache_log_centos_6.txt
>
>
> On OSX, {{make clean && make -j8 V=0 check}}:
> {code}
> [--] 3 tests from FetcherCacheHttpTest
> [ RUN ] FetcherCacheHttpTest.HttpCachedSerialized
> HTTP/1.1 200 OK
> Date: Fri, 07 Aug 2015 17:23:05 GMT
> Content-Length: 30
> I0807 10:23:05.673596 2085372672 exec.cpp:133] Version: 0.24.0
> E0807 10:23:05.675884 184373248 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> I0807 10:23:05.675897 182226944 exec.cpp:207] Executor registered on slave
> 20150807-102305-139395082-52338-52313-S0
> E0807 10:23:05.683980 184373248 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> Registered executor on 10.0.79.8
> Starting task 0
> Forked command at 54363
> sh -c './mesos-fetcher-test-cmd 0'
> E0807 10:23:05.694953 184373248 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> Command exited with status 0 (pid: 54363)
> E0807 10:23:05.793927 184373248 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> I0807 10:23:06.590008 2085372672 exec.cpp:133] Version: 0.24.0
> E0807 10:23:06.592244 355938304 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> I0807 10:23:06.592243 353255424 exec.cpp:207] Executor registered on slave
> 20150807-102305-139395082-52338-52313-S0
> E0807 10:23:06.597995 355938304 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> Registered executor on 10.0.79.8
> Starting task 1
> Forked command at 54411
> sh -c './mesos-fetcher-test-cmd 1'
> E0807 10:23:06.608708 355938304 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> Command exited with status 0 (pid: 54411)
> E0807 10:23:06.707649 355938304 socket.hpp:173] Shutdown failed on fd=18:
> Socket is not connected [57]
> ../../src/tests/fetcher_cache_tests.cpp:860: Failure
> Failed to wait 15secs for awaitFinished(task.get())
> *** Aborted at 1438968214 (unix time) try "date -d @1438968214" if you are
> using GNU date ***
> [ FAILED ] FetcherCacheHttpTest.HttpCachedSerialized (28685 ms)
> [ RUN ] FetcherCacheHttpTest.HttpCachedConcurrent
> PC: @0x113723618 process::Owned<>::get()
> *** SIGSEGV (@0x0) received by PID 52313 (TID 0x118d59000) stack trace: ***
> @ 0x7fff8fcacf1a _sigtramp
> @ 0x7f9bc3109710 (unknown)
> @0x1136f07e2 mesos::internal::slave::Fetcher::fetch()
> @0x113862f9d
> mesos::internal::slave::MesosContainerizerProcess::fetch()
> @0x1138f1b5d
> _ZZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERKNS2_11ContainerIDERKNS2_11CommandInfoERKNSt3__112basic_stringIcNSC_11char_traitsIcEENSC_9allocatorIcRK6OptionISI_ERKNS2_7SlaveIDES6_S9_SI_SM_SP_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSW_FSU_T1_T2_T3_T4_T5_ET6_T7_T8_T9_T10_ENKUlPNS_11ProcessBaseEE_clES1D_
> @0x1138f18cf
> _ZNSt3__110__function6__funcIZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERKNS5_11ContainerIDERKNS5_11CommandInfoERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcRK6OptionISK_ERKNS5_7SlaveIDES9_SC_SK_SO_SR_EENS2_6FutureIT_EERKNS2_3PIDIT0_EEMSY_FSW_T1_T2_T3_T4_T5_ET6_T7_T8_T9_T10_EUlPNS2_11ProcessBaseEE_NSI_IS1G_EEFvS1F_EEclEOS1F_
> @0x1143768cf std::__1::function<>::operator()()
> @0x11435ca7f process::ProcessBase::visit()
> @0x1143ed6fe process::DispatchEvent::visit()
> @0x11271 process::ProcessBase::serve()
> @0x114343b4e process::ProcessManager::resume()
> @0x1143431ca process::internal::schedule()
> @0x1143da646 _ZNSt3__114__thread_proxyINS_5tupleIJPFvvEEPvS5_
> @ 0x7fff95090268 _pthread_body
> @
[jira] [Updated] (MESOS-4843) Authorize Master Operator Endpoints
[ https://issues.apache.org/jira/browse/MESOS-4843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-4843: -- Labels: authorization mesosphere security (was: mesosphere security) > Authorize Master Operator Endpoints > --- > > Key: MESOS-4843 > URL: https://issues.apache.org/jira/browse/MESOS-4843 > Project: Mesos > Issue Type: Epic > Components: master, security >Reporter: Adam B >Assignee: Joerg Schad > Labels: authorization, mesosphere, security > > In a secure, multi-tenant cluster, the operator doesn't want to give every > user access to read or modify cluster state/config, nor to perform > administrative actions. As such, we need to make sure that all such endpoints > are authenticated and authorized. > We've already added authorization to some operator endpoints (/teardown, > /reserve, etc.), but many remain unsecured. > - /roles, /observe, /registrar, /state-summary > - /maintenance, /machine, > - /logging, /profiler, /metrics, /flags, /system/stats.json > - Leave open? /redirect, /health, /version > See http://mesos.apache.org/documentation/latest/endpoints/ for a more > complete list. Some endpoints (e.g. state.json) will need a finer-grained > authz. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[
https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257686#comment-15257686
]
AndyPang commented on MESOS-5268:
-
I find in mesos cgroup assigin operation are write "cgroup.procs" file ,while
in SLES 11 sp2 sp3 kernel 3.0 have no "cgroup.procs" character,it
reimplantation from community SUSE version kernel 3.2. I have test when write
TGID into cgroup.procs it will not auto write multithread into "tasks".
If I modify both write into "tasks" it will take effect
{code:title=cgroup assigin|borderStyle=solid}
Try assign(const string& hierarchy, const string& cgroup, pid_t pid)
{
return cgroups::write(hierarchy, cgroup, "cgroup.procs", stringify(pid));
}
{code}
> Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
> -
>
> Key: MESOS-5268
> URL: https://issues.apache.org/jira/browse/MESOS-5268
> Project: Mesos
> Issue Type: Bug
> Components: isolation
>Affects Versions: 0.27.0
> Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22
> UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: cgroups
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator
> don't take effect. Two framework cpushare proportion is 1:3, we find at last
> in mesos container cpu.shares value is right, but when we use "top" to see
> result, the cpu usage is not 1:3. Our Application is multithread and can
> fulfil the cpu quota when single run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[ https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-5268: Labels: cgroups (was: patch) > Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3 > - > > Key: MESOS-5268 > URL: https://issues.apache.org/jira/browse/MESOS-5268 > Project: Mesos > Issue Type: Bug > Components: isolation >Affects Versions: 0.27.0 > Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22 > UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux >Reporter: AndyPang >Assignee: AndyPang > Labels: cgroups > Original Estimate: 48h > Remaining Estimate: 48h > > meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator > don't take effect. Two framework cpushare proportion is 1:3, we find at last > in mesos container cpu.shares value is right, but when we use "top" to see > result, the cpu usage is not 1:3. Our Application is multithread and can > fulfil the cpu quota when single run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[
https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
AndyPang updated MESOS-5268:
Comment: was deleted
(was: I find in mesos cgroup assigin operation
{code:title=cgroup assigin |borderStyle=solid}
Try assign(const string& hierarchy, const string& cgroup, pid_t pid)
{
return cgroups::write(hierarchy, cgroup, "cgroup.procs", stringify(pid));
}
{code})
> Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
> -
>
> Key: MESOS-5268
> URL: https://issues.apache.org/jira/browse/MESOS-5268
> Project: Mesos
> Issue Type: Bug
> Components: isolation
>Affects Versions: 0.27.0
> Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22
> UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: patch
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator
> don't take effect. Two framework cpushare proportion is 1:3, we find at last
> in mesos container cpu.shares value is right, but when we use "top" to see
> result, the cpu usage is not 1:3. Our Application is multithread and can
> fulfil the cpu quota when single run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5268) Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
[
https://issues.apache.org/jira/browse/MESOS-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257679#comment-15257679
]
AndyPang commented on MESOS-5268:
-
I find in mesos cgroup assigin operation
{code:title=cgroup assigin |borderStyle=solid}
Try assign(const string& hierarchy, const string& cgroup, pid_t pid)
{
return cgroups::write(hierarchy, cgroup, "cgroup.procs", stringify(pid));
}
{code}
> Cgroups CpushareIsolator don't take effect on SLES 11 SP2 SP3
> -
>
> Key: MESOS-5268
> URL: https://issues.apache.org/jira/browse/MESOS-5268
> Project: Mesos
> Issue Type: Bug
> Components: isolation
>Affects Versions: 0.27.0
> Environment: suse 3.0.101-0.47.71-default #1 SMP Thu Nov 12 12:22:22
> UTC 2015 (b5b212e) x86_64 x86_64 x86_64 GNU/Linux
>Reporter: AndyPang
>Assignee: AndyPang
> Labels: patch
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> meson run in SLES 11 sp2 sp3, kernel version 3.0.13/3.076, cpushareisolator
> don't take effect. Two framework cpushare proportion is 1:3, we find at last
> in mesos container cpu.shares value is right, but when we use "top" to see
> result, the cpu usage is not 1:3. Our Application is multithread and can
> fulfil the cpu quota when single run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-1739) Allow slave reconfiguration on restart
[ https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257669#comment-15257669 ] Adam B commented on MESOS-1739: --- > send the event to all the frameworks which have tasks on the agent? Yes, that's what we'd have to do. > Allow slave reconfiguration on restart > -- > > Key: MESOS-1739 > URL: https://issues.apache.org/jira/browse/MESOS-1739 > Project: Mesos > Issue Type: Epic >Reporter: Patrick Reilly > Labels: external-volumes, mesosphere, myriad > > Make it so that either via a slave restart or a out of process "reconfigure" > ping, the attributes and resources of a slave can be updated to be a superset > of what they used to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1739) Allow slave reconfiguration on restart
[ https://issues.apache.org/jira/browse/MESOS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257662#comment-15257662 ] Qian Zhang commented on MESOS-1739: --- But how can we know which frameworks we should send the event to? I think we do not know which tasks are impacted by the agent attribute change since there is no dependent attribute in TaskInfo. Or we just simply send the event to all the frameworks which have tasks on the agent? > Allow slave reconfiguration on restart > -- > > Key: MESOS-1739 > URL: https://issues.apache.org/jira/browse/MESOS-1739 > Project: Mesos > Issue Type: Epic >Reporter: Patrick Reilly > Labels: external-volumes, mesosphere, myriad > > Make it so that either via a slave restart or a out of process "reconfigure" > ping, the attributes and resources of a slave can be updated to be a superset > of what they used to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1806) Substituting etcd for Zookeeper
[ https://issues.apache.org/jira/browse/MESOS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257657#comment-15257657 ] Jay Guo commented on MESOS-1806: We should also update Mesos documentation to reflect modulerization. http://mesos.apache.org/documentation/latest/high-availability/ Contender/Detector is still tightly coupled with Zookeeper according to the doc. > Substituting etcd for Zookeeper > --- > > Key: MESOS-1806 > URL: https://issues.apache.org/jira/browse/MESOS-1806 > Project: Mesos > Issue Type: Task > Components: leader election >Reporter: Ed Ropple >Assignee: Shuai Lin >Priority: Minor > >eropple: Could you also file a new JIRA for Mesos to drop ZK > in favor of etcd or ReplicatedLog? Would love to get some momentum going on > that one. > -- > Consider it filed. =) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
