[jira] [Assigned] (MESOS-3841) Master HTTP API support to get the leader

[Jian Qiu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jian Qiu reassigned MESOS-3841:
---

Assignee: Jian Qiu

> Master HTTP API support to get the leader
> -
>
> Key: MESOS-3841
> URL: https://issues.apache.org/jira/browse/MESOS-3841
> Project: Mesos
>  Issue Type: Improvement
>  Components: HTTP API
>Reporter: Cosmin Lehene
>Assignee: Jian Qiu
>
> There's currently no good way to query the current master ensemble leader.
> Some workarounds to get the leader (and parse it from leader@ip) from 
> {{/state.json}} or to grep it from  {{master/redirect}}. 
> The scheduler API does an HTTP redirect, but that requires an HTTP  POST 
> coming from a framework as well
> {{POST /api/v1/scheduler  HTTP/1.1}}
> There should be a lightweight API call to get the current master. 
> This could be part of a more granular representation (REST) of the current 
> state.json.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3086) Create cgroups TasksKiller for non freeze subsystems.

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske updated MESOS-3086:
--
Sprint: Mesosphere Sprint 15, Mesosphere Sprint 16, Mesosphere Sprint 17, 
Mesosphere Sprint 18, Mesosphere Sprint 19, Mesosphere Sprint 20, Mesosphere 
Sprint 21, Mesosphere Sprint 22  (was: Mesosphere Sprint 15, Mesosphere Sprint 
16, Mesosphere Sprint 17, Mesosphere Sprint 18, Mesosphere Sprint 19, 
Mesosphere Sprint 20, Mesosphere Sprint 21, Mesosphere Sprint 22, Mesosphere 
Sprint 23)

> Create cgroups TasksKiller for non freeze subsystems.
> -
>
> Key: MESOS-3086
> URL: https://issues.apache.org/jira/browse/MESOS-3086
> Project: Mesos
>  Issue Type: Bug
>Reporter: Joerg Schad
>Assignee: Joerg Schad
>  Labels: mesosphere
>
> We have a number of test issues when we cannot remove cgroups (in case there 
> are still related tasks running) in cases where the freezer subsystem is not 
> available. 
> In the current code 
> (https://github.com/apache/mesos/blob/0.22.1/src/linux/cgroups.cpp#L1728)  we 
> will fallback to a very simple mechnism of recursivly trying to remove the 
> cgroups which fails if there are still tasks running. 
> Therefore we need an additional  (NonFreeze)TasksKiller which doesn't  rely 
> on the freezer subsystem.
> This problem caused issues when running 'sudo make check' during 0.23 release 
> testing, where BenH provided already a better error message with 
> b1a23d6a52c31b8c5c840ab01902dbe00cb1feef / https://reviews.apache.org/r/36604.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4069) libevent_ssl_socket assertion fails

[Jojy Varghese (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jojy Varghese updated MESOS-4069:
-
  Sprint: Mesosphere Sprint 23
Story Points: 3
  Labels: mesosphere  (was: )

> libevent_ssl_socket assertion fails 
> 
>
> Key: MESOS-4069
> URL: https://issues.apache.org/jira/browse/MESOS-4069
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
> Environment: ubuntu 14.04
>Reporter: Jojy Varghese
>Assignee: Jojy Varghese
>  Labels: mesosphere
>
> Have been seeing the following socket  receive error frequently:
> {code}
> F1204 11:12:47.301839 54104 libevent_ssl_socket.cpp:245] Check failed: length 
> > 0 
> *** Check failure stack trace: ***
> @ 0x7f73227fe5a6  google::LogMessage::Fail()
> @ 0x7f73227fe4f2  google::LogMessage::SendToLog()
> @ 0x7f73227fdef4  google::LogMessage::Flush()
> @ 0x7f7322800e08  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f73227b93e2  
> process::network::LibeventSSLSocketImpl::recv_callback()
> @ 0x7f73227b9182  
> process::network::LibeventSSLSocketImpl::recv_callback()
> @ 0x7f731cbc75cc  bufferevent_run_deferred_callbacks_locked
> @ 0x7f731cbbdc5d  event_base_loop
> @ 0x7f73227d9ded  process::EventLoop::run()
> @ 0x7f73227a3101  
> _ZNSt12_Bind_simpleIFPFvvEvEE9_M_invokeIJEEEvSt12_Index_tupleIJXspT_EEE
> @ 0x7f73227a305b  std::_Bind_simple<>::operator()()
> @ 0x7f73227a2ff4  std::thread::_Impl<>::_M_run()
> @ 0x7f731e0d1a40  (unknown)
> @ 0x7f731de0a182  start_thread
> @ 0x7f731db3730d  (unknown)
> @  (nil)  (unknown)
> {code}
> In this case this was a HTTP get over SSL. The url being:
> https://dseasb33srnrn.cloudfront.net:443/registry-v2/docker/registry/v2/blobs/sha256/44/44be94a95984bb47dc3a193f59bf8c04d5e877160b745b119278f38753a6f58f/data?Expires=1449259252=Q4CQdr1LbxsiYyVebmetrx~lqDgQfHVkGxpbMM3PoISn6r07DXIzBX6~tl1iZx9uXdfr~5awH8Kxwh-y8b0dTV3mLTZAVlneZlHbhBAX9qbYMd180-QvUvrFezwOlSmX4B3idvo-zK0CarUu3Ev1hbJz5y3olwe2ZC~RXHEwzkQ_=APKAJECH5M7VWIS5YZ6Q
> *Steps to reproduce:*
> 1. Run master
> 2. Run slave from your build directory as  as:
> {code}
>  
> GLOG_v=1;SSL_ENABLED=1;SSL_KEY_FILE=;SSL_CERT_FILE=;sudo
>  -E ./bin/mesos-slave.sh \
>   --master=127.0.0.1:5050 \   
>
>   --executor_registration_timeout=5mins \ 
>
>   --containerizers=mesos  \   
>
>   --isolation=filesystem/linux \  
>
>   --image_providers=DOCKER  \ 
>
>   --docker_puller_timeout=600 \   
>
>   --launcher_dir=$MESOS_BUILD_DIR/src/.libs \ 
>
>   --switch_user="false" \ 
>
>   --docker_puller="registry"  
> {code} 
> 3. Run mesos-execute from your build directory as :
> {code}
> ./src/mesos-execute \ 
>
> --master=127.0.0.1:5050 \ 
>
> --command="uname -a"  \   
>
> --name=test \ 
>
> --docker_image=ubuntu 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4076) Create simple LoadQoSController which will evict revocable executors when system load is too high.

[Bartek Plotka (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bartek Plotka updated MESOS-4076:
-
Description: 
It would be nice to have simple QoS Controller module  out-of-box in _Mesos_ 
(Similar to the _FixedResourceEstimator_).
 As a result we will:
 - enable simple QoS assurance and encourage users to use oversubscription 
modules.
-  present example QoS module for new developers.

The idea is to implement _LoadQoSController_ which will monitor system load and 
evict all revocable executors when the load is above configured threshold.
In implementation, it will support two configurable thresholds: system load 
average 5min and 15min. System load 1 min will be ignored, since it could be 
misleading signal when temporary fluctuations appears.

We could also add description to the oversubscription.md doc.

  was:
It would be nice to have simple QoS Controller module  out-of-box in 
_Mesos_(Similar to the _FixedResourceEstimator_). The idea is to implement 
_LoadQoSController_ which will monitor system load and evict all revocable 
executors when the load is above configured threshold.

In implementation, it will support two configurable thresholds: system load 
average 5min and 15min. System load 1 min will be ignored, since it could be 
misleading signal when temporary fluctuations appears.

We could also add description to the oversubscription.md doc,


> Create simple LoadQoSController which will evict revocable executors when 
> system load is too high.
> --
>
> Key: MESOS-4076
> URL: https://issues.apache.org/jira/browse/MESOS-4076
> Project: Mesos
>  Issue Type: Task
>Reporter: Bartek Plotka
>Assignee: Bartek Plotka
>  Labels: Intel
>
> It would be nice to have simple QoS Controller module  out-of-box in _Mesos_ 
> (Similar to the _FixedResourceEstimator_).
>  As a result we will:
>  - enable simple QoS assurance and encourage users to use oversubscription 
> modules.
> -  present example QoS module for new developers.
> The idea is to implement _LoadQoSController_ which will monitor system load 
> and evict all revocable executors when the load is above configured threshold.
> In implementation, it will support two configurable thresholds: system load 
> average 5min and 15min. System load 1 min will be ignored, since it could be 
> misleading signal when temporary fluctuations appears.
> We could also add description to the oversubscription.md doc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-4076) Create simple LoadQoSController which will evict revocable executors when system load is too high.

[Bartek Plotka (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045082#comment-15045082
 ] 

Bartek Plotka commented on MESOS-4076:
--

https://reviews.apache.org/r/40617/

> Create simple LoadQoSController which will evict revocable executors when 
> system load is too high.
> --
>
> Key: MESOS-4076
> URL: https://issues.apache.org/jira/browse/MESOS-4076
> Project: Mesos
>  Issue Type: Task
>Reporter: Bartek Plotka
>Assignee: Bartek Plotka
>  Labels: Intel
>
> It would be nice to have simple QoS Controller module  out-of-box in 
> _Mesos_(Similar to the _FixedResourceEstimator_). The idea is to implement 
> _LoadQoSController_ which will monitor system load and evict all revocable 
> executors when the load is above configured threshold.
> In implementation, it will support two configurable thresholds: system load 
> average 5min and 15min. System load 1 min will be ignored, since it could be 
> misleading signal when temporary fluctuations appears.
> We could also add description to the oversubscription.md doc,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4076) Create simple LoadQoSController which will evict revocable executors when system load is too high.

[Bartek Plotka (JIRA)]

Bartek Plotka created MESOS-4076:


 Summary: Create simple LoadQoSController which will evict 
revocable executors when system load is too high.
 Key: MESOS-4076
 URL: https://issues.apache.org/jira/browse/MESOS-4076
 Project: Mesos
  Issue Type: Task
Reporter: Bartek Plotka
Assignee: Bartek Plotka


It would be nice to have simple QoS Controller module  out-of-box in 
_Mesos_(Similar to the _FixedResourceEstimator_). The idea is to implement 
_LoadQoSController_ which will monitor system load and evict all revocable 
executors when the load is above configured threshold.

In implementation, it will support two configurable thresholds: system load 
average 5min and 15min. System load 1 min will be ignored, since it could be 
misleading signal when temporary fluctuations appears.

We could also add description to the oversubscription.md doc,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4075) Continue test suite execution across crashing tests.

[Bernd Mathiske (JIRA)]

Bernd Mathiske created MESOS-4075:
-

 Summary: Continue test suite execution across crashing tests.
 Key: MESOS-4075
 URL: https://issues.apache.org/jira/browse/MESOS-4075
 Project: Mesos
  Issue Type: Improvement
  Components: test
Affects Versions: 0.26.0
Reporter: Bernd Mathiske


Currently, mesos-tests.sh exits when a test crashes. This is inconvenient when 
trying to find out all tests that fail. 

mesos-tests.sh should rate a test that crashes as failed and continue the same 
way as if the test merely returned with a failure result and exited properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3960) Standardize quota endpoints

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-3960:
---
Shepherd: Joris Van Remoortere

> Standardize quota endpoints
> ---
>
> Key: MESOS-3960
> URL: https://issues.apache.org/jira/browse/MESOS-3960
> Project: Mesos
>  Issue Type: Improvement
>  Components: master
>Reporter: Alexander Rukletsov
>Assignee: Alexander Rukletsov
>  Labels: http, mesosphere
>
> To be consistent with other operator endpoints, require a single JSON object 
> in the request as opposed to key-value pairs encoded in a string.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4077) Prototype quota removal authorization

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4077:
---

 Summary: Prototype quota removal authorization
 Key: MESOS-4077
 URL: https://issues.apache.org/jira/browse/MESOS-4077
 Project: Mesos
  Issue Type: Task
  Components: master
Reporter: Jan Schlicht
Assignee: Jan Schlicht
Priority: Critical


For the quota remove endpoint authorization has to be implemented, similar to 
the quota set endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4078) Prototype tests for quota authentication and authorization

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4078:
---

 Summary: Prototype tests for quota authentication and authorization
 Key: MESOS-4078
 URL: https://issues.apache.org/jira/browse/MESOS-4078
 Project: Mesos
  Issue Type: Task
  Components: master, test
Reporter: Jan Schlicht
Assignee: Jan Schlicht
Priority: Critical






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4080) Clean up HTTP authentication in quota endpoints

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4080:

Description: The authentification of quota requests introduces some 
technical dept that will be resolved by the refactored HTTP based 
authentification. This ticket tracks the work related to cleaning up the quota 
handling to use the new HTTP authen

> Clean up HTTP authentication in quota endpoints
> ---
>
> Key: MESOS-4080
> URL: https://issues.apache.org/jira/browse/MESOS-4080
> Project: Mesos
>  Issue Type: Task
>  Components: HTTP API, master
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Critical
>  Labels: mesosphere, quota, tech-debt
>
> The authentification of quota requests introduces some technical dept that 
> will be resolved by the refactored HTTP based authentification. This ticket 
> tracks the work related to cleaning up the quota handling to use the new HTTP 
> authen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4080) Clean up HTTP authentification in quota endpoints

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4080:

Labels: mesosphere quota tech-debt  (was: mesosphere quota)

> Clean up HTTP authentification in quota endpoints
> -
>
> Key: MESOS-4080
> URL: https://issues.apache.org/jira/browse/MESOS-4080
> Project: Mesos
>  Issue Type: Task
>  Components: HTTP API, master
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Critical
>  Labels: mesosphere, quota, tech-debt
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-4071) Master crash during framework teardown ( Check failed: total.resources.contains(slaveId))

[James Peach (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045218#comment-15045218
 ] 

James Peach commented on MESOS-4071:


I made the following change and successfully ran for the whole weekend without 
seeing this crash.

{code}
diff --git a/src/common/resources.cpp b/src/common/resources.cpp
index 601388c..8e07cc6 100644
--- a/src/common/resources.cpp
+++ b/src/common/resources.cpp
@@ -499,7 +499,7 @@ Option Resources::validate(
 bool Resources::isEmpty(const Resource& resource)
 {
   if (resource.type() == Value::SCALAR) {
-return resource.scalar().value() == 0;
+return resource.scalar().value() < 0.0001;
   } else if (resource.type() == Value::RANGES) {
 return resource.ranges().range_size() == 0;
   } else if (resource.type() == Value::SET) {
{code}

> Master crash during framework teardown ( Check failed: 
> total.resources.contains(slaveId))
> -
>
> Key: MESOS-4071
> URL: https://issues.apache.org/jira/browse/MESOS-4071
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.25.0
>Reporter: Mandeep Chadha
>
> Stack Trace :
> NOTE : Replaced IP address with XX.XX.XX.XX 
> {code}
> I1204 10:31:03.391127 2588810 master.cpp:5564] Processing TEARDOWN call for 
> framework 61ce62d1-7418-4ae1-aa78-a8ebf75ad502-0014 
> (mloop-coprocesses-183c4999-9ce9-47b2-bc96-a865c672fcbb (TEST) at 
> scheduler-c8ab2103-cf36-40d8-8a2d-a6b69a8fc...@xx.xx.xx.xx:35237
> I1204 10:31:03.391177 2588810 master.cpp:5576] Removing framework 
> 61ce62d1-7418-4ae1-aa78-a8ebf75ad502-0014 
> (mloop-coprocesses-183c4999-9ce9-47b2-bc96-a865c672fcbb (TEST)) at 
> schedulerc8ab2103-cf36-40d8-8a2d-a6b69a8fc...@xx.xx.xx.xx:35237
> I1204 10:31:03.391337 2588805 hierarchical.hpp:605] Deactivated framework 
> 61ce62d1-7418-4ae1-aa78-a8ebf75ad502-0014
> F1204 10:31:03.395500 2588810 sorter.cpp:233] Check failed: 
> total.resources.contains(slaveId)
> *** Check failure stack trace: ***
> @ 0x7f2b3dda53d8  google::LogMessage::Fail()
> @ 0x7f2b3dda5327  google::LogMessage::SendToLog()
> @ 0x7f2b3dda4d38  google::LogMessage::Flush()
> @ 0x7f2b3dda7a6c  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f2b3d3351a1  
> mesos::internal::master::allocator::DRFSorter::remove()
> @ 0x7f2b3d0b8c29  
> mesos::internal::master::allocator::HierarchicalAllocatorProcess<>::removeFramework()
> @ 0x7f2b3d0ca823 
> _ZZN7process8dispatchIN5mesos8internal6master9allocator21MesosAllocatorProcessERKNS1_11FrameworkIDES6_EEvRKNS_3PIDIT_EEMSA_FvT0_ET1_ENKUlPNS_11ProcessBaseEE_clESJ_
> @ 0x7f2b3d0dc8dc  
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchIN5mesos8internal6master9allocator21MesosAllocatorProcessERKNS5_11FrameworkIDESA_EEvRKNS0_3PIDIT_EEMSE_FvT0_ET1_EUlS2_E_E9_M_invokeERKSt9_Any_dataS2
> _
> @ 0x7f2b3dd2cc35  std::function<>::operator()()
> @ 0x7f2b3dd15ae5  process::ProcessBase::visit()
> @ 0x7f2b3dd188e2  process::DispatchEvent::visit()
> @   0x472366  process::ProcessBase::serve()
> @ 0x7f2b3dd1203f  process::ProcessManager::resume()
> @ 0x7f2b3dd061b2  process::internal::schedule()
> @ 0x7f2b3dd63efd  
> _ZNSt12_Bind_simpleIFPFvvEvEE9_M_invokeIJEEEvSt12_Inde
> x_tupleIJXspT_EEE
> @ 0x7f2b3dd63e4d  std::_Bind_simple<>::operator()()
> @ 0x7f2b3dd63de6  std::thread::_Impl<>::_M_run()
> @   0x318c2b6470  (unknown)
> @   0x318b2079d1  (unknown)
> @   0x318aae8b5d  (unknown)
> @  (nil)  (unknown)
> Aborted (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4072) The lt-mesos-master will coredump in some situation.

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-4072:
---
Labels: mesosphere newbie  (was: )

> The lt-mesos-master will coredump in some situation.
> 
>
> Key: MESOS-4072
> URL: https://issues.apache.org/jira/browse/MESOS-4072
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.25.0
>Reporter: Nan Xiao
>  Labels: mesosphere, newbie
>
>  I find  lt-mesos-master  will coredump when following conditions are met:  
> (1) The user doesn't have write permission of /var/lib/mesos directory:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/
> total 176
> dr-xr-xr-x 2 rootroot4096 Dec  7 03:08 mesos
> ..
> (2) the /var/lib/mesos is an empty folder:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/mesos/
> total 0
> Executing following command will core dump:
> nan@ubuntu:~/mesos-0.25.0/build$ ./bin/mesos-master.sh --ip=16.187.250.141 
> --work_dir=/var/lib/mesos
> I1207 03:18:36.431015 22951 main.cpp:229] Build: 2015-12-07 00:11:18 by nan
> I1207 03:18:36.431154 22951 main.cpp:231] Version: 0.25.0
> I1207 03:18:36.431388 22951 main.cpp:252] Using 'HierarchicalDRF' allocator
> F1207 03:18:36.431807 22951 replica.cpp:724] CHECK_SOME(state): IO error: 
> /var/lib/mesos/replicated_log/LOCK: No such file or directory Failed to 
> recover the log
> *** Check failure stack trace: ***
> @ 0x7f076bc208ca  google::LogMessage::Fail()
> @ 0x7f076bc20816  google::LogMessage::SendToLog()
> @ 0x7f076bc20218  google::LogMessage::Flush()
> @ 0x7f076bc2312c  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f076adf8f30  _CheckFatal::~_CheckFatal()
> @ 0x7f076baa4939  mesos::internal::log::ReplicaProcess::restore()
> @ 0x7f076baa0f8c  
> mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0x7f076baa4c95  mesos::internal::log::Replica::Replica()
> @ 0x7f076b9cf819  mesos::internal::log::LogProcess::LogProcess()
> @ 0x7f076b9d576c  mesos::internal::log::Log::Log()
> @   0x46d21f  main
> @ 0x7f0766f69ec5  (unknown)
> @   0x46b979  (unknown)
> Aborted (core dumped)
> Use gdb to analyze it:
> nan@ubuntu:~/mesos-0.25.0/build$ gdb 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master core
> GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master...done.
> [New LWP 22065]
> [New LWP 22087]
> [New LWP 22085]
> [New LWP 22089]
> [New LWP 22084]
> [New LWP 22086]
> [New LWP 22091]
> [New LWP 22088]
> [New LWP 22092]
> [New LWP 22090]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master 
> --ip=127.0.0.1 --work_di'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> Traceback (most recent call last):
>   File 
> "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py",
>  line 63, in 
> from libstdcxx.v6.printers import register_libstdcxx_printers
> ImportError: No module named 'libstdcxx'
> (gdb) bt
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x7fe9178140d8 in __GI_abort () at abort.c:89
> #2  0x7fe91c4b8c1b in DumpStackTraceAndExit () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #3  0x7fe91c4b28ca in google::LogMessage::Fail () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #4  0x7fe91c4b2816 in google::LogMessage::SendToLog () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #5  0x7fe91c4b2218 in google::LogMessage::Flush () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #6  0x7fe91c4b512c in 

[jira] [Updated] (MESOS-4080) Clean up HTTP authentication in quota endpoints

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4080:

Description: The authentification of quota requests introduces some 
technical dept that will be resolved by the refactored HTTP based 
authentification. This ticket tracks the work related to cleaning up the quota 
handling to use the new HTTP API.  (was: The authentification of quota requests 
introduces some technical dept that will be resolved by the refactored HTTP 
based authentification. This ticket tracks the work related to cleaning up the 
quota handling to use the new HTTP authen)

> Clean up HTTP authentication in quota endpoints
> ---
>
> Key: MESOS-4080
> URL: https://issues.apache.org/jira/browse/MESOS-4080
> Project: Mesos
>  Issue Type: Task
>  Components: HTTP API, master
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Critical
>  Labels: mesosphere, quota, tech-debt
>
> The authentification of quota requests introduces some technical dept that 
> will be resolved by the refactored HTTP based authentification. This ticket 
> tracks the work related to cleaning up the quota handling to use the new HTTP 
> API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4072) The lt-mesos-master will coredump in some situation.

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-4072:
---
Component/s: master

> The lt-mesos-master will coredump in some situation.
> 
>
> Key: MESOS-4072
> URL: https://issues.apache.org/jira/browse/MESOS-4072
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.25.0
>Reporter: Nan Xiao
>  Labels: mesosphere, newbie
>
>  I find  lt-mesos-master  will coredump when following conditions are met:  
> (1) The user doesn't have write permission of /var/lib/mesos directory:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/
> total 176
> dr-xr-xr-x 2 rootroot4096 Dec  7 03:08 mesos
> ..
> (2) the /var/lib/mesos is an empty folder:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/mesos/
> total 0
> Executing following command will core dump:
> nan@ubuntu:~/mesos-0.25.0/build$ ./bin/mesos-master.sh --ip=16.187.250.141 
> --work_dir=/var/lib/mesos
> I1207 03:18:36.431015 22951 main.cpp:229] Build: 2015-12-07 00:11:18 by nan
> I1207 03:18:36.431154 22951 main.cpp:231] Version: 0.25.0
> I1207 03:18:36.431388 22951 main.cpp:252] Using 'HierarchicalDRF' allocator
> F1207 03:18:36.431807 22951 replica.cpp:724] CHECK_SOME(state): IO error: 
> /var/lib/mesos/replicated_log/LOCK: No such file or directory Failed to 
> recover the log
> *** Check failure stack trace: ***
> @ 0x7f076bc208ca  google::LogMessage::Fail()
> @ 0x7f076bc20816  google::LogMessage::SendToLog()
> @ 0x7f076bc20218  google::LogMessage::Flush()
> @ 0x7f076bc2312c  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f076adf8f30  _CheckFatal::~_CheckFatal()
> @ 0x7f076baa4939  mesos::internal::log::ReplicaProcess::restore()
> @ 0x7f076baa0f8c  
> mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0x7f076baa4c95  mesos::internal::log::Replica::Replica()
> @ 0x7f076b9cf819  mesos::internal::log::LogProcess::LogProcess()
> @ 0x7f076b9d576c  mesos::internal::log::Log::Log()
> @   0x46d21f  main
> @ 0x7f0766f69ec5  (unknown)
> @   0x46b979  (unknown)
> Aborted (core dumped)
> Use gdb to analyze it:
> nan@ubuntu:~/mesos-0.25.0/build$ gdb 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master core
> GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master...done.
> [New LWP 22065]
> [New LWP 22087]
> [New LWP 22085]
> [New LWP 22089]
> [New LWP 22084]
> [New LWP 22086]
> [New LWP 22091]
> [New LWP 22088]
> [New LWP 22092]
> [New LWP 22090]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master 
> --ip=127.0.0.1 --work_di'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> Traceback (most recent call last):
>   File 
> "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py",
>  line 63, in 
> from libstdcxx.v6.printers import register_libstdcxx_printers
> ImportError: No module named 'libstdcxx'
> (gdb) bt
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x7fe9178140d8 in __GI_abort () at abort.c:89
> #2  0x7fe91c4b8c1b in DumpStackTraceAndExit () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #3  0x7fe91c4b28ca in google::LogMessage::Fail () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #4  0x7fe91c4b2816 in google::LogMessage::SendToLog () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #5  0x7fe91c4b2218 in google::LogMessage::Flush () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #6  0x7fe91c4b512c in 

[jira] [Commented] (MESOS-3997) Switch to fixed-point for resources

[James Peach (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045227#comment-15045227
 ] 

James Peach commented on MESOS-3997:


I believe that MESOS-4071 is another manifestation of this problem. In that 
issue, we subtract the CPU resource from both the roles' allocation and the 
slave total resources. One of the subtractions goes to zero and the other goes 
to an extremely small fraction (3.3389957465601583e-14) of a CPU.

> Switch to fixed-point for resources
> ---
>
> Key: MESOS-3997
> URL: https://issues.apache.org/jira/browse/MESOS-3997
> Project: Mesos
>  Issue Type: Improvement
>  Components: allocation, master
>Reporter: Neil Conway
>  Labels: mesosphere, resources
>
> Using floating point for resources is problematic, because roundoff and 
> precision errors when doing resource math can produce unexpected results.
> Instead, we should probably adopt a fixed-point representation: e.g., CPU 
> resources will be measured as an integer number of fractional CPUs (e.g., 25 
> deci-CPUs == 2.5 CPUs).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4080) Clean up HTTP authentification in quota endpoints

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4080:
---

 Summary: Clean up HTTP authentification in quota endpoints
 Key: MESOS-4080
 URL: https://issues.apache.org/jira/browse/MESOS-4080
 Project: Mesos
  Issue Type: Task
  Components: HTTP API, master
Reporter: Jan Schlicht
Assignee: Jan Schlicht
Priority: Critical






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4082) Add Tests for quota authentification and authorization

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4082:
---

 Summary: Add Tests for quota authentification and authorization
 Key: MESOS-4082
 URL: https://issues.apache.org/jira/browse/MESOS-4082
 Project: Mesos
  Issue Type: Task
  Components: master, test
Reporter: Jan Schlicht
Assignee: Jan Schlicht






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4083) Add tests for quota removal

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4083:
---

 Summary: Add tests for quota removal
 Key: MESOS-4083
 URL: https://issues.apache.org/jira/browse/MESOS-4083
 Project: Mesos
  Issue Type: Task
  Components: master, test
Reporter: Jan Schlicht
Assignee: Jan Schlicht






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3992) Change Doubles to Ints in the protobufs

[James Peach (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045225#comment-15045225
 ] 

James Peach commented on MESOS-3992:


This should probably be marked a duplicate of MESOS-3997.

> Change Doubles to Ints in the protobufs
> ---
>
> Key: MESOS-3992
> URL: https://issues.apache.org/jira/browse/MESOS-3992
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Gabriel Hartmann
>
> There are a number of problems  (see list below) associated with doubles 
> being used for representing Resource values.  Move to integers.  The only 
> resource that may need non-whole numbers is the CPU resource anyway.  Make it 
> denominated in 1/100ths of a CPU and be done with it.
> https://issues.apache.org/jira/browse/MESOS-3990
> https://issues.apache.org/jira/browse/MESOS-3552



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4081) Authorize quota removal

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4081:
---

 Summary: Authorize quota removal
 Key: MESOS-4081
 URL: https://issues.apache.org/jira/browse/MESOS-4081
 Project: Mesos
  Issue Type: Task
  Components: master
Reporter: Jan Schlicht
Assignee: Jan Schlicht






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4079) Prototype tests for quota removal authorization

[Jan Schlicht (JIRA)]

Jan Schlicht created MESOS-4079:
---

 Summary: Prototype tests for quota removal authorization
 Key: MESOS-4079
 URL: https://issues.apache.org/jira/browse/MESOS-4079
 Project: Mesos
  Issue Type: Task
  Components: master, test
Reporter: Jan Schlicht
Assignee: Jan Schlicht
Priority: Critical






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4073) Expose recovery parameters from Hierarchical allocator

[Alexander Rukletsov (JIRA)]

Alexander Rukletsov created MESOS-4073:
--

 Summary: Expose recovery parameters from Hierarchical allocator
 Key: MESOS-4073
 URL: https://issues.apache.org/jira/browse/MESOS-4073
 Project: Mesos
  Issue Type: Improvement
  Components: allocation
Reporter: Alexander Rukletsov
Assignee: Alexander Rukletsov


While implementing recovery in the hierarchical allocator, we introduced some 
internal constants that influence the recovery process: 
{{ALLOCATION_HOLD_OFF_RECOVERY_TIMEOUT}} and {{AGENT_RECOVERY_FACTOR}}. We 
should expose these parameters for operators to configure.

However, I am a bit reluctant to expose them as master flags, because they are 
implementation specific. It would be nice to combine all hierarchical 
allocator-related flags into one (maybe JSON) file, similar to how we do it for 
modules.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4074) Tests for master failover in presence of quota

[Alexander Rukletsov (JIRA)]

Alexander Rukletsov created MESOS-4074:
--

 Summary: Tests for master failover in presence of quota
 Key: MESOS-4074
 URL: https://issues.apache.org/jira/browse/MESOS-4074
 Project: Mesos
  Issue Type: Task
  Components: master, test
Reporter: Alexander Rukletsov
Assignee: Alexander Rukletsov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MESOS-3942) Enhance endpoint /roles for adding a new role

[Yong Qiao Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044617#comment-15044617
 ] 

Yong Qiao Wang edited comment on MESOS-3942 at 12/7/15 9:13 AM:


After discussion with Adam B, and we will support both Dynamic Roles and 
Implicit Roles, and new role will be implicitly created when framework register 
in Implicit Roles ticket, so mark this JIRA as invalid.


was (Author: jamesyongqiaowang):
New role will be implicitly created when framework register in Implicit Roles 
ticket, so mark this JIRA as invalid.

> Enhance endpoint /roles for adding a new role
> -
>
> Key: MESOS-3942
> URL: https://issues.apache.org/jira/browse/MESOS-3942
> Project: Mesos
>  Issue Type: Task
>Reporter: Yong Qiao Wang
>Assignee: Yong Qiao Wang
>
> In this ticket, we will enhance the existing HTTP endpoint /roles to can add 
> a new role at runtime as outlined in the Design Doc: 
> https://docs.google.com/document/d/1OIgceqpsjV3-_LGF83IMAFnrh1Ea3Zc16w9kWWPpUj4/edit#



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3208) Fetch checksum files to inform fetcher cache use

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske updated MESOS-3208:
--
Assignee: (was: Bernd Mathiske)

> Fetch checksum files to inform fetcher cache use
> 
>
> Key: MESOS-3208
> URL: https://issues.apache.org/jira/browse/MESOS-3208
> Project: Mesos
>  Issue Type: Improvement
>  Components: fetcher
>Reporter: Bernd Mathiske
>Priority: Minor
>
> This is the first part of phase 1 as described in the comments for 
> MESOS-2073. We add a field to CommandInfo::URI that contains the URI of a 
> checksum file. When this file has new content, then the contents of the 
> associated value URI needs to be refreshed in the fetcher cache. 
> In this implementation step, we just add the above basic functionality 
> (download, checksum comparison). In later steps, we will add more control 
> flow to cover corner cases and thus make this feature more useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-115) Include slave hostname in SlaveID

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske updated MESOS-115:
-
Assignee: (was: Bernd Mathiske)

> Include slave hostname in SlaveID
> -
>
> Key: MESOS-115
> URL: https://issues.apache.org/jira/browse/MESOS-115
> Project: Mesos
>  Issue Type: Improvement
>  Components: master
>Reporter: Bill Farner
>Priority: Minor
>
> There are some API calls that pass both SlaveID and hostname, and others that 
> provide only SlaveID.  This can make log forensics difficult from the 
> framework perspective.  It would be much nicer to compose the hostname 
> directly in the SlaveID proto.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2073) Fetcher cache file verification, updating and invalidation

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske updated MESOS-2073:
--
Assignee: (was: Bernd Mathiske)

> Fetcher cache file verification, updating and invalidation
> --
>
> Key: MESOS-2073
> URL: https://issues.apache.org/jira/browse/MESOS-2073
> Project: Mesos
>  Issue Type: Epic
>  Components: fetcher, slave
>Reporter: Bernd Mathiske
>Priority: Minor
>  Labels: mesosphere
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> The other tickets in the fetcher cache epic do not necessitate a check sum 
> (e.g. MD5, SHA*) for files cached by the fetcher. Whereas such a check sum 
> could be used to verify whether the file arrived without unintended 
> alterations, it can first and foremost be employed to detect and trigger 
> updates. 
> Scenario: If a UIR is requested for fetching and the indicated download has 
> the same check sum as the cached file, then the cache file will be used and 
> the download forgone. If the check sum is different, then fetching proceeds 
> and the cached file gets replaced. 
> This capability will be indicated by an additional field in the URI protobuf. 
> Details TBD, i.e. to be discussed in comments below.
> In addition to the above, even if the check sum is the same, we can support 
> voluntary cache file invalidation: a fresh download can be requested, or the 
> caching behavior can be revoked entirely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-2073) Fetcher cache file verification, updating and invalidation

[Bernd Mathiske (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044841#comment-15044841
 ] 

Bernd Mathiske commented on MESOS-2073:
---

Since there was no reply on the dev and user list as to how the fetcher cache 
is being used and what features would be best to extend its feature set, 
especially mtime-based cache entry invalidation, let's deprioritize this topic 
for now.

> Fetcher cache file verification, updating and invalidation
> --
>
> Key: MESOS-2073
> URL: https://issues.apache.org/jira/browse/MESOS-2073
> Project: Mesos
>  Issue Type: Epic
>  Components: fetcher, slave
>Reporter: Bernd Mathiske
>Priority: Minor
>  Labels: mesosphere
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> The other tickets in the fetcher cache epic do not necessitate a check sum 
> (e.g. MD5, SHA*) for files cached by the fetcher. Whereas such a check sum 
> could be used to verify whether the file arrived without unintended 
> alterations, it can first and foremost be employed to detect and trigger 
> updates. 
> Scenario: If a UIR is requested for fetching and the indicated download has 
> the same check sum as the cached file, then the cache file will be used and 
> the download forgone. If the check sum is different, then fetching proceeds 
> and the cached file gets replaced. 
> This capability will be indicated by an additional field in the URI protobuf. 
> Details TBD, i.e. to be discussed in comments below.
> In addition to the above, even if the check sum is the same, we can support 
> voluntary cache file invalidation: a fresh download can be requested, or the 
> caching behavior can be revoked entirely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-4072) The lt-mesos-master will coredump in some situation.

[Benjamin Bannier (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044831#comment-15044831
 ] 

Benjamin Bannier commented on MESOS-4072:
-

Note that this is an intentional hard exit: you specified a {{work_dir}} which 
is not writable, so there is no way we can continue after emitting an error 
message (which we did).

However, we do not need to show a stack trace or dump core here (i.e. replace 
the use of {{CHECK}} with something like {{EXIT}}).

> The lt-mesos-master will coredump in some situation.
> 
>
> Key: MESOS-4072
> URL: https://issues.apache.org/jira/browse/MESOS-4072
> Project: Mesos
>  Issue Type: Bug
>Affects Versions: 0.25.0
>Reporter: Nan Xiao
>
>  I find  lt-mesos-master  will coredump when following conditions are met:  
> (1) The user doesn't have write permission of /var/lib/mesos directory:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/
> total 176
> dr-xr-xr-x 2 rootroot4096 Dec  7 03:08 mesos
> ..
> (2) the /var/lib/mesos is an empty folder:
> nan@ubuntu:~/mesos-0.25.0/build$ ls -lt /var/lib/mesos/
> total 0
> Executing following command will core dump:
> nan@ubuntu:~/mesos-0.25.0/build$ ./bin/mesos-master.sh --ip=16.187.250.141 
> --work_dir=/var/lib/mesos
> I1207 03:18:36.431015 22951 main.cpp:229] Build: 2015-12-07 00:11:18 by nan
> I1207 03:18:36.431154 22951 main.cpp:231] Version: 0.25.0
> I1207 03:18:36.431388 22951 main.cpp:252] Using 'HierarchicalDRF' allocator
> F1207 03:18:36.431807 22951 replica.cpp:724] CHECK_SOME(state): IO error: 
> /var/lib/mesos/replicated_log/LOCK: No such file or directory Failed to 
> recover the log
> *** Check failure stack trace: ***
> @ 0x7f076bc208ca  google::LogMessage::Fail()
> @ 0x7f076bc20816  google::LogMessage::SendToLog()
> @ 0x7f076bc20218  google::LogMessage::Flush()
> @ 0x7f076bc2312c  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f076adf8f30  _CheckFatal::~_CheckFatal()
> @ 0x7f076baa4939  mesos::internal::log::ReplicaProcess::restore()
> @ 0x7f076baa0f8c  
> mesos::internal::log::ReplicaProcess::ReplicaProcess()
> @ 0x7f076baa4c95  mesos::internal::log::Replica::Replica()
> @ 0x7f076b9cf819  mesos::internal::log::LogProcess::LogProcess()
> @ 0x7f076b9d576c  mesos::internal::log::Log::Log()
> @   0x46d21f  main
> @ 0x7f0766f69ec5  (unknown)
> @   0x46b979  (unknown)
> Aborted (core dumped)
> Use gdb to analyze it:
> nan@ubuntu:~/mesos-0.25.0/build$ gdb 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master core
> GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from 
> /home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master...done.
> [New LWP 22065]
> [New LWP 22087]
> [New LWP 22085]
> [New LWP 22089]
> [New LWP 22084]
> [New LWP 22086]
> [New LWP 22091]
> [New LWP 22088]
> [New LWP 22092]
> [New LWP 22090]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/home/nan/mesos-0.25.0/build/src/.libs/lt-mesos-master 
> --ip=127.0.0.1 --work_di'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> Traceback (most recent call last):
>   File 
> "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py",
>  line 63, in 
> from libstdcxx.v6.printers import register_libstdcxx_printers
> ImportError: No module named 'libstdcxx'
> (gdb) bt
> #0  0x7fe917810cc9 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x7fe9178140d8 in __GI_abort () at abort.c:89
> #2  0x7fe91c4b8c1b in DumpStackTraceAndExit () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #3  0x7fe91c4b28ca in google::LogMessage::Fail () from 
> /home/nan/mesos-0.25.0/build/src/.libs/libmesos-0.25.0.so
> #4  0x7fe91c4b2816 in 

[jira] [Updated] (MESOS-3858) Draft quota limits design document

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske updated MESOS-3858:
--
Sprint: Mesosphere Sprint 22  (was: Mesosphere Sprint 22, Mesosphere Sprint 
23)

> Draft quota limits design document
> --
>
> Key: MESOS-3858
> URL: https://issues.apache.org/jira/browse/MESOS-3858
> Project: Mesos
>  Issue Type: Task
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere, quota
>
> In the design documents for Quota 
> (https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I/edit#)
>  the proposed MVP does not include quota limits. Quota limits represent an 
> upper bound of resources that a role is allowed to use. The task of this 
> ticket is to outline a design document on how to implement quota limits when 
> the quota MVP is implemented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-4071) Master crash during framework teardown ( Check failed: total.resources.contains(slaveId))

[Klaus Ma (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046193#comment-15046193
 ] 

Klaus Ma commented on MESOS-4071:
-

[~jvanremoortere]/[~jamespeach], should we add {{almostEquals}} into {{stout}} 
before MESOS-3997? Just as I mentioned in MESOS-1187. Any comments?

> Master crash during framework teardown ( Check failed: 
> total.resources.contains(slaveId))
> -
>
> Key: MESOS-4071
> URL: https://issues.apache.org/jira/browse/MESOS-4071
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.25.0
>Reporter: Mandeep Chadha
>
> Stack Trace :
> NOTE : Replaced IP address with XX.XX.XX.XX 
> {code}
> I1204 10:31:03.391127 2588810 master.cpp:5564] Processing TEARDOWN call for 
> framework 61ce62d1-7418-4ae1-aa78-a8ebf75ad502-0014 
> (mloop-coprocesses-183c4999-9ce9-47b2-bc96-a865c672fcbb (TEST) at 
> scheduler-c8ab2103-cf36-40d8-8a2d-a6b69a8fc...@xx.xx.xx.xx:35237
> I1204 10:31:03.391177 2588810 master.cpp:5576] Removing framework 
> 61ce62d1-7418-4ae1-aa78-a8ebf75ad502-0014 
> (mloop-coprocesses-183c4999-9ce9-47b2-bc96-a865c672fcbb (TEST)) at 
> schedulerc8ab2103-cf36-40d8-8a2d-a6b69a8fc...@xx.xx.xx.xx:35237
> I1204 10:31:03.391337 2588805 hierarchical.hpp:605] Deactivated framework 
> 61ce62d1-7418-4ae1-aa78-a8ebf75ad502-0014
> F1204 10:31:03.395500 2588810 sorter.cpp:233] Check failed: 
> total.resources.contains(slaveId)
> *** Check failure stack trace: ***
> @ 0x7f2b3dda53d8  google::LogMessage::Fail()
> @ 0x7f2b3dda5327  google::LogMessage::SendToLog()
> @ 0x7f2b3dda4d38  google::LogMessage::Flush()
> @ 0x7f2b3dda7a6c  google::LogMessageFatal::~LogMessageFatal()
> @ 0x7f2b3d3351a1  
> mesos::internal::master::allocator::DRFSorter::remove()
> @ 0x7f2b3d0b8c29  
> mesos::internal::master::allocator::HierarchicalAllocatorProcess<>::removeFramework()
> @ 0x7f2b3d0ca823 
> _ZZN7process8dispatchIN5mesos8internal6master9allocator21MesosAllocatorProcessERKNS1_11FrameworkIDES6_EEvRKNS_3PIDIT_EEMSA_FvT0_ET1_ENKUlPNS_11ProcessBaseEE_clESJ_
> @ 0x7f2b3d0dc8dc  
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchIN5mesos8internal6master9allocator21MesosAllocatorProcessERKNS5_11FrameworkIDESA_EEvRKNS0_3PIDIT_EEMSE_FvT0_ET1_EUlS2_E_E9_M_invokeERKSt9_Any_dataS2
> _
> @ 0x7f2b3dd2cc35  std::function<>::operator()()
> @ 0x7f2b3dd15ae5  process::ProcessBase::visit()
> @ 0x7f2b3dd188e2  process::DispatchEvent::visit()
> @   0x472366  process::ProcessBase::serve()
> @ 0x7f2b3dd1203f  process::ProcessManager::resume()
> @ 0x7f2b3dd061b2  process::internal::schedule()
> @ 0x7f2b3dd63efd  
> _ZNSt12_Bind_simpleIFPFvvEvEE9_M_invokeIJEEEvSt12_Inde
> x_tupleIJXspT_EEE
> @ 0x7f2b3dd63e4d  std::_Bind_simple<>::operator()()
> @ 0x7f2b3dd63de6  std::thread::_Impl<>::_M_run()
> @   0x318c2b6470  (unknown)
> @   0x318b2079d1  (unknown)
> @   0x318aae8b5d  (unknown)
> @  (nil)  (unknown)
> Aborted (core dumped)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4064) Add ContainerInfo to internal Task protobuf.

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4064:
-
Shepherd: Benjamin Mahler

> Add ContainerInfo to internal Task protobuf.
> 
>
> Key: MESOS-4064
> URL: https://issues.apache.org/jira/browse/MESOS-4064
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Artem Harutyunyan
>  Labels: mesosphere
>
> In what seems like an oversight, when ContainerInfo was added to TaskInfo, it 
> was not added to our internal Task protobuf.
> Also, unlike the agent, it appears that the master does not use 
> protobuf::createTask. We should try remove the manual construction in the 
> master in favor of construction through protobuf::createTask.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4015) Expose task / executor health in master & slave state.json

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4015:
-
Shepherd: Benjamin Mahler

> Expose task / executor health in master & slave state.json
> --
>
> Key: MESOS-4015
> URL: https://issues.apache.org/jira/browse/MESOS-4015
> Project: Mesos
>  Issue Type: Improvement
>Affects Versions: 0.25.0
>Reporter: Sargun Dhillon
>Assignee: Artem Harutyunyan
>Priority: Trivial
>  Labels: mesosphere
>
> Right now, if I specify a healthcheck for a task, the only way to get to it 
> is via the Task Status updates that come to the framework. Unfortunately, 
> this information isn't exposed in the state.json either in the slave or 
> master. It'd be ideal to have that information to enable tools like Mesos-DNS 
> to be health-aware.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3844) getting started documentation has flaws, corrections suggested (http://mesos.apache.org/gettingstarted/)

[Benjamin Hindman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Hindman updated MESOS-3844:

Shepherd: Benjamin Hindman

> getting started documentation has flaws, corrections suggested 
> (http://mesos.apache.org/gettingstarted/)
> 
>
> Key: MESOS-3844
> URL: https://issues.apache.org/jira/browse/MESOS-3844
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, project website, test
>Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 
> (x86_64) with Updates HVM (a t2.medium instance)
>Reporter: Manne Laukkanen
>Assignee: Kevin Klues
>Priority: Trivial
>  Labels: build, documentation, mesosphere
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Getting started documentation, while having great virtues, has room for 
> improvement:
> 1) Documentation is illogical and wrong for this part:
>  " $ wget http://www.apache.org/dist/mesos/0.25.0/mesos-0.25.0.tar.gz
>  $ tar -zxf mesos-0.25.0.tar.gz" ...then, later:
> "# Install a few utility tools
> $ sudo yum install -y tar wget
> ..obviously using tar and wget is not possible before installing them.
> 2) Although vi is fine for many, utility tools having:
> sudo yum install -y tar wget nano
> might make editing e.g. the WANDISCO -repo file way easier for newbies.
> 3) Advice to launch Mesos with localhost option ( " ./bin/mesos-master.sh 
> --ip=127.0.0.1 --work_dir=/var/lib/mesos " ) will lead into a state where 
> Mesos UI can not be reached in port :5050 in a production environment e.g. in 
> AWS EC2. Mentioning this would help, not hinder deployment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3842) getting started documentation following Mesos 0.25 build fails for CentOS7 (http://mesos.apache.org/gettingstarted/)

[Benjamin Hindman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Hindman updated MESOS-3842:

Shepherd: Benjamin Hindman

> getting started documentation following Mesos 0.25 build fails for CentOS7 
> (http://mesos.apache.org/gettingstarted/)
> 
>
> Key: MESOS-3842
> URL: https://issues.apache.org/jira/browse/MESOS-3842
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, project website
>Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 
> (x86_64) with Updates HVM (a t2.medium instance)
>Reporter: Manne Laukkanen
>Assignee: Kevin Klues
>  Labels: build, documentation, mesosphere
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> WANdisco SVN repo file usage leads to failure of build process with error, so 
> usage of it should be 1) discouraged 2) replaced with a working solution
> Proceeding according to documentation at 
> http://mesos.apache.org/gettingstarted/:
> # 'Mesos > 0.21.0' requires 'subversion > 1.8' devel package, which is
> # not available in the default repositories.
> # Add the WANdisco SVN repo file: '/etc/yum.repos.d/wandisco-svn.repo' with 
> content:
>   [WANdiscoSVN]
>   name=WANdisco SVN Repo 1.9
>   enabled=1
>   baseurl=http://opensource.wandisco.com/centos/7/svn-1.9/RPMS/$basearch/
>   gpgcheck=1
>   gpgkey=http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco
> ...we do as is described, then proceed to next step, which is 
> "# Install essential development tools."
> sudo yum groupinstall -y "Development Tools"
> ...the added WANDISCO -repo causes failed building process with error:
> Error: Package: subversion-1.9.2-1.x86_64 (WANdiscoSVN)
>Requires: libserf-1.so.0()(64bit)
>  - we end up with e.g. no build tools to proceed with, so process fails, 
> Mesos can not be built according to instructions (e.g. no C-compiler in 
> path...)
> Interestingly, building with aforementioned instructions (with some 
> modifications mentioned in ticket MESOS-3844) was successful without errors 
> justa a few days ago on 30 Oct 2015. WANDISCO repo breakage? 
> No changes to building machine image (the CentOS7 image) nor machine itself 
> (t2.medium EC2 instance) were made in between attempts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3954) The documentation should recommend an updated systemd for centos 7.

[Benjamin Hindman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Hindman updated MESOS-3954:

Shepherd: Benjamin Hindman

> The documentation should recommend an updated systemd for centos 7.
> ---
>
> Key: MESOS-3954
> URL: https://issues.apache.org/jira/browse/MESOS-3954
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Till Toenshoff
>Assignee: Kevin Klues
>Priority: Minor
>  Labels: documentation, mesosphere
>
> After installing a plain centos 7, some Mesos tests kept failing due to 
> MESOS-3352.
> We should try to minimize such experience for our users by e.g. adding the 
> need for an explicit systemd update on this distribution (and maybe others).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-4085) Implement implicit roles

[Yong Qiao Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046253#comment-15046253
 ] 

Yong Qiao Wang commented on MESOS-4085:
---

[~neilc], we also have a requirement to register a Mesos framework with any 
role, so this improvement is urgent and important for us. I find this feature 
can be released before Dec 21 based on the current plan, can we work together 
to speed up this release? After you create sub tasks for this improvement, can 
you assign some to me?

> Implement implicit roles
> 
>
> Key: MESOS-4085
> URL: https://issues.apache.org/jira/browse/MESOS-4085
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: mesosphere, roles
>
> See also design doc: MESOS-4000.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4067) ReservationTest.ACLMultipleOperations is flaky

[Greg Mann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann updated MESOS-4067:
-
Story Points: 2

> ReservationTest.ACLMultipleOperations is flaky
> --
>
> Key: MESOS-4067
> URL: https://issues.apache.org/jira/browse/MESOS-4067
> Project: Mesos
>  Issue Type: Bug
>Reporter: Michael Park
>Assignee: Greg Mann
>  Labels: flaky, mesosphere
>
> Observed from the CI: 
> https://builds.apache.org/job/Mesos/COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,OS=ubuntu%3A14.04,label_exp=docker%7C%7CHadoop/1319/changes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3032) Document containerizer launch

[Anand Mazumdar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anand Mazumdar updated MESOS-3032:
--
Shepherd: Jie Yu  (was: Timothy Chen)

> Document containerizer launch 
> --
>
> Key: MESOS-3032
> URL: https://issues.apache.org/jira/browse/MESOS-3032
> Project: Mesos
>  Issue Type: Documentation
>  Components: containerization
>Reporter: Jojy Varghese
>Assignee: Jojy Varghese
>Priority: Minor
>  Labels: docathon, documentation, mesosphere
>
> We currently dont have enough documentation for the containerizer component. 
> This task adds documentation for containerizer launch sequence.
> The mail goals are:
> - Have diagrams (state, sequence, class etc) depicting the containerizer 
> launch process.
> - Make the documentation newbie friendly.
> - Usable for future design discussions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4029) ContentType/SchedulerTest is flaky.

[Anand Mazumdar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anand Mazumdar updated MESOS-4029:
--
Sprint: Mesosphere Sprint 23  (was: Mesosphere Sprint 23, Mesosphere Sprint 
24)

> ContentType/SchedulerTest is flaky.
> ---
>
> Key: MESOS-4029
> URL: https://issues.apache.org/jira/browse/MESOS-4029
> Project: Mesos
>  Issue Type: Bug
>Affects Versions: 0.26.0
>Reporter: Till Toenshoff
>Assignee: Anand Mazumdar
>  Labels: flaky, flaky-test, mesosphere
>
> SSL build, [Ubuntu 
> 14.04|https://github.com/tillt/mesos-vagrant-ci/blob/master/ubuntu14/setup.sh],
>  non-root test run.
> {noformat}
> [--] 22 tests from ContentType/SchedulerTest
> [ RUN  ] ContentType/SchedulerTest.Subscribe/0
> [   OK ] ContentType/SchedulerTest.Subscribe/0 (48 ms)
> *** Aborted at 1448928007 (unix time) try "date -d @1448928007" if you are 
> using GNU date ***
> [ RUN  ] ContentType/SchedulerTest.Subscribe/1
> PC: @  0x1451b8e 
> testing::internal::UntypedFunctionMockerBase::UntypedInvokeWith()
> *** SIGSEGV (@0x10030) received by PID 21320 (TID 0x2b549e5d4700) from 
> PID 48; stack trace: ***
> @ 0x2b54c95940b7 os::Linux::chained_handler()
> @ 0x2b54c9598219 JVM_handle_linux_signal
> @ 0x2b5496300340 (unknown)
> @  0x1451b8e 
> testing::internal::UntypedFunctionMockerBase::UntypedInvokeWith()
> @   0xe2ea6d 
> _ZN7testing8internal18FunctionMockerBaseIFvRKSt5queueIN5mesos2v19scheduler5EventESt5dequeIS6_SaIS6_E10InvokeWithERKSt5tupleIJSC_EE
> @   0xe2b1bc testing::internal::FunctionMocker<>::Invoke()
> @  0x1118aed 
> mesos::internal::tests::SchedulerTest::Callbacks::received()
> @  0x111c453 
> _ZNKSt7_Mem_fnIMN5mesos8internal5tests13SchedulerTest9CallbacksEFvRKSt5queueINS0_2v19scheduler5EventESt5dequeIS8_SaIS8_EclIJSE_EvEEvRS4_DpOT_
> @  0x111c001 
> _ZNSt5_BindIFSt7_Mem_fnIMN5mesos8internal5tests13SchedulerTest9CallbacksEFvRKSt5queueINS1_2v19scheduler5EventESt5dequeIS9_SaIS9_ESt17reference_wrapperIS5_ESt12_PlaceholderILi16__callIvJSF_EJLm0ELm1T_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE
> @  0x111b90d 
> _ZNSt5_BindIFSt7_Mem_fnIMN5mesos8internal5tests13SchedulerTest9CallbacksEFvRKSt5queueINS1_2v19scheduler5EventESt5dequeIS9_SaIS9_ESt17reference_wrapperIS5_ESt12_PlaceholderILi1clIJSF_EvEET0_DpOT_
> @  0x111ae09 std::_Function_handler<>::_M_invoke()
> @ 0x2b5493c6da09 std::function<>::operator()()
> @ 0x2b5493c688ee process::AsyncExecutorProcess::execute<>()
> @ 0x2b5493c6db2a 
> _ZZN7process8dispatchI7NothingNS_20AsyncExecutorProcessERKSt8functionIFvRKSt5queueIN5mesos2v19scheduler5EventESt5dequeIS8_SaIS8_ESC_PvSG_SC_SJ_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSO_FSL_T1_T2_T3_ET4_T5_T6_ENKUlPNS_11ProcessBaseEE_clES11_
> @ 0x2b5493c765a4 
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchI7NothingNS0_20AsyncExecutorProcessERKSt8functionIFvRKSt5queueIN5mesos2v19scheduler5EventESt5dequeISC_SaISC_ESG_PvSK_SG_SN_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSS_FSP_T1_T2_T3_ET4_T5_T6_EUlS2_E_E9_M_invokeERKSt9_Any_dataS2_
> @ 0x2b54946b1201 std::function<>::operator()()
> @ 0x2b549469960f process::ProcessBase::visit()
> @ 0x2b549469d480 process::DispatchEvent::visit()
> @   0x9dc0ba process::ProcessBase::serve()
> @ 0x2b54946958cc process::ProcessManager::resume()
> @ 0x2b5494692a9c 
> _ZZN7process14ProcessManager12init_threadsEvENKUlRKSt11atomic_boolE_clES3_
> @ 0x2b549469ccac 
> _ZNSt5_BindIFZN7process14ProcessManager12init_threadsEvEUlRKSt11atomic_boolE_St17reference_wrapperIS3_EEE6__callIvIEILm0T_OSt5tupleIIDpT0_EESt12_Index_tupleIIXspT1_EEE
> @ 0x2b549469cc5c 
> _ZNSt5_BindIFZN7process14ProcessManager12init_threadsEvEUlRKSt11atomic_boolE_St17reference_wrapperIS3_EEEclIIEvEET0_DpOT_
> @ 0x2b549469cbee 
> _ZNSt12_Bind_simpleIFSt5_BindIFZN7process14ProcessManager12init_threadsEvEUlRKSt11atomic_boolE_St17reference_wrapperIS4_EEEvEE9_M_invokeIIEEEvSt12_Index_tupleIIXspT_EEE
> @ 0x2b549469cb45 
> _ZNSt12_Bind_simpleIFSt5_BindIFZN7process14ProcessManager12init_threadsEvEUlRKSt11atomic_boolE_St17reference_wrapperIS4_EEEvEEclEv
> @ 0x2b549469cade 
> _ZNSt6thread5_ImplISt12_Bind_simpleIFSt5_BindIFZN7process14ProcessManager12init_threadsEvEUlRKSt11atomic_boolE_St17reference_wrapperIS6_EEEvEEE6_M_runEv
> @ 0x2b5495b81a40 (unknown)
> @ 0x2b54962f8182 start_thread
> @ 0x2b549660847d (unknown)
> make[3]: *** [check-local] Segmentation fault
> make[3]: Leaving directory `/home/vagrant/mesos/build/src'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory 

[jira] [Created] (MESOS-4085) Implement implicit roles

[Neil Conway (JIRA)]

Neil Conway created MESOS-4085:
--

 Summary: Implement implicit roles
 Key: MESOS-4085
 URL: https://issues.apache.org/jira/browse/MESOS-4085
 Project: Mesos
  Issue Type: Improvement
Reporter: Neil Conway






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-4085) Implement implicit roles

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway reassigned MESOS-4085:
--

Assignee: Neil Conway

> Implement implicit roles
> 
>
> Key: MESOS-4085
> URL: https://issues.apache.org/jira/browse/MESOS-4085
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: mesosphere, roles
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4085) Implement implicit roles

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-4085:
---
Shepherd: Adam B

> Implement implicit roles
> 
>
> Key: MESOS-4085
> URL: https://issues.apache.org/jira/browse/MESOS-4085
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: mesosphere, roles
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3928) ROOT tests fail on Mesos 0.26 on Ubuntu/CentOS

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-3928:
-
Sprint: Mesosphere Sprint 23  (was: Mesosphere Sprint 23, Mesosphere Sprint 
24)

> ROOT tests fail on Mesos 0.26 on Ubuntu/CentOS
> --
>
> Key: MESOS-3928
> URL: https://issues.apache.org/jira/browse/MESOS-3928
> Project: Mesos
>  Issue Type: Bug
>Affects Versions: 0.26.0
>Reporter: Marco Massenzio
>Assignee: Greg Mann
>  Labels: tech-debt, testing
> Attachments: ROOT-tests-centos-7.1.log, ROOT-tests-ubuntu-14.04.log
>
>
> Running {{0.26.0-rc1}} on both CentOS 7.1 and Ubuntu 14.04 with {{sudo}} 
> privileges, causes segfaults when running Docker tests.
> Logs attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4085) Implement implicit roles

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-4085:
---
Sprint: Mesosphere Sprint 24

> Implement implicit roles
> 
>
> Key: MESOS-4085
> URL: https://issues.apache.org/jira/browse/MESOS-4085
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: mesosphere, roles
>
> See also design doc: MESOS-4000.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2857) FetcherCacheTest.LocalCachedExtract is flaky.

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske updated MESOS-2857:
--
Shepherd: Bernd Mathiske

> FetcherCacheTest.LocalCachedExtract is flaky.
> -
>
> Key: MESOS-2857
> URL: https://issues.apache.org/jira/browse/MESOS-2857
> Project: Mesos
>  Issue Type: Bug
>  Components: fetcher, test
>Reporter: Benjamin Mahler
>Assignee: Benjamin Bannier
>  Labels: flaky-test, mesosphere
>
> From jenkins:
> {noformat}
> [ RUN  ] FetcherCacheTest.LocalCachedExtract
> Using temporary directory '/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj'
> I0610 20:04:48.591573 24561 leveldb.cpp:176] Opened db in 3.512525ms
> I0610 20:04:48.592456 24561 leveldb.cpp:183] Compacted db in 828630ns
> I0610 20:04:48.592512 24561 leveldb.cpp:198] Created db iterator in 32992ns
> I0610 20:04:48.592531 24561 leveldb.cpp:204] Seeked to beginning of db in 
> 8967ns
> I0610 20:04:48.592545 24561 leveldb.cpp:273] Iterated through 0 keys in the 
> db in 7762ns
> I0610 20:04:48.592604 24561 replica.cpp:744] Replica recovered with log 
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0610 20:04:48.593438 24587 recover.cpp:449] Starting replica recovery
> I0610 20:04:48.593698 24587 recover.cpp:475] Replica is in EMPTY status
> I0610 20:04:48.595641 24580 replica.cpp:641] Replica in EMPTY status received 
> a broadcasted recover request
> I0610 20:04:48.596086 24590 recover.cpp:195] Received a recover response from 
> a replica in EMPTY status
> I0610 20:04:48.596607 24590 recover.cpp:566] Updating replica status to 
> STARTING
> I0610 20:04:48.597507 24590 leveldb.cpp:306] Persisting metadata (8 bytes) to 
> leveldb took 717888ns
> I0610 20:04:48.597535 24590 replica.cpp:323] Persisted replica status to 
> STARTING
> I0610 20:04:48.597697 24590 recover.cpp:475] Replica is in STARTING status
> I0610 20:04:48.599165 24584 replica.cpp:641] Replica in STARTING status 
> received a broadcasted recover request
> I0610 20:04:48.599434 24584 recover.cpp:195] Received a recover response from 
> a replica in STARTING status
> I0610 20:04:48.599915 24590 recover.cpp:566] Updating replica status to VOTING
> I0610 20:04:48.600545 24590 leveldb.cpp:306] Persisting metadata (8 bytes) to 
> leveldb took 432335ns
> I0610 20:04:48.600574 24590 replica.cpp:323] Persisted replica status to 
> VOTING
> I0610 20:04:48.600659 24590 recover.cpp:580] Successfully joined the Paxos 
> group
> I0610 20:04:48.600797 24590 recover.cpp:464] Recover process terminated
> I0610 20:04:48.602905 24594 master.cpp:363] Master 
> 20150610-200448-3875541420-32907-24561 (dbade881e927) started on 
> 172.17.0.231:32907
> I0610 20:04:48.602957 24594 master.cpp:365] Flags at startup: --acls="" 
> --allocation_interval="1secs" --allocator="HierarchicalDRF" 
> --authenticate="true" --authenticate_slaves="true" --authenticators="crammd5" 
> --credentials="/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/credentials" 
> --framework_sorter="drf" --help="false" --initialize_driver_logging="true" 
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO" 
> --quiet="false" --recovery_slave_removal_limit="100%" 
> --registry="replicated_log" --registry_fetch_timeout="1mins" 
> --registry_store_timeout="25secs" --registry_strict="true" 
> --root_submissions="true" --slave_reregister_timeout="10mins" 
> --user_sorter="drf" --version="false" 
> --webui_dir="/mesos/mesos-0.23.0/_inst/share/mesos/webui" 
> --work_dir="/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/master" 
> --zk_session_timeout="10secs"
> I0610 20:04:48.603374 24594 master.cpp:410] Master only allowing 
> authenticated frameworks to register
> I0610 20:04:48.603392 24594 master.cpp:415] Master only allowing 
> authenticated slaves to register
> I0610 20:04:48.603404 24594 credentials.hpp:37] Loading credentials for 
> authentication from 
> '/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/credentials'
> I0610 20:04:48.603751 24594 master.cpp:454] Using default 'crammd5' 
> authenticator
> I0610 20:04:48.604928 24594 master.cpp:491] Authorization enabled
> I0610 20:04:48.606034 24593 hierarchical.hpp:309] Initialized hierarchical 
> allocator process
> I0610 20:04:48.606106 24593 whitelist_watcher.cpp:79] No whitelist given
> I0610 20:04:48.607430 24594 master.cpp:1476] The newly elected leader is 
> master@172.17.0.231:32907 with id 20150610-200448-3875541420-32907-24561
> I0610 20:04:48.607466 24594 master.cpp:1489] Elected as the leading master!
> I0610 20:04:48.607481 24594 master.cpp:1259] Recovering from registrar
> I0610 20:04:48.607712 24594 registrar.cpp:313] Recovering registrar
> I0610 20:04:48.608543 24588 log.cpp:661] Attempting to start the writer
> I0610 20:04:48.610231 24588 replica.cpp:477] Replica received implicit 
> promise request 

[jira] [Updated] (MESOS-3861) Authenticate quota requests

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-3861:
---
Shepherd: Till Toenshoff  (was: Joris Van Remoortere)

> Authenticate quota requests
> ---
>
> Key: MESOS-3861
> URL: https://issues.apache.org/jira/browse/MESOS-3861
> Project: Mesos
>  Issue Type: Task
>  Components: master
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere, security
>
> Quota requests need to be authenticated.
> This ticket will authenticate quota requests using credentials provided by 
> the {{Authorization}} field of the HTTP request. This is similar to how 
> authentication is implemented in {{Master::Http}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-4015) Expose task / executor health in master & slave state.json

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan reassigned MESOS-4015:


Assignee: Artem Harutyunyan

> Expose task / executor health in master & slave state.json
> --
>
> Key: MESOS-4015
> URL: https://issues.apache.org/jira/browse/MESOS-4015
> Project: Mesos
>  Issue Type: Improvement
>Affects Versions: 0.25.0
>Reporter: Sargun Dhillon
>Assignee: Artem Harutyunyan
>Priority: Trivial
>  Labels: mesosphere
>
> Right now, if I specify a healthcheck for a task, the only way to get to it 
> is via the Task Status updates that come to the framework. Unfortunately, 
> this information isn't exposed in the state.json either in the slave or 
> master. It'd be ideal to have that information to enable tools like Mesos-DNS 
> to be health-aware.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4064) Add ContainerInfo to internal Task protobuf.

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4064:
-
Sprint: Mesosphere Sprint 24

> Add ContainerInfo to internal Task protobuf.
> 
>
> Key: MESOS-4064
> URL: https://issues.apache.org/jira/browse/MESOS-4064
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Artem Harutyunyan
>  Labels: mesosphere
>
> In what seems like an oversight, when ContainerInfo was added to TaskInfo, it 
> was not added to our internal Task protobuf.
> Also, unlike the agent, it appears that the master does not use 
> protobuf::createTask. We should try remove the manual construction in the 
> master in favor of construction through protobuf::createTask.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-4064) Add ContainerInfo to internal Task protobuf.

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan reassigned MESOS-4064:


Assignee: Artem Harutyunyan

> Add ContainerInfo to internal Task protobuf.
> 
>
> Key: MESOS-4064
> URL: https://issues.apache.org/jira/browse/MESOS-4064
> Project: Mesos
>  Issue Type: Task
>Reporter: Benjamin Mahler
>Assignee: Artem Harutyunyan
>  Labels: mesosphere
>
> In what seems like an oversight, when ContainerInfo was added to TaskInfo, it 
> was not added to our internal Task protobuf.
> Also, unlike the agent, it appears that the master does not use 
> protobuf::createTask. We should try remove the manual construction in the 
> master in favor of construction through protobuf::createTask.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4015) Expose task / executor health in master & slave state.json

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4015:
-
Sprint: Mesosphere Sprint 24

> Expose task / executor health in master & slave state.json
> --
>
> Key: MESOS-4015
> URL: https://issues.apache.org/jira/browse/MESOS-4015
> Project: Mesos
>  Issue Type: Improvement
>Affects Versions: 0.25.0
>Reporter: Sargun Dhillon
>Assignee: Artem Harutyunyan
>Priority: Trivial
>  Labels: mesosphere
>
> Right now, if I specify a healthcheck for a task, the only way to get to it 
> is via the Task Status updates that come to the framework. Unfortunately, 
> this information isn't exposed in the state.json either in the slave or 
> master. It'd be ideal to have that information to enable tools like Mesos-DNS 
> to be health-aware.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3962) Add labels to the message Port

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-3962:
-
Assignee: (was: Artem Harutyunyan)

> Add labels to the message Port
> --
>
> Key: MESOS-3962
> URL: https://issues.apache.org/jira/browse/MESOS-3962
> Project: Mesos
>  Issue Type: Wish
>Reporter: Sargun Dhillon
>Priority: Minor
>  Labels: mesosphere
>
> I want to add arbitrary labels to the message "Port". I have a few use cases 
> for this:
> 1) I want to use it to drive isolators to install firewall rules associated 
> with the port
> 2) I want to use it to drive third party components to be able to specify 
> advertising information
> 3) I want to be able to able to use this to associate a deterministic virtual 
> hostname with a given port
> Ideally, once the task is launched, these labels would be immutable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3962) Add labels to the message Port

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-3962:
-
Sprint: Mesosphere Sprint 24

> Add labels to the message Port
> --
>
> Key: MESOS-3962
> URL: https://issues.apache.org/jira/browse/MESOS-3962
> Project: Mesos
>  Issue Type: Wish
>Reporter: Sargun Dhillon
>Priority: Minor
>  Labels: mesosphere
>
> I want to add arbitrary labels to the message "Port". I have a few use cases 
> for this:
> 1) I want to use it to drive isolators to install firewall rules associated 
> with the port
> 2) I want to use it to drive third party components to be able to specify 
> advertising information
> 3) I want to be able to able to use this to associate a deterministic virtual 
> hostname with a given port
> Ideally, once the task is launched, these labels would be immutable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-3962) Add labels to the message Port

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song reassigned MESOS-3962:
---

Assignee: Gilbert Song

> Add labels to the message Port
> --
>
> Key: MESOS-3962
> URL: https://issues.apache.org/jira/browse/MESOS-3962
> Project: Mesos
>  Issue Type: Wish
>Reporter: Sargun Dhillon
>Assignee: Gilbert Song
>Priority: Minor
>  Labels: mesosphere
>
> I want to add arbitrary labels to the message "Port". I have a few use cases 
> for this:
> 1) I want to use it to drive isolators to install firewall rules associated 
> with the port
> 2) I want to use it to drive third party components to be able to specify 
> advertising information
> 3) I want to be able to able to use this to associate a deterministic virtual 
> hostname with a given port
> Ideally, once the task is launched, these labels would be immutable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-3962) Add labels to the message Port

[Artem Harutyunyan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan reassigned MESOS-3962:


Assignee: Artem Harutyunyan

> Add labels to the message Port
> --
>
> Key: MESOS-3962
> URL: https://issues.apache.org/jira/browse/MESOS-3962
> Project: Mesos
>  Issue Type: Wish
>Reporter: Sargun Dhillon
>Assignee: Artem Harutyunyan
>Priority: Minor
>  Labels: mesosphere
>
> I want to add arbitrary labels to the message "Port". I have a few use cases 
> for this:
> 1) I want to use it to drive isolators to install firewall rules associated 
> with the port
> 2) I want to use it to drive third party components to be able to specify 
> advertising information
> 3) I want to be able to able to use this to associate a deterministic virtual 
> hostname with a given port
> Ideally, once the task is launched, these labels would be immutable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3024) HTTP endpoint authN is enabled merely by specifying --credentials

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-3024:
--
Assignee: (was: Marco Massenzio)

> HTTP endpoint authN is enabled merely by specifying --credentials
> -
>
> Key: MESOS-3024
> URL: https://issues.apache.org/jira/browse/MESOS-3024
> Project: Mesos
>  Issue Type: Bug
>  Components: master, security
>Reporter: Adam B
>  Labels: authentication, http, mesosphere
>
> If I set `--credentials` on the master, framework and slave authentication 
> are allowed, but not required. On the other hand, http authentication is now 
> required for authenticated endpoints (currently only `/shutdown`). That means 
> that I cannot enable framework or slave authentication without also enabling 
> http endpoint authentication. This is undesirable.
> Framework and slave authentication have separate flags (`\--authenticate` and 
> `\--authenticate_slaves`) to require authentication for each. It would be 
> great if there was also such a flag for http authentication. Or maybe we get 
> rid of these flags altogether and rely on ACLs to determine which 
> unauthenticated principals are even allowed to authenticate for each 
> endpoint/action.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3962) Add labels to the message Port

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song updated MESOS-3962:

Assignee: (was: Gilbert Song)

> Add labels to the message Port
> --
>
> Key: MESOS-3962
> URL: https://issues.apache.org/jira/browse/MESOS-3962
> Project: Mesos
>  Issue Type: Wish
>Reporter: Sargun Dhillon
>Priority: Minor
>  Labels: mesosphere
>
> I want to add arbitrary labels to the message "Port". I have a few use cases 
> for this:
> 1) I want to use it to drive isolators to install firewall rules associated 
> with the port
> 2) I want to use it to drive third party components to be able to specify 
> advertising information
> 3) I want to be able to able to use this to associate a deterministic virtual 
> hostname with a given port
> Ideally, once the task is launched, these labels would be immutable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4077) Prototype quota removal authorization

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4077:

Shepherd:   (was: Joris Van Remoortere)

> Prototype quota removal authorization
> -
>
> Key: MESOS-4077
> URL: https://issues.apache.org/jira/browse/MESOS-4077
> Project: Mesos
>  Issue Type: Task
>  Components: master
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Critical
>  Labels: mesosphere, quota
>
> For the quota remove endpoint authorization has to be implemented, similar to 
> the quota set endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2353) Improve performance of the master's state.json endpoint for large clusters.

[Michael Park (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Park updated MESOS-2353:

Shepherd: Benjamin Hindman
Assignee: Michael Park
  Sprint: Twitter Mesos Q1 Sprint 5, Mesosphere Sprint 24  (was: Twitter 
Mesos Q1 Sprint 5)

> Improve performance of the master's state.json endpoint for large clusters.
> ---
>
> Key: MESOS-2353
> URL: https://issues.apache.org/jira/browse/MESOS-2353
> Project: Mesos
>  Issue Type: Improvement
>  Components: master
>Reporter: Benjamin Mahler
>Assignee: Michael Park
>  Labels: newbie, scalability, twitter
>
> The master's state.json endpoint consistently takes a long time to compute 
> the JSON result, for large clusters:
> {noformat}
> $ time curl -s -o /dev/null localhost:5050/master/state.json
> Mon Jan 26 22:38:50 UTC 2015
> real  0m13.174s
> user  0m0.003s
> sys   0m0.022s
> {noformat}
> This can cause the master to get backlogged if there are many state.json 
> requests in flight.
> Looking at {{perf}} data, it seems most of the time is spent doing memory 
> allocation / de-allocation. This ticket will try to capture any low hanging 
> fruit to speed this up. Possibly we can leverage moves if they are not 
> already being used by the compiler.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4078) Prototype tests for quota authentication and authorization

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4078:

Shepherd:   (was: Joris Van Remoortere)

> Prototype tests for quota authentication and authorization
> --
>
> Key: MESOS-4078
> URL: https://issues.apache.org/jira/browse/MESOS-4078
> Project: Mesos
>  Issue Type: Task
>  Components: master, test
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Critical
>  Labels: mesosphere, quota
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4083) Add tests for quota removal

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4083:

Shepherd:   (was: Joris Van Remoortere)

> Add tests for quota removal
> ---
>
> Key: MESOS-4083
> URL: https://issues.apache.org/jira/browse/MESOS-4083
> Project: Mesos
>  Issue Type: Task
>  Components: master, test
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere, quota
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4082) Add Tests for quota authentification and authorization

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4082:

Shepherd:   (was: Joris Van Remoortere)

> Add Tests for quota authentification and authorization
> --
>
> Key: MESOS-4082
> URL: https://issues.apache.org/jira/browse/MESOS-4082
> Project: Mesos
>  Issue Type: Task
>  Components: master, test
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere, quota
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4079) Prototype tests for quota removal authorization

[Jan Schlicht (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4079:

Shepherd:   (was: Joris Van Remoortere)

> Prototype tests for quota removal authorization
> ---
>
> Key: MESOS-4079
> URL: https://issues.apache.org/jira/browse/MESOS-4079
> Project: Mesos
>  Issue Type: Task
>  Components: master, test
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>Priority: Critical
>  Labels: mesosphere, quota
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3761) Support C++11 lambda syntax for delay()

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3761:
---
Labels: c++11 mesosphere  (was: mesosphere)

> Support C++11 lambda syntax for delay()
> ---
>
> Key: MESOS-3761
> URL: https://issues.apache.org/jira/browse/MESOS-3761
> Project: Mesos
>  Issue Type: Improvement
>  Components: libprocess
>Reporter: Neil Conway
>Priority: Minor
>  Labels: c++11, mesosphere
>
> Right now, we support {{delay(Seconds(5), ::foo);}}, but it would 
> be better to also support passing a C++11 lambda.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-313) report executor deaths to framework schedulers

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-313:
-
Story Points: 2

> report executor deaths to framework schedulers
> --
>
> Key: MESOS-313
> URL: https://issues.apache.org/jira/browse/MESOS-313
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Charles Reiss
>Assignee: Zhitao Li
>  Labels: mesosphere, newbie
>
> The Scheduler interface has a callback for executorLost, but currently it is 
> never called.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-313) report executor deaths to framework schedulers

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-313:
-
Sprint: Mesosphere Sprint 24

> report executor deaths to framework schedulers
> --
>
> Key: MESOS-313
> URL: https://issues.apache.org/jira/browse/MESOS-313
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Charles Reiss
>Assignee: Zhitao Li
>  Labels: mesosphere, newbie
>
> The Scheduler interface has a callback for executorLost, but currently it is 
> never called.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3065) Add framework authorization for persistent volume

[Adam B (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045558#comment-15045558
 ] 

Adam B commented on MESOS-3065:
---

Can this be resolved as a duplicate of MESOS-3903 or do we need separate 
ACLs/API-checks for which framework principals are allowed to create/destroy 
volumes?

> Add framework authorization for persistent volume
> -
>
> Key: MESOS-3065
> URL: https://issues.apache.org/jira/browse/MESOS-3065
> Project: Mesos
>  Issue Type: Task
>Reporter: Michael Park
>Assignee: Greg Mann
>  Labels: mesosphere, persistent-volumes
>
> Persistent volume should be authorized with the {{principal}} of the 
> reserving entity (framework or master). The idea is to introduce {{Create}} 
> and {{Destroy}} into the ACL.
> {code}
>   message Create {
> // Subjects.
> required Entity principals = 1;
> // Objects? Perhaps the kind of volume? allowed permissions?
>   }
>   message Destroy {
> // Subjects.
> required Entity principals = 1;
> // Objects.
> required Entity creator_principals = 2;
>   }
> {code}
> When a framework creates a persistent volume, "create" ACLs are checked to 
> see if the framework (FrameworkInfo.principal) or the operator 
> (Credential.user) is authorized to create persistent volumes. If not 
> authorized, the create operation is rejected.
> When a framework destroys a persistent volume, "destroy" ACLs are checked to 
> see if the framework (FrameworkInfo.principal) or the operator 
> (Credential.user) is authorized to destroy the persistent volume created by a 
> framework or operator (Resource.DiskInfo.principal). If not authorized, the 
> destroy operation is rejected.
> A separate ticket will use the structures created here to enable 
> authorization of the "/create" and "/destroy" HTTP endpoints: 
> https://issues.apache.org/jira/browse/MESOS-3903



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3608) optionally install test binaries

[Till Toenshoff (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till Toenshoff updated MESOS-3608:
--
Labels: mesosphere  (was: )

> optionally install test binaries
> 
>
> Key: MESOS-3608
> URL: https://issues.apache.org/jira/browse/MESOS-3608
> Project: Mesos
>  Issue Type: Improvement
>  Components: build, test
>Reporter: James Peach
>Assignee: James Peach
>Priority: Minor
>  Labels: mesosphere
>
> Many of the tests in Mesos could be described as integration tests, since 
> they have external dependencies on kernel features, installed tools, 
> permissions, etc. I'd like to be able to generate a {{mesos-tests}} RPM along 
> with my {{mesos}} RPM so that I can run the same tests in different 
> deployment environments.
> I propose a new configuration option named {{--enable-test-tools}} that will 
> install the tests into {{libexec/mesos/tests}}. I'll also need to make some 
> minor changes to tests so that helper tools can be found in this location as 
> well as in the build directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1872) Cleanup right angle bracket in the code base.

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-1872:
---
Issue Type: Improvement  (was: Bug)

> Cleanup right angle bracket in the code base.
> -
>
> Key: MESOS-1872
> URL: https://issues.apache.org/jira/browse/MESOS-1872
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Jie Yu
>Assignee: Evelina Dumitrescu
>  Labels: c++11, newbie
>
> As we start to use c++11 style right angle brackets ('>>' instead of '> >'):
> https://reviews.apache.org/r/25861
> We should do a sweep in our code base to make it consistent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4012) Update documentation to reflect the addition of installable tests.

[Till Toenshoff (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till Toenshoff updated MESOS-4012:
--
Labels: mesosphere  (was: )

> Update documentation to reflect the addition of installable tests.  
> 
>
> Key: MESOS-4012
> URL: https://issues.apache.org/jira/browse/MESOS-4012
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Till Toenshoff
>  Labels: mesosphere
>
> We may want to add the needed steps for administrators to create and run the 
> test-suite on anything other than the build machine. 
> One possible location could be {{docs/gettings-started.md}} for validating 
> the pre-requisites as described in that document. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-2782) document the sandbox

[Joseph Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu reassigned MESOS-2782:


Assignee: Joseph Wu

> document the sandbox
> 
>
> Key: MESOS-2782
> URL: https://issues.apache.org/jira/browse/MESOS-2782
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Aaron Bell
>Assignee: Joseph Wu
>  Labels: documentation, mesosphere
>
> The sandbox is the arena of debugging for most Mesos users. From an 
> application- or framework-developer perspective, they need to know
> - What it is
> - Where it is
> - How to use it, and how NOT to use it
> - What Mesos writes here (fetcher etc.)
> - Storage limits
> - Lifecycle and garbage collection
> This needs to be documented to help users get over the hump of learning to 
> work with Mesos.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2782) document the sandbox

[Joseph Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu updated MESOS-2782:
-
Sprint: Mesosphere Sprint 24

> document the sandbox
> 
>
> Key: MESOS-2782
> URL: https://issues.apache.org/jira/browse/MESOS-2782
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Aaron Bell
>Assignee: Joseph Wu
>  Labels: documentation, mesosphere
>
> The sandbox is the arena of debugging for most Mesos users. From an 
> application- or framework-developer perspective, they need to know
> - What it is
> - Where it is
> - How to use it, and how NOT to use it
> - What Mesos writes here (fetcher etc.)
> - Storage limits
> - Lifecycle and garbage collection
> This needs to be documented to help users get over the hump of learning to 
> work with Mesos.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2639) Document expected label values throughout hook tests

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-2639:
--
Shepherd:   (was: Adam B)

> Document expected label values throughout hook tests
> 
>
> Key: MESOS-2639
> URL: https://issues.apache.org/jira/browse/MESOS-2639
> Project: Mesos
>  Issue Type: Documentation
>  Components: technical debt
>Reporter: Niklas Quarfot Nielsen
>Priority: Minor
>  Labels: mesosphere
>
> Labels gets added and removed at different places in the hooks test and can 
> be hard to wrap your head around. We can add a diagram illustrating the 
> expected values and why we have chosen those permutations (which corner cases 
> we try to expose, etc).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2315) Deprecate / Remove CommandInfo::ContainerInfo

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-2315:
--
  Sprint: Mesosphere Sprint 24
Story Points: 2

Sorry for letting this sit for so long. I'll make sure to review it this sprint.

> Deprecate / Remove CommandInfo::ContainerInfo
> -
>
> Key: MESOS-2315
> URL: https://issues.apache.org/jira/browse/MESOS-2315
> Project: Mesos
>  Issue Type: Task
>Reporter: Ian Downes
>Assignee: Vaibhav Khanduja
>Priority: Minor
>  Labels: mesosphere, newbie
> Attachments: diff.txt
>
>
> IIUC this has been deprecated and all current code (except 
> examples/docker_no_executor_framework.cpp) uses the top-level ContainerInfo?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-3936) Document possible task state transitions for framework authors

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway reassigned MESOS-3936:
--

Assignee: Neil Conway

> Document possible task state transitions for framework authors
> --
>
> Key: MESOS-3936
> URL: https://issues.apache.org/jira/browse/MESOS-3936
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: documentation, mesosphere
>
> We should document the possible ways in which the state of a task can evolve 
> over time; what happens when an agent is partitioned from the master; and 
> more generally, how we recommend that framework authors develop 
> fault-tolerant schedulers and do task state reconciliation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3374) Improve High Availability documentation

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3374:
---
Shepherd: Benjamin Hindman

> Improve High Availability documentation
> ---
>
> Key: MESOS-3374
> URL: https://issues.apache.org/jira/browse/MESOS-3374
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Affects Versions: 0.23.0
>Reporter: Aaron Bell
>Assignee: Neil Conway
>Priority: Minor
>  Labels: documentation, mesosphere
>
> This [Call Me Maybe 
> article|https://aphyr.com/posts/326-call-me-maybe-chronos] used the Jepsen 
> tool to evaluate Chronos running on Mesos. It uncovered bug MESOS-3280.
> Action: Improve documentation at 
> http://mesos.apache.org/documentation/latest/high-availability to include 
> 'good practice' patterns or recommendations.
> For example:
> - We RECOMMEND running ZooKeeper co-located with Mesos masters.
> -- This reduces the set of network partitions to worry about.
> -- This means you’re going to have 1 ZK node for every Mesos master.
> -- This is NOT technically required. If you have a different ZK deployment 
> architecture you're free to use it.
> - _More ideas_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3374) Improve High Availability documentation

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3374:
---
Shepherd: Jie Yu  (was: Benjamin Hindman)

> Improve High Availability documentation
> ---
>
> Key: MESOS-3374
> URL: https://issues.apache.org/jira/browse/MESOS-3374
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Affects Versions: 0.23.0
>Reporter: Aaron Bell
>Assignee: Neil Conway
>Priority: Minor
>  Labels: documentation, mesosphere
>
> This [Call Me Maybe 
> article|https://aphyr.com/posts/326-call-me-maybe-chronos] used the Jepsen 
> tool to evaluate Chronos running on Mesos. It uncovered bug MESOS-3280.
> Action: Improve documentation at 
> http://mesos.apache.org/documentation/latest/high-availability to include 
> 'good practice' patterns or recommendations.
> For example:
> - We RECOMMEND running ZooKeeper co-located with Mesos masters.
> -- This reduces the set of network partitions to worry about.
> -- This means you’re going to have 1 ZK node for every Mesos master.
> -- This is NOT technically required. If you have a different ZK deployment 
> architecture you're free to use it.
> - _More ideas_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2782) document the sandbox

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-2782:
--
Shepherd: Jie Yu  (was: Adam B)

> document the sandbox
> 
>
> Key: MESOS-2782
> URL: https://issues.apache.org/jira/browse/MESOS-2782
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Aaron Bell
>Assignee: Joseph Wu
>  Labels: documentation, mesosphere
>
> The sandbox is the arena of debugging for most Mesos users. From an 
> application- or framework-developer perspective, they need to know
> - What it is
> - Where it is
> - How to use it, and how NOT to use it
> - What Mesos writes here (fetcher etc.)
> - Storage limits
> - Lifecycle and garbage collection
> This needs to be documented to help users get over the hump of learning to 
> work with Mesos.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3936) Document possible task state transitions for framework authors

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3936:
---
Shepherd: Benjamin Hindman

> Document possible task state transitions for framework authors
> --
>
> Key: MESOS-3936
> URL: https://issues.apache.org/jira/browse/MESOS-3936
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: documentation, mesosphere
>
> We should document the possible ways in which the state of a task can evolve 
> over time; what happens when an agent is partitioned from the master; and 
> more generally, how we recommend that framework authors develop 
> fault-tolerant schedulers and do task state reconciliation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-3996) libprocess: document when, why defer() is necessary

[Greg Mann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann reassigned MESOS-3996:


Assignee: Greg Mann

> libprocess: document when, why defer() is necessary
> ---
>
> Key: MESOS-3996
> URL: https://issues.apache.org/jira/browse/MESOS-3996
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Neil Conway
>Assignee: Greg Mann
>Priority: Minor
>  Labels: documentation, libprocess, mesosphere
>
> Current rules around this are pretty confusing and undocumented, as evidenced 
> by some recent bugs in this area.
> Some example snippets in the mesos source code that were a result of this 
> confusion and are indeed bugs:
> 1. 
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/mesos/provisioner/docker/registry_client.cpp#L754
> {code}
> return doHttpGet(blobURL, None(), true, true, None())
> .then([this, blobURLPath, digest, filePath](
> const http::Response& response) -> Future {
>   Try fd = os::open(
>   filePath.value,
>   O_WRONLY | O_CREAT | O_TRUNC | O_CLOEXEC,
>   S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3996) libprocess: document when, why defer() is necessary

[Greg Mann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann updated MESOS-3996:
-
Shepherd: Benjamin Hindman
  Sprint: Mesosphere Sprint 24
Story Points: 1

> libprocess: document when, why defer() is necessary
> ---
>
> Key: MESOS-3996
> URL: https://issues.apache.org/jira/browse/MESOS-3996
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Neil Conway
>Assignee: Greg Mann
>Priority: Minor
>  Labels: documentation, libprocess, mesosphere
>
> Current rules around this are pretty confusing and undocumented, as evidenced 
> by some recent bugs in this area.
> Some example snippets in the mesos source code that were a result of this 
> confusion and are indeed bugs:
> 1. 
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/mesos/provisioner/docker/registry_client.cpp#L754
> {code}
> return doHttpGet(blobURL, None(), true, true, None())
> .then([this, blobURLPath, digest, filePath](
> const http::Response& response) -> Future {
>   Try fd = os::open(
>   filePath.value,
>   O_WRONLY | O_CREAT | O_TRUNC | O_CLOEXEC,
>   S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-2998) Disable Persistent Volumes, Dynamic Reservations via master flags

[Adam B (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045584#comment-15045584
 ] 

Adam B commented on MESOS-2998:
---

This ticket was intended as a stopgap until we get the ACLs in place. Now that 
we're landing the ACLs, I think we can close it (duplicate? won't fix?). 
Objections?

cc: [~jieyu], [~greggomann]

> Disable Persistent Volumes, Dynamic Reservations via master flags
> -
>
> Key: MESOS-2998
> URL: https://issues.apache.org/jira/browse/MESOS-2998
> Project: Mesos
>  Issue Type: Improvement
>  Components: master
>Affects Versions: 0.23.0
>Reporter: Adam B
>Assignee: Michael Park
>  Labels: mesosphere, persistence, reservations, volumes
>
> As an operator, I might not want frameworks using the experimental dynamic 
> reservations/persistent volumes APIs in 0.23, since there are no ACLs or 
> operator endpoints for me to manage them. That means that a rogue framework 
> could start reserving resources and creating volumes with all resources 
> provided, and I would have no way to clean them up.
> Is it possible to disable these features from the master (flags, etc.)?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3936) Document possible task state transitions for framework authors

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3936:
---
Sprint: Mesosphere Sprint 24

> Document possible task state transitions for framework authors
> --
>
> Key: MESOS-3936
> URL: https://issues.apache.org/jira/browse/MESOS-3936
> Project: Mesos
>  Issue Type: Documentation
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: documentation, mesosphere
>
> We should document the possible ways in which the state of a task can evolve 
> over time; what happens when an agent is partitioned from the master; and 
> more generally, how we recommend that framework authors develop 
> fault-tolerant schedulers and do task state reconciliation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3954) The documentation should recommend an updated systemd for centos 7.

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3954:
---
 Sprint: Mesosphere Sprint 24
Component/s: documentation

> The documentation should recommend an updated systemd for centos 7.
> ---
>
> Key: MESOS-3954
> URL: https://issues.apache.org/jira/browse/MESOS-3954
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Till Toenshoff
>Priority: Minor
>  Labels: documentation, mesosphere
>
> After installing a plain centos 7, some Mesos tests kept failing due to 
> MESOS-3352.
> We should try to minimize such experience for our users by e.g. adding the 
> need for an explicit systemd update on this distribution (and maybe others).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3374) Improve High Availability documentation

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3374:
---
   Sprint: Mesosphere Sprint 24
Affects Version/s: (was: 0.23.0)

> Improve High Availability documentation
> ---
>
> Key: MESOS-3374
> URL: https://issues.apache.org/jira/browse/MESOS-3374
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Aaron Bell
>Assignee: Neil Conway
>Priority: Minor
>  Labels: documentation, mesosphere
>
> This [Call Me Maybe 
> article|https://aphyr.com/posts/326-call-me-maybe-chronos] used the Jepsen 
> tool to evaluate Chronos running on Mesos. It uncovered bug MESOS-3280.
> Action: Improve documentation at 
> http://mesos.apache.org/documentation/latest/high-availability to include 
> 'good practice' patterns or recommendations.
> For example:
> - We RECOMMEND running ZooKeeper co-located with Mesos masters.
> -- This reduces the set of network partitions to worry about.
> -- This means you’re going to have 1 ZK node for every Mesos master.
> -- This is NOT technically required. If you have a different ZK deployment 
> architecture you're free to use it.
> - _More ideas_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3305) Getting Started docs for Ubuntu needs reference to libsasl2-modules

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3305:
---
Sprint: Mesosphere Sprint 24

> Getting Started docs for Ubuntu needs reference to libsasl2-modules
> ---
>
> Key: MESOS-3305
> URL: https://issues.apache.org/jira/browse/MESOS-3305
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Affects Versions: 0.23.0
> Environment: Ubuntu 14.04
>Reporter: Andrew A Smith
>Priority: Minor
>  Labels: documentation, mesosphere, newbie
>
> Following the Getting Started docs leads to an error during configure, due to 
> a missing dependency.
> Error during configure:
> checking SASL CRAM-MD5 support... configure: error: no
> ---
> We need CRAM-MD5 support for SASL authentication.
> ---



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3844) getting started documentation has flaws, corrections suggested (http://mesos.apache.org/gettingstarted/)

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3844:
---
Sprint: Mesosphere Sprint 24

> getting started documentation has flaws, corrections suggested 
> (http://mesos.apache.org/gettingstarted/)
> 
>
> Key: MESOS-3844
> URL: https://issues.apache.org/jira/browse/MESOS-3844
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, project website, test
>Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 
> (x86_64) with Updates HVM (a t2.medium instance)
>Reporter: Manne Laukkanen
>Priority: Trivial
>  Labels: build, documentation, mesosphere
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Getting started documentation, while having great virtues, has room for 
> improvement:
> 1) Documentation is illogical and wrong for this part:
>  " $ wget http://www.apache.org/dist/mesos/0.25.0/mesos-0.25.0.tar.gz
>  $ tar -zxf mesos-0.25.0.tar.gz" ...then, later:
> "# Install a few utility tools
> $ sudo yum install -y tar wget
> ..obviously using tar and wget is not possible before installing them.
> 2) Although vi is fine for many, utility tools having:
> sudo yum install -y tar wget nano
> might make editing e.g. the WANDISCO -repo file way easier for newbies.
> 3) Advice to launch Mesos with localhost option ( " ./bin/mesos-master.sh 
> --ip=127.0.0.1 --work_dir=/var/lib/mesos " ) will lead into a state where 
> Mesos UI can not be reached in port :5050 in a production environment e.g. in 
> AWS EC2. Mentioning this would help, not hinder deployment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3842) getting started documentation following Mesos 0.25 build fails for CentOS7 (http://mesos.apache.org/gettingstarted/)

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3842:
---
Sprint: Mesosphere Sprint 24

> getting started documentation following Mesos 0.25 build fails for CentOS7 
> (http://mesos.apache.org/gettingstarted/)
> 
>
> Key: MESOS-3842
> URL: https://issues.apache.org/jira/browse/MESOS-3842
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation, project website
>Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 
> (x86_64) with Updates HVM (a t2.medium instance)
>Reporter: Manne Laukkanen
>  Labels: build, documentation, mesosphere
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> WANdisco SVN repo file usage leads to failure of build process with error, so 
> usage of it should be 1) discouraged 2) replaced with a working solution
> Proceeding according to documentation at 
> http://mesos.apache.org/gettingstarted/:
> # 'Mesos > 0.21.0' requires 'subversion > 1.8' devel package, which is
> # not available in the default repositories.
> # Add the WANdisco SVN repo file: '/etc/yum.repos.d/wandisco-svn.repo' with 
> content:
>   [WANdiscoSVN]
>   name=WANdisco SVN Repo 1.9
>   enabled=1
>   baseurl=http://opensource.wandisco.com/centos/7/svn-1.9/RPMS/$basearch/
>   gpgcheck=1
>   gpgkey=http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco
> ...we do as is described, then proceed to next step, which is 
> "# Install essential development tools."
> sudo yum groupinstall -y "Development Tools"
> ...the added WANDISCO -repo causes failed building process with error:
> Error: Package: subversion-1.9.2-1.x86_64 (WANdiscoSVN)
>Requires: libserf-1.so.0()(64bit)
>  - we end up with e.g. no build tools to proceed with, so process fails, 
> Mesos can not be built according to instructions (e.g. no C-compiler in 
> path...)
> Interestingly, building with aforementioned instructions (with some 
> modifications mentioned in ticket MESOS-3844) was successful without errors 
> justa a few days ago on 30 Oct 2015. WANDISCO repo breakage? 
> No changes to building machine image (the CentOS7 image) nor machine itself 
> (t2.medium EC2 instance) were made in between attempts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-4075) Continue test suite execution across crashing tests.

[Bernd Mathiske (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Mathiske reassigned MESOS-4075:
-

Assignee: Bernd Mathiske

> Continue test suite execution across crashing tests.
> 
>
> Key: MESOS-4075
> URL: https://issues.apache.org/jira/browse/MESOS-4075
> Project: Mesos
>  Issue Type: Improvement
>  Components: test
>Affects Versions: 0.26.0
>Reporter: Bernd Mathiske
>Assignee: Bernd Mathiske
>  Labels: mesosphere
>
> Currently, mesos-tests.sh exits when a test crashes. This is inconvenient 
> when trying to find out all tests that fail. 
> mesos-tests.sh should rate a test that crashes as failed and continue the 
> same way as if the test merely returned with a failure result and exited 
> properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-1872) Cleanup right angle bracket in the code base.

[Neil Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045598#comment-15045598
 ] 

Neil Conway commented on MESOS-1872:


I believe the plan here is to do this incrementally (when we're modifying a 
file that uses the old-style brackets).

> Cleanup right angle bracket in the code base.
> -
>
> Key: MESOS-1872
> URL: https://issues.apache.org/jira/browse/MESOS-1872
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Jie Yu
>Assignee: Evelina Dumitrescu
>  Labels: c++11, newbie
>
> As we start to use c++11 style right angle brackets ('>>' instead of '> >'):
> https://reviews.apache.org/r/25861
> We should do a sweep in our code base to make it consistent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4086) Containerizer logging modularization

[Joseph Wu (JIRA)]

Joseph Wu created MESOS-4086:


 Summary: Containerizer logging modularization
 Key: MESOS-4086
 URL: https://issues.apache.org/jira/browse/MESOS-4086
 Project: Mesos
  Issue Type: Epic
  Components: containerization, modules
Reporter: Joseph Wu
Assignee: Joseph Wu


Executors and tasks are configured (via the various containerizers) to write 
their output (stdout/stderr) to files ("stdout" and "stderr") on an agent's 
disk.

Unlike Master/Agent logs, executor/task logs are not attached to any formal 
logging system, like {{glog}}.  As such, there is significant scope for 
improvement.

By introducing a module for logging, we can provide a common/programmatic way 
to access and manage executor/task logs.  Modules could implement additional 
sinks for logs, such as:
* to the sandbox (the status quo),
* to syslog,
* to journald

This would also provide the hooks to deal with logging related problems, such 
as:
* the (current) lack of log rotation,
* searching through executor/task logs (i.e. via aggregation)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-2153) Add support for systemd journal for logging

[Joseph Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu reassigned MESOS-2153:


Assignee: Joseph Wu

> Add support for systemd journal for logging
> ---
>
> Key: MESOS-2153
> URL: https://issues.apache.org/jira/browse/MESOS-2153
> Project: Mesos
>  Issue Type: Improvement
>  Components: master, slave
>Reporter: Alexander Rukletsov
>Assignee: Joseph Wu
>Priority: Minor
>  Labels: mesosphere
>
> We should be able to redirect master and slave logs to systemd journal on the 
> systems where it's available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2980) Allow runtime configuration to be returned from provisioner

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song updated MESOS-2980:

Sprint: Mesosphere Sprint 24

> Allow runtime configuration to be returned from provisioner
> ---
>
> Key: MESOS-2980
> URL: https://issues.apache.org/jira/browse/MESOS-2980
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Timothy Chen
>Assignee: Gilbert Song
>  Labels: mesosphere
>
> Image specs also includes execution configuration (e.g: Env, user, ports, 
> etc).
> We should support passing those information from the image provisioner back 
> to the containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4087) Introduce a module for logging executor/task output

[Joseph Wu (JIRA)]

Joseph Wu created MESOS-4087:


 Summary: Introduce a module for logging executor/task output
 Key: MESOS-4087
 URL: https://issues.apache.org/jira/browse/MESOS-4087
 Project: Mesos
  Issue Type: Task
  Components: containerization, modules
Reporter: Joseph Wu
Assignee: Joseph Wu


Existing executor/task logs are logged to files in their sandbox directory, 
with some nuances based on which containerizer is used (see background section 
in linked document).

A logger for executor/task logs has the following requirements:
* The logger is given a command to run and must handle the stdout/stderr of the 
command.
* The handling of stdout/stderr must be resilient across agent failover.  
Logging should not stop if the agent fails.
* Logs should be readable, presumably via the web UI, or via some other 
module-specific UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-4088) Modularize existing plain-file logging for executor/task logs

[Joseph Wu (JIRA)]

Joseph Wu created MESOS-4088:


 Summary: Modularize existing plain-file logging for executor/task 
logs
 Key: MESOS-4088
 URL: https://issues.apache.org/jira/browse/MESOS-4088
 Project: Mesos
  Issue Type: Task
  Components: modules
Reporter: Joseph Wu
Assignee: Joseph Wu


Once a module for executor/task output logging has been introduced, the default 
module will mirror the existing behavior.  Executor/task stdout/stderr is piped 
into files within the executor's sandbox directory.

The files are exposed in the web UI, via the {{/files}} endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-1807) Disallow executors with cpu only or memory only resources

[Vinod Kone (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-1807:
--
Labels:   (was: newbie)

yea, i think it's still blocked on those tickets. i'll remove the 'newbie' 
label to avoid confusion.

> Disallow executors with cpu only or memory only resources
> -
>
> Key: MESOS-1807
> URL: https://issues.apache.org/jira/browse/MESOS-1807
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Vinod Kone
> Attachments: Screenshot 2015-07-28 14.40.35.png
>
>
> Currently master allows executors to be launched with either only cpus or 
> only memory but we shouldn't allow that.
> This is because executor is an actual unix process that is launched by the 
> slave. If an executor doesn't specify cpus, what should do the cpu limits be 
> for that executor when there are no tasks running on it? If no cpu limits are 
> set then it might starve other executors/tasks on the slave violating 
> isolation guarantees. Same goes with memory. Moreover, the current 
> containerizer/isolator code will throw failures when using such an executor, 
> e.g., when the last task on the executor finishes and Containerizer::update() 
> is called with 0 cpus or 0 mem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-3946) Test for role management

[Neil Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15045749#comment-15045749
 ] 

Neil Conway commented on MESOS-3946:


FYI, https://reviews.apache.org/r/40995/ adds a few tests for role management 
behavior.

> Test for role management
> 
>
> Key: MESOS-3946
> URL: https://issues.apache.org/jira/browse/MESOS-3946
> Project: Mesos
>  Issue Type: Task
>Reporter: Yong Qiao Wang
>Assignee: Yong Qiao Wang
>
> Add test for role dynamic configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3792) flags.acls in /state.json response is not the flag value passed to Mesos master

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-3792:
---
Component/s: master

> flags.acls in /state.json response is not the flag value passed to Mesos 
> master
> ---
>
> Key: MESOS-3792
> URL: https://issues.apache.org/jira/browse/MESOS-3792
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Reporter: James Fisher
>Assignee: Jian Qiu
>
> Steps to reproduce: Start Mesos master with the `--acls` flag set to the 
> following value:
> {code}
> { "run_tasks": [ { "principals": { "values": ["foo", "bar"] }, "users": { 
> "values": ["alice"] } } ] }
> {code}
> Then make a request to {{http://mesosmaster:5050/state.json}} and extract the 
> value for key `flags.acls` from the JSON body of the response.
> Expected behavior: the value is the same JSON string passed on the 
> command-line.
> Actual behavior: the value is this string in some unknown syntax:
> {code}
> run_tasks {
>   principals {
> values: "foo"
> values: "bar"
>   }
>   users {
> values: "alice"
>   }
> }
> {code}
> I don't know what this is, but it's not an ACL expression according to the 
> documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)