[jira] [Assigned] (MESOS-1693) Enable builds for ARM
[ https://issues.apache.org/jira/browse/MESOS-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy St. Clair reassigned MESOS-1693: Assignee: Timothy St. Clair Enable builds for ARM - Key: MESOS-1693 URL: https://issues.apache.org/jira/browse/MESOS-1693 Project: Mesos Issue Type: Bug Components: build Affects Versions: 0.19.1 Reporter: Timothy St. Clair Assignee: Timothy St. Clair Enable building for ARM architecture. Current restriction support only x86 based architectures. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1692) Build error on gcc-4.4.
[
https://issues.apache.org/jira/browse/MESOS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093014#comment-14093014
]
Jie Yu commented on MESOS-1692:
---
The build is broken on gcc-4.6 as well:
https://builds.apache.org/job/mesos-reviewbot/1312/consoleFull
Build error on gcc-4.4.
---
Key: MESOS-1692
URL: https://issues.apache.org/jira/browse/MESOS-1692
Project: Mesos
Issue Type: Bug
Reporter: Jie Yu
Assignee: Benjamin Hindman
{noformat}
../../../mesos/src/master/http.cpp: In member function
'process::Futureprocess::http::Response
mesos::internal::master::Master::Http::shutdown(const
process::http::Request)':../../../mesos/src/master/http.cpp:677: error: no
matching function for call to 'process::Futurebool::th
en(process::Deferredprocess::Futureprocess::http::Response(bool))'
...
In file included from
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/functional:56,
from
../../../mesos/3rdparty/libprocess/3rdparty/stout/include/stout/lambda.hpp:28,
from
../../../mesos/3rdparty/libprocess/include/process/event.hpp:9,
from
../../../mesos/3rdparty/libprocess/include/process/process.hpp:11,
from
../../../mesos/3rdparty/libprocess/include/process/timeout.hpp:4,
from
../../../mesos/3rdparty/libprocess/include/process/timer.hpp:7,
from
../../../mesos/3rdparty/libprocess/include/process/future.hpp:25,
from
../../../mesos/3rdparty/libprocess/include/process/help.hpp:8,
from ../../../mesos/src/master/http.cpp:27:
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:
In static member function 'static _Res
std::tr1::_Function_handler_Res(_ArgTypes ...), _Functor::_M_invoke(const
std::tr1::_Any_data, _ArgTypes ...) [with _Res =
process::Futureprocess::http::Response, _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _ArgTypes = bool]':
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:2005:
instantiated from 'std::tr1::function_Res(_ArgTypes
...)::function(_Functor, typename __gnu_cxx::__enable_if(!
std::tr1::is_integral::value), std::tr1::function_Res(_ArgTypes
...)::_Useless::__type) [with _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _Res =
process::Futureprocess::http::Response, _ArgTypes = bool]'
../../../mesos/3rdparty/libprocess/include/process/defer.hpp:472:
instantiated from 'process::Deferredprocess::FutureX(A0)
process::defer(const process::UPID, const
std::tr1::functionprocess::FutureX(A0)) [with R =
process::http::Response, A0 = bool, F = void()]'
../../../mesos/src/master/http.cpp:677: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:1654:
error: conversion from 'void' to non-scalar type
'process::Futureprocess::http::Response' requested
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1316) Implement decent unit test coverage for the mesos-fetcher tool
[
https://issues.apache.org/jira/browse/MESOS-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lambert updated MESOS-1316:
-
Sprint: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3 (was: Q3 Sprint 1, Q3 Sprint
2)
Implement decent unit test coverage for the mesos-fetcher tool
--
Key: MESOS-1316
URL: https://issues.apache.org/jira/browse/MESOS-1316
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Tom Arnfeld
Assignee: Benjamin Hindman
There are current no tests that cover the {{mesos-fetcher}} tool itself, and
hence bugs like MESOS-1313 have accidentally slipped though.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1620) Reconciliation does not send back tasks pending validation / authorization.
[ https://issues.apache.org/jira/browse/MESOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1620: - Sprint: Q3 Sprint 2, Q3 Sprint 3 (was: Q3 Sprint 2) Reconciliation does not send back tasks pending validation / authorization. --- Key: MESOS-1620 URL: https://issues.apache.org/jira/browse/MESOS-1620 Project: Mesos Issue Type: Improvement Reporter: Benjamin Mahler Assignee: Benjamin Mahler Per Vinod's feedback on https://reviews.apache.org/r/23542/, we do not send back TASK_STAGING for those tasks that are pending in the Master (validation / authorization still in progress). For both implicit and explicit task reconciliation, the master could reply with TASK_STAGING for these tasks, as this provides additional information to the framework. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1527) Choose containerizer at runtime
[ https://issues.apache.org/jira/browse/MESOS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1527: - Sprint: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3 (was: Q3 Sprint 1, Q3 Sprint 2) Choose containerizer at runtime --- Key: MESOS-1527 URL: https://issues.apache.org/jira/browse/MESOS-1527 Project: Mesos Issue Type: Improvement Components: containerization Reporter: Jay Buffington Assignee: Benjamin Hindman Currently you have to choose the containerizer at mesos-slave start time via the --isolation option. I'd like to be able to specify the containerizer in the request to launch the job. This could be specified by a new Provider field in the ContainerInfo proto buf. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1567) Add logging of the user uid when receiving SIGTERM.
[ https://issues.apache.org/jira/browse/MESOS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambert updated MESOS-1567: - Sprint: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3 (was: Q3 Sprint 1, Q3 Sprint 2) Add logging of the user uid when receiving SIGTERM. --- Key: MESOS-1567 URL: https://issues.apache.org/jira/browse/MESOS-1567 Project: Mesos Issue Type: Improvement Components: master, slave Reporter: Benjamin Mahler Assignee: Alexandra Sava We currently do not log the user id when receiving a SIGTERM, this makes debugging a bit difficult. It's easy to get this information through sigaction. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1670) Build Failure on Mac OSX with undefined link
[ https://issues.apache.org/jira/browse/MESOS-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093033#comment-14093033 ] Thomas Rampelberg commented on MESOS-1670: -- This looks like it is a problem with the python library as well: ImportError: dlopen(~/.python-eggs/mesos.native-0.20.0-py2.7-macosx-10.9-x86_64.egg-tmp/mesos/native/_mesos.so, 2): Symbol not found: __ZN7cgroups9hierarchyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIc Referenced from: ~/.python-eggs/mesos.native-0.20.0-py2.7-macosx-10.9-x86_64.egg-tmp/mesos/native/_mesos.so Build Failure on Mac OSX with undefined link - Key: MESOS-1670 URL: https://issues.apache.org/jira/browse/MESOS-1670 Project: Mesos Issue Type: Bug Components: build Affects Versions: 0.20.0 Environment: Mac OSX Reporter: Ken Sipe Building from master after the latest commits. There is a linking error end with this output: ./mesos-tests Source directory: /Users/kensipe/projects/mesos/mesos Build directory: /Users/kensipe/projects/mesos/mesos/build dyld: lazy symbol binding failed: Symbol not found: __ZN7cgroups9hierarchyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIc Referenced from: /Users/kensipe/projects/mesos/mesos/build/src/.libs/libmesos-0.20.0.dylib Expected in: flat namespace dyld: Symbol not found: __ZN7cgroups9hierarchyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIc Referenced from: /Users/kensipe/projects/mesos/mesos/build/src/.libs/libmesos-0.20.0.dylib Expected in: flat namespace make[3]: *** [check-local] Trace/BPT trap: 5 make[2]: *** [check-am] Error 2 make[1]: *** [check] Error 2 debugging shows: echo __ZN7cgroups9hierarchyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIc|c++filt cgroups::hierarchy(std::__1::basic_stringchar, std::__1::char_traitschar, std::__1::allocatorchar const) and nm indicates that it is undefined: nm /Users/kensipe/projects/mesos/mesos/build/src/.libs/libmesos-0.20.0.dylib|grep __ZN7cgroups9hierarchyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIc U __ZN7cgroups9hierarchyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIc It appears that there is a #ifdef __linux directive missing around some cgroup code. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093056#comment-14093056 ] Timothy St. Clair commented on MESOS-1645: -- I would like to add https://issues.apache.org/jira/browse/MESOS-1071 and I'm hoping to get: https://issues.apache.org/jira/browse/MESOS-1693 https://issues.apache.org/jira/browse/MESOS-1195 0.20.0 Release -- Key: MESOS-1645 URL: https://issues.apache.org/jira/browse/MESOS-1645 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093065#comment-14093065 ] Jie Yu commented on MESOS-1645: --- [~tstclair] When do you think MESOS-1071 will be resolved? 0.20.0 Release -- Key: MESOS-1645 URL: https://issues.apache.org/jira/browse/MESOS-1645 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1425) LogZooKeeperTest.WriteRead test is flaky
[
https://issues.apache.org/jira/browse/MESOS-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Hamon updated MESOS-1425:
-
Sprint: Q3 Sprint 1, Q3 Sprint 2 (was: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint
3)
LogZooKeeperTest.WriteRead test is flaky
Key: MESOS-1425
URL: https://issues.apache.org/jira/browse/MESOS-1425
Project: Mesos
Issue Type: Bug
Components: test
Affects Versions: 0.19.0
Reporter: Vinod Kone
Assignee: Jie Yu
{code}
[ RUN ] LogZooKeeperTest.WriteRead
I0527 23:23:48.286031 1352 zookeeper_test_server.cpp:158] Started
ZooKeeperTestServer on port 39446
I0527 23:23:48.293916 1352 log_tests.cpp:1945] Using temporary directory
'/tmp/LogZooKeeperTest_WriteRead_Vyty8g'
I0527 23:23:48.296430 1352 leveldb.cpp:176] Opened db in 2.459713ms
I0527 23:23:48.296740 1352 leveldb.cpp:183] Compacted db in 286843ns
I0527 23:23:48.296761 1352 leveldb.cpp:198] Created db iterator in 3083ns
I0527 23:23:48.296772 1352 leveldb.cpp:204] Seeked to beginning of db in
4541ns
I0527 23:23:48.296777 1352 leveldb.cpp:273] Iterated through 0 keys in the
db in 87ns
I0527 23:23:48.296788 1352 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
I0527 23:23:48.297499 1383 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 505340ns
I0527 23:23:48.297513 1383 replica.cpp:320] Persisted replica status to
VOTING
I0527 23:23:48.299492 1352 leveldb.cpp:176] Opened db in 1.73582ms
I0527 23:23:48.299773 1352 leveldb.cpp:183] Compacted db in 263937ns
I0527 23:23:48.299793 1352 leveldb.cpp:198] Created db iterator in 7494ns
I0527 23:23:48.299806 1352 leveldb.cpp:204] Seeked to beginning of db in
235ns
I0527 23:23:48.299813 1352 leveldb.cpp:273] Iterated through 0 keys in the
db in 93ns
I0527 23:23:48.299821 1352 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
I0527 23:23:48.300503 1380 leveldb.cpp:306] Persisting metadata (8 bytes) to
leveldb took 492309ns
I0527 23:23:48.300516 1380 replica.cpp:320] Persisted replica status to
VOTING
I0527 23:23:48.302500 1352 leveldb.cpp:176] Opened db in 1.793829ms
I0527 23:23:48.303642 1352 leveldb.cpp:183] Compacted db in 1.123929ms
I0527 23:23:48.303669 1352 leveldb.cpp:198] Created db iterator in 5865ns
I0527 23:23:48.303689 1352 leveldb.cpp:204] Seeked to beginning of db in
8811ns
I0527 23:23:48.303705 1352 leveldb.cpp:273] Iterated through 1 keys in the
db in 9545ns
I0527 23:23:48.303715 1352 replica.cpp:741] Replica recovered with log
positions 0 - 0 with 1 holes and 0 unlearned
2014-05-27 23:23:48,303:1352(0x2b1173a29700):ZOO_INFO@log_env@712: Client
environment:zookeeper.version=zookeeper C client 3.4.5
2014-05-27 23:23:48,303:1352(0x2b1173a29700):ZOO_INFO@log_env@716: Client
environment:host.name=minerva
2014-05-27 23:23:48,303:1352(0x2b1173a29700):ZOO_INFO@log_env@723: Client
environment:os.name=Linux
2014-05-27 23:23:48,303:1352(0x2b1173a29700):ZOO_INFO@log_env@724: Client
environment:os.arch=3.2.0-57-generic
2014-05-27 23:23:48,303:1352(0x2b1173a29700):ZOO_INFO@log_env@725: Client
environment:os.version=#87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013
2014-05-27 23:23:48,303:1352(0x2b1173e2b700):ZOO_INFO@log_env@712: Client
environment:zookeeper.version=zookeeper C client 3.4.5
2014-05-27 23:23:48,304:1352(0x2b1173e2b700):ZOO_INFO@log_env@716: Client
environment:host.name=minerva
2014-05-27 23:23:48,304:1352(0x2b1173e2b700):ZOO_INFO@log_env@723: Client
environment:os.name=Linux
2014-05-27 23:23:48,304:1352(0x2b1173e2b700):ZOO_INFO@log_env@724: Client
environment:os.arch=3.2.0-57-generic
2014-05-27 23:23:48,304:1352(0x2b1173e2b700):ZOO_INFO@log_env@725: Client
environment:os.version=#87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013
2014-05-27 23:23:48,304:1352(0x2b1173a29700):ZOO_INFO@log_env@733: Client
environment:user.name=(null)
I0527 23:23:48.303988 1380 log.cpp:238] Attempting to join replica to
ZooKeeper group
2014-05-27 23:23:48,304:1352(0x2b1173e2b700):ZOO_INFO@log_env@733: Client
environment:user.name=(null)
2014-05-27 23:23:48,304:1352(0x2b1173a29700):ZOO_INFO@log_env@741: Client
environment:user.home=/home/jenkins
I0527 23:23:48.304198 1385 recover.cpp:425] Starting replica recovery
2014-05-27 23:23:48,304:1352(0x2b1173e2b700):ZOO_INFO@log_env@741: Client
environment:user.home=/home/jenkins
2014-05-27 23:23:48,304:1352(0x2b1173a29700):ZOO_INFO@log_env@753: Client
environment:user.dir=/tmp/LogZooKeeperTest_WriteRead_Vyty8g
2014-05-27 23:23:48,304:1352(0x2b1173a29700):ZOO_INFO@zookeeper_init@786:
Initiating client connection, host=127.0.0.1:39446 sessionTimeout=5000
watcher=0x2b11708e98d0 sessionId=0 sessionPasswd=null
context=0x2b118002f4e0 flags=0
[jira] [Updated] (MESOS-1316) Implement decent unit test coverage for the mesos-fetcher tool
[
https://issues.apache.org/jira/browse/MESOS-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Hamon updated MESOS-1316:
-
Sprint: Q3 Sprint 1, Q3 Sprint 2 (was: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint
3)
Implement decent unit test coverage for the mesos-fetcher tool
--
Key: MESOS-1316
URL: https://issues.apache.org/jira/browse/MESOS-1316
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Tom Arnfeld
Assignee: Benjamin Hindman
There are current no tests that cover the {{mesos-fetcher}} tool itself, and
hence bugs like MESOS-1313 have accidentally slipped though.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1518) Update Rate Limiting Design doc to reflect the latest changes
[ https://issues.apache.org/jira/browse/MESOS-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1518: - Sprint: Q2 Sprint 4, Q3 Sprint 3 (was: Q2 Sprint 4) Update Rate Limiting Design doc to reflect the latest changes - Key: MESOS-1518 URL: https://issues.apache.org/jira/browse/MESOS-1518 Project: Mesos Issue Type: Improvement Components: documentation Reporter: Yan Xu Assignee: Yan Xu - Usage - Design - Implementation Notes -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1219) Master should disallow frameworks that reconnect after failover timeout.
[ https://issues.apache.org/jira/browse/MESOS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1219: - Sprint: Q3 Sprint 1, Q3 Sprint 3 (was: Q3 Sprint 1) Master should disallow frameworks that reconnect after failover timeout. Key: MESOS-1219 URL: https://issues.apache.org/jira/browse/MESOS-1219 Project: Mesos Issue Type: Bug Components: master, webui Reporter: Robert Lacroix Assignee: Vinod Kone When a scheduler reconnects after the failover timeout has exceeded, the framework id is usually reused because the scheduler doesn't know that the timeout exceeded and it is actually handled as a new framework. The /framework/:framework_id route of the Web UI doesn't handle those cases very well because its key is reused. It only shows the terminated one. Would it make sense to ignore the provided framework id when a scheduler reconnects to a terminated framework and generate a new id to make sure it's unique? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1645: - Sprint: Q3 Sprint 3 0.20.0 Release -- Key: MESOS-1645 URL: https://issues.apache.org/jira/browse/MESOS-1645 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1466) Race between executor exited event and launch task can cause overcommit of resources
[ https://issues.apache.org/jira/browse/MESOS-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1466: - Sprint: Q3 Sprint 3 Race between executor exited event and launch task can cause overcommit of resources Key: MESOS-1466 URL: https://issues.apache.org/jira/browse/MESOS-1466 Project: Mesos Issue Type: Bug Components: allocation, master Reporter: Vinod Kone Assignee: Benjamin Mahler Labels: reliability The following sequence of events can cause an overcommit -- Launch task is called for a task whose executor is already running -- Executor's resources are not accounted for on the master -- Executor exits and the event is enqueued behind launch tasks on the master -- Master sends the task to the slave which needs to commit for resources for task and the (new) executor. -- Master processes the executor exited event and re-offers the executor's resources causing an overcommit of resources. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1466) Race between executor exited event and launch task can cause overcommit of resources
[ https://issues.apache.org/jira/browse/MESOS-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1466: - Assignee: Benjamin Mahler (was: Dominic Hamon) Race between executor exited event and launch task can cause overcommit of resources Key: MESOS-1466 URL: https://issues.apache.org/jira/browse/MESOS-1466 Project: Mesos Issue Type: Bug Components: allocation, master Reporter: Vinod Kone Assignee: Benjamin Mahler Labels: reliability The following sequence of events can cause an overcommit -- Launch task is called for a task whose executor is already running -- Executor's resources are not accounted for on the master -- Executor exits and the event is enqueued behind launch tasks on the master -- Master sends the task to the slave which needs to commit for resources for task and the (new) executor. -- Master processes the executor exited event and re-offers the executor's resources causing an overcommit of resources. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1466) Race between executor exited event and launch task can cause overcommit of resources
[ https://issues.apache.org/jira/browse/MESOS-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1466: - Shepherd: Vinod Kone Race between executor exited event and launch task can cause overcommit of resources Key: MESOS-1466 URL: https://issues.apache.org/jira/browse/MESOS-1466 Project: Mesos Issue Type: Bug Components: allocation, master Reporter: Vinod Kone Labels: reliability The following sequence of events can cause an overcommit -- Launch task is called for a task whose executor is already running -- Executor's resources are not accounted for on the master -- Executor exits and the event is enqueued behind launch tasks on the master -- Master sends the task to the slave which needs to commit for resources for task and the (new) executor. -- Master processes the executor exited event and re-offers the executor's resources causing an overcommit of resources. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1629) GLOG Initialized twice if the Framework Scheduler also uses GLOG
[
https://issues.apache.org/jira/browse/MESOS-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Hamon updated MESOS-1629:
-
Sprint: Q3 Sprint 3
GLOG Initialized twice if the Framework Scheduler also uses GLOG
Key: MESOS-1629
URL: https://issues.apache.org/jira/browse/MESOS-1629
Project: Mesos
Issue Type: Bug
Reporter: Zuyu Zhang
Assignee: Vinod Kone
{noformat}
Could not create logging file: No such file or directory
COULD NOT CREATE A LOGGINGFILE 20140722-205220.31450!F0722 20:52:20.494424
31450 utilities.cc:317] Check failed: !IsGoogleLoggingInitialized() You
called InitGoogleLogging() twice!
*** Check failure stack trace: ***
@ 0x4399ce google::LogMessage::Fail()
@ 0x43991d google::LogMessage::SendToLog()
@ 0x43932e google::LogMessage::Flush()
@ 0x43c0e5 google::LogMessageFatal::~LogMessageFatal()
@ 0x44089f
google::glog_internal_namespace_::InitGoogleLoggingUtilities()
@ 0x43c409 google::InitGoogleLogging()
@ 0x7f0bdd43b55c mesos::internal::logging::initialize()
@ 0x7f0bdcf9564d mesos::scheduler::MesosProcess::MesosProcess()
@ 0x7f0bdcf92de0 mesos::scheduler::Mesos::Mesos()
@ 0x421483 heron::mesos::Scheduler::Scheduler()
@ 0x4305dc main
@ 0x7f0bd97159c4 __libc_start_main
@ 0x420869 (unknown)
Aborted
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1683) Create user doc for framework rate limiting feature
[ https://issues.apache.org/jira/browse/MESOS-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1683: - Sprint: Q3 Sprint 3 Create user doc for framework rate limiting feature --- Key: MESOS-1683 URL: https://issues.apache.org/jira/browse/MESOS-1683 Project: Mesos Issue Type: Task Components: documentation Affects Versions: 0.20.0 Reporter: Yan Xu Assignee: Yan Xu Create a Markdown doc under /docs -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1592) Introduce the notion of an inverse resource offer.
[ https://issues.apache.org/jira/browse/MESOS-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1592: - Sprint: Q3 Sprint 3 Introduce the notion of an inverse resource offer. -- Key: MESOS-1592 URL: https://issues.apache.org/jira/browse/MESOS-1592 Project: Mesos Issue Type: Task Components: allocation Reporter: Benjamin Mahler Assignee: Benjamin Mahler An inverse resource offer means that Mesos is requesting resources back from the framework, possibly within some time interval. This can be leveraged initially to provide more automated cluster maintenance, by offering schedulers the opportunity to move tasks to compensate for planned maintenance. Operators can set a time limit on how long to wait for schedulers to relocate tasks before the tasks are forcibly terminated. Inverse resource offers have many other potential uses, as it opens the opportunity for the allocator to attempt to move tasks in the cluster through the co-operation of the framework, possibly providing better over-subscription, fairness, etc. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1219) Master should disallow frameworks that reconnect after failover timeout.
[ https://issues.apache.org/jira/browse/MESOS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1219: - Story Points: 2 Master should disallow frameworks that reconnect after failover timeout. Key: MESOS-1219 URL: https://issues.apache.org/jira/browse/MESOS-1219 Project: Mesos Issue Type: Bug Components: master, webui Reporter: Robert Lacroix Assignee: Vinod Kone When a scheduler reconnects after the failover timeout has exceeded, the framework id is usually reused because the scheduler doesn't know that the timeout exceeded and it is actually handled as a new framework. The /framework/:framework_id route of the Web UI doesn't handle those cases very well because its key is reused. It only shows the terminated one. Would it make sense to ignore the provided framework id when a scheduler reconnects to a terminated framework and generate a new id to make sure it's unique? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1645: - Story Points: 1 0.20.0 Release -- Key: MESOS-1645 URL: https://issues.apache.org/jira/browse/MESOS-1645 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1592) Design inverse resource offer support
[ https://issues.apache.org/jira/browse/MESOS-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1592: - Story Points: 5 Summary: Design inverse resource offer support (was: Introduce the notion of an inverse resource offer.) Added 5 as story point to capture uncertainty. Also renamed to more specifically describe the work here. Please add more tasks once the design is understood or if work needs to be done to complete the design. Design inverse resource offer support - Key: MESOS-1592 URL: https://issues.apache.org/jira/browse/MESOS-1592 Project: Mesos Issue Type: Task Components: allocation Reporter: Benjamin Mahler Assignee: Benjamin Mahler An inverse resource offer means that Mesos is requesting resources back from the framework, possibly within some time interval. This can be leveraged initially to provide more automated cluster maintenance, by offering schedulers the opportunity to move tasks to compensate for planned maintenance. Operators can set a time limit on how long to wait for schedulers to relocate tasks before the tasks are forcibly terminated. Inverse resource offers have many other potential uses, as it opens the opportunity for the allocator to attempt to move tasks in the cluster through the co-operation of the framework, possibly providing better over-subscription, fairness, etc. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093298#comment-14093298 ] Jie Yu edited comment on MESOS-1645 at 8/11/14 9:12 PM: [~tstclair]] Do you want all reviews in MESOS-1071 to go in 0.20.0, or just part of them. For example, do you want pip and wheel stuff to go in? was (Author: jieyu): [~t.st.clair] Do you want all reviews in MESOS-1071 to go in 0.20.0, or just part of them. For example, do you want pip and wheel stuff to go in? 0.20.0 Release -- Key: MESOS-1645 URL: https://issues.apache.org/jira/browse/MESOS-1645 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1692) Build error on gcc-4.4.
[
https://issues.apache.org/jira/browse/MESOS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093302#comment-14093302
]
Brenden Matthews commented on MESOS-1692:
-
I bumped into this today as well. Is anyone working on a patch? Should I fix
it?
Build error on gcc-4.4.
---
Key: MESOS-1692
URL: https://issues.apache.org/jira/browse/MESOS-1692
Project: Mesos
Issue Type: Bug
Reporter: Jie Yu
Assignee: Benjamin Hindman
{noformat}
../../../mesos/src/master/http.cpp: In member function
'process::Futureprocess::http::Response
mesos::internal::master::Master::Http::shutdown(const
process::http::Request)':../../../mesos/src/master/http.cpp:677: error: no
matching function for call to 'process::Futurebool::th
en(process::Deferredprocess::Futureprocess::http::Response(bool))'
...
In file included from
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/functional:56,
from
../../../mesos/3rdparty/libprocess/3rdparty/stout/include/stout/lambda.hpp:28,
from
../../../mesos/3rdparty/libprocess/include/process/event.hpp:9,
from
../../../mesos/3rdparty/libprocess/include/process/process.hpp:11,
from
../../../mesos/3rdparty/libprocess/include/process/timeout.hpp:4,
from
../../../mesos/3rdparty/libprocess/include/process/timer.hpp:7,
from
../../../mesos/3rdparty/libprocess/include/process/future.hpp:25,
from
../../../mesos/3rdparty/libprocess/include/process/help.hpp:8,
from ../../../mesos/src/master/http.cpp:27:
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:
In static member function 'static _Res
std::tr1::_Function_handler_Res(_ArgTypes ...), _Functor::_M_invoke(const
std::tr1::_Any_data, _ArgTypes ...) [with _Res =
process::Futureprocess::http::Response, _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _ArgTypes = bool]':
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:2005:
instantiated from 'std::tr1::function_Res(_ArgTypes
...)::function(_Functor, typename __gnu_cxx::__enable_if(!
std::tr1::is_integral::value), std::tr1::function_Res(_ArgTypes
...)::_Useless::__type) [with _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _Res =
process::Futureprocess::http::Response, _ArgTypes = bool]'
../../../mesos/3rdparty/libprocess/include/process/defer.hpp:472:
instantiated from 'process::Deferredprocess::FutureX(A0)
process::defer(const process::UPID, const
std::tr1::functionprocess::FutureX(A0)) [with R =
process::http::Response, A0 = bool, F = void()]'
../../../mesos/src/master/http.cpp:677: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:1654:
error: conversion from 'void' to non-scalar type
'process::Futureprocess::http::Response' requested
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1692) Build error on gcc-4.4.
[
https://issues.apache.org/jira/browse/MESOS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman updated MESOS-1692:
Affects Version/s: 0.20.0
Build error on gcc-4.4.
---
Key: MESOS-1692
URL: https://issues.apache.org/jira/browse/MESOS-1692
Project: Mesos
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Jie Yu
Assignee: Benjamin Hindman
{noformat}
../../../mesos/src/master/http.cpp: In member function
'process::Futureprocess::http::Response
mesos::internal::master::Master::Http::shutdown(const
process::http::Request)':../../../mesos/src/master/http.cpp:677: error: no
matching function for call to 'process::Futurebool::th
en(process::Deferredprocess::Futureprocess::http::Response(bool))'
...
In file included from
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/functional:56,
from
../../../mesos/3rdparty/libprocess/3rdparty/stout/include/stout/lambda.hpp:28,
from
../../../mesos/3rdparty/libprocess/include/process/event.hpp:9,
from
../../../mesos/3rdparty/libprocess/include/process/process.hpp:11,
from
../../../mesos/3rdparty/libprocess/include/process/timeout.hpp:4,
from
../../../mesos/3rdparty/libprocess/include/process/timer.hpp:7,
from
../../../mesos/3rdparty/libprocess/include/process/future.hpp:25,
from
../../../mesos/3rdparty/libprocess/include/process/help.hpp:8,
from ../../../mesos/src/master/http.cpp:27:
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:
In static member function 'static _Res
std::tr1::_Function_handler_Res(_ArgTypes ...), _Functor::_M_invoke(const
std::tr1::_Any_data, _ArgTypes ...) [with _Res =
process::Futureprocess::http::Response, _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _ArgTypes = bool]':
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:2005:
instantiated from 'std::tr1::function_Res(_ArgTypes
...)::function(_Functor, typename __gnu_cxx::__enable_if(!
std::tr1::is_integral::value), std::tr1::function_Res(_ArgTypes
...)::_Useless::__type) [with _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _Res =
process::Futureprocess::http::Response, _ArgTypes = bool]'
../../../mesos/3rdparty/libprocess/include/process/defer.hpp:472:
instantiated from 'process::Deferredprocess::FutureX(A0)
process::defer(const process::UPID, const
std::tr1::functionprocess::FutureX(A0)) [with R =
process::http::Response, A0 = bool, F = void()]'
../../../mesos/src/master/http.cpp:677: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:1654:
error: conversion from 'void' to non-scalar type
'process::Futureprocess::http::Response' requested
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-1692) Build error on gcc-4.4.
[
https://issues.apache.org/jira/browse/MESOS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093310#comment-14093310
]
Brenden Matthews commented on MESOS-1692:
-
Thanks for clarifying that! I'm happy to test the patch.
Build error on gcc-4.4.
---
Key: MESOS-1692
URL: https://issues.apache.org/jira/browse/MESOS-1692
Project: Mesos
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Jie Yu
Assignee: Benjamin Hindman
{noformat}
../../../mesos/src/master/http.cpp: In member function
'process::Futureprocess::http::Response
mesos::internal::master::Master::Http::shutdown(const
process::http::Request)':../../../mesos/src/master/http.cpp:677: error: no
matching function for call to 'process::Futurebool::th
en(process::Deferredprocess::Futureprocess::http::Response(bool))'
...
In file included from
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/functional:56,
from
../../../mesos/3rdparty/libprocess/3rdparty/stout/include/stout/lambda.hpp:28,
from
../../../mesos/3rdparty/libprocess/include/process/event.hpp:9,
from
../../../mesos/3rdparty/libprocess/include/process/process.hpp:11,
from
../../../mesos/3rdparty/libprocess/include/process/timeout.hpp:4,
from
../../../mesos/3rdparty/libprocess/include/process/timer.hpp:7,
from
../../../mesos/3rdparty/libprocess/include/process/future.hpp:25,
from
../../../mesos/3rdparty/libprocess/include/process/help.hpp:8,
from ../../../mesos/src/master/http.cpp:27:
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:
In static member function 'static _Res
std::tr1::_Function_handler_Res(_ArgTypes ...), _Functor::_M_invoke(const
std::tr1::_Any_data, _ArgTypes ...) [with _Res =
process::Futureprocess::http::Response, _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _ArgTypes = bool]':
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:2005:
instantiated from 'std::tr1::function_Res(_ArgTypes
...)::function(_Functor, typename __gnu_cxx::__enable_if(!
std::tr1::is_integral::value), std::tr1::function_Res(_ArgTypes
...)::_Useless::__type) [with _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _Res =
process::Futureprocess::http::Response, _ArgTypes = bool]'
../../../mesos/3rdparty/libprocess/include/process/defer.hpp:472:
instantiated from 'process::Deferredprocess::FutureX(A0)
process::defer(const process::UPID, const
std::tr1::functionprocess::FutureX(A0)) [with R =
process::http::Response, A0 = bool, F = void()]'
../../../mesos/src/master/http.cpp:677: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:1654:
error: conversion from 'void' to non-scalar type
'process::Futureprocess::http::Response' requested
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-1692) Build error on gcc-4.4.
[
https://issues.apache.org/jira/browse/MESOS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093314#comment-14093314
]
Benjamin Hindman commented on MESOS-1692:
-
Please test [~brenden]!
Build error on gcc-4.4.
---
Key: MESOS-1692
URL: https://issues.apache.org/jira/browse/MESOS-1692
Project: Mesos
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Jie Yu
Assignee: Benjamin Hindman
{noformat}
../../../mesos/src/master/http.cpp: In member function
'process::Futureprocess::http::Response
mesos::internal::master::Master::Http::shutdown(const
process::http::Request)':../../../mesos/src/master/http.cpp:677: error: no
matching function for call to 'process::Futurebool::th
en(process::Deferredprocess::Futureprocess::http::Response(bool))'
...
In file included from
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/functional:56,
from
../../../mesos/3rdparty/libprocess/3rdparty/stout/include/stout/lambda.hpp:28,
from
../../../mesos/3rdparty/libprocess/include/process/event.hpp:9,
from
../../../mesos/3rdparty/libprocess/include/process/process.hpp:11,
from
../../../mesos/3rdparty/libprocess/include/process/timeout.hpp:4,
from
../../../mesos/3rdparty/libprocess/include/process/timer.hpp:7,
from
../../../mesos/3rdparty/libprocess/include/process/future.hpp:25,
from
../../../mesos/3rdparty/libprocess/include/process/help.hpp:8,
from ../../../mesos/src/master/http.cpp:27:
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:
In static member function 'static _Res
std::tr1::_Function_handler_Res(_ArgTypes ...), _Functor::_M_invoke(const
std::tr1::_Any_data, _ArgTypes ...) [with _Res =
process::Futureprocess::http::Response, _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _ArgTypes = bool]':
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:2005:
instantiated from 'std::tr1::function_Res(_ArgTypes
...)::function(_Functor, typename __gnu_cxx::__enable_if(!
std::tr1::is_integral::value), std::tr1::function_Res(_ArgTypes
...)::_Useless::__type) [with _Functor = std::tr1::_Bindvoid
(*(process::UPID,
std::tr1::functionprocess::Futureprocess::http::Response(bool),
std::tr1::_Placeholder1))(const process::UPID, const
std::tr1::functionvoid(bool), bool), _Res =
process::Futureprocess::http::Response, _ArgTypes = bool]'
../../../mesos/3rdparty/libprocess/include/process/defer.hpp:472:
instantiated from 'process::Deferredprocess::FutureX(A0)
process::defer(const process::UPID, const
std::tr1::functionprocess::FutureX(A0)) [with R =
process::http::Response, A0 = bool, F = void()]'
../../../mesos/src/master/http.cpp:677: instantiated from here
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/functional:1654:
error: conversion from 'void' to non-scalar type
'process::Futureprocess::http::Response' requested
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (MESOS-1032) Apache Mesos logo is missing trademark
[ https://issues.apache.org/jira/browse/MESOS-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1032: --- Attachment: mesos_final_white.png mesos_final_dkblue.png mesos_final_white.ai mesos_final_dkblue.ai Adding illustrator and png files of logo with TM notice. These were previously shared with the dev list, but never added to this JIRA issue Apache Mesos logo is missing trademark --- Key: MESOS-1032 URL: https://issues.apache.org/jira/browse/MESOS-1032 Project: Mesos Issue Type: Bug Reporter: Jake Farrell Assignee: Dave Lester Attachments: mesos_draft.png, mesos_final_dkblue.ai, mesos_final_dkblue.png, mesos_final_white.ai, mesos_final_white.png The Apache Mesos logo needs to have a tm added to it http://www.apache.org/foundation/marks/pmcs.html#graphics -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1478) Replace Master/Slave terminology
[ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093357#comment-14093357 ] Ben Rosengart commented on MESOS-1478: -- +1 for this change, and +∞ to all involved for being so nice about it. Replace Master/Slave terminology Key: MESOS-1478 URL: https://issues.apache.org/jira/browse/MESOS-1478 Project: Mesos Issue Type: Improvement Reporter: Clark Breyman Priority: Minor Inspired by the comments on this PR: https://github.com/django/django/pull/2692 TL;DR - Computers sharing work should be a good thing. Using the language of human bondage and suffering is inappropriate in this context. It also has the potential to alienate users and community members. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1147) Result and Try should return const for messages rather than copy
[ https://issues.apache.org/jira/browse/MESOS-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon updated MESOS-1147: - Sprint: Q3 Sprint 3 Result and Try should return const for messages rather than copy -- Key: MESOS-1147 URL: https://issues.apache.org/jira/browse/MESOS-1147 Project: Mesos Issue Type: Task Components: stout, technical debt Reporter: Dominic Hamon Assignee: Dominic Hamon Coping the message on return is wasteful - a const reference should be returned instead. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1645) 0.20.0 Release
[ https://issues.apache.org/jira/browse/MESOS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-1645: -- Story Points: 5 (was: 1) 0.20.0 Release -- Key: MESOS-1645 URL: https://issues.apache.org/jira/browse/MESOS-1645 Project: Mesos Issue Type: Task Reporter: Jie Yu Assignee: Jie Yu I would like to volunteer to be the release manager for 0.20.0, which will be releasing the following major features: - Docker support in Mesos (MESOS-1524) - Container level network monitoring for mesos containerizer (MESOS-1228). - Authorization (MESOS-1342) - Framework rate limiting (MESOS-1306) I would like to track blockers for the release on this ticket. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1694) Future::failure should return a const string
Dominic Hamon created MESOS-1694: Summary: Future::failure should return a const string Key: MESOS-1694 URL: https://issues.apache.org/jira/browse/MESOS-1694 Project: Mesos Issue Type: Task Components: technical debt Reporter: Dominic Hamon Priority: Minor -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1620) Reconciliation does not send back tasks pending validation / authorization.
[ https://issues.apache.org/jira/browse/MESOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093505#comment-14093505 ] Benjamin Mahler commented on MESOS-1620: Review chain for this one, did some cleanups along the way: https://reviews.apache.org/r/24582/ https://reviews.apache.org/r/24583/ https://reviews.apache.org/r/24576/ https://reviews.apache.org/r/24515/ https://reviews.apache.org/r/24516/ Reconciliation does not send back tasks pending validation / authorization. --- Key: MESOS-1620 URL: https://issues.apache.org/jira/browse/MESOS-1620 Project: Mesos Issue Type: Improvement Reporter: Benjamin Mahler Assignee: Benjamin Mahler Per Vinod's feedback on https://reviews.apache.org/r/23542/, we do not send back TASK_STAGING for those tasks that are pending in the Master (validation / authorization still in progress). For both implicit and explicit task reconciliation, the master could reply with TASK_STAGING for these tasks, as this provides additional information to the framework. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-292) Remove unnecessary includes of headers to improve compile times
[ https://issues.apache.org/jira/browse/MESOS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon resolved MESOS-292. - Resolution: Fixed Fix Version/s: 0.20.0 commit c9d1c4cd1be097e3bcee63855847da272c43bc68 Author: Isabel Jimenez cont...@isabeljimenez.com Commit: Benjamin Hindman benjamin.hind...@gmail.com Removed unnecessary includes and inline definitions. Dominic's Hamon review request: https://reviews.apache.org/r/18295 mergeable to today's master version, this is a lightened version to make review easier. Note I see an improvements of ~7.5% of the compile time. Review: https://reviews.apache.org/r/23745 Remove unnecessary includes of headers to improve compile times --- Key: MESOS-292 URL: https://issues.apache.org/jira/browse/MESOS-292 Project: Mesos Issue Type: Improvement Components: technical debt Reporter: Vinod Kone Assignee: Dominic Hamon Priority: Minor Fix For: 0.20.0 We should be exploiting the compiler firewall (Pimpl) idiom to reduce the compile times. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1620) Reconciliation does not send back tasks pending validation / authorization.
[ https://issues.apache.org/jira/browse/MESOS-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-1620: --- Shepherd: Vinod Kone (was: Dominic Hamon) Reconciliation does not send back tasks pending validation / authorization. --- Key: MESOS-1620 URL: https://issues.apache.org/jira/browse/MESOS-1620 Project: Mesos Issue Type: Improvement Reporter: Benjamin Mahler Assignee: Benjamin Mahler Per Vinod's feedback on https://reviews.apache.org/r/23542/, we do not send back TASK_STAGING for those tasks that are pending in the Master (validation / authorization still in progress). For both implicit and explicit task reconciliation, the master could reply with TASK_STAGING for these tasks, as this provides additional information to the framework. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (MESOS-1694) Future::failure should return a const string
[ https://issues.apache.org/jira/browse/MESOS-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Hamon reassigned MESOS-1694: Assignee: Dominic Hamon Future::failure should return a const string - Key: MESOS-1694 URL: https://issues.apache.org/jira/browse/MESOS-1694 Project: Mesos Issue Type: Task Components: technical debt Reporter: Dominic Hamon Assignee: Dominic Hamon Priority: Minor Labels: newbie -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (MESOS-1691) Improvement of Docker image location failure message
[ https://issues.apache.org/jira/browse/MESOS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Chen reassigned MESOS-1691: --- Assignee: Timothy Chen Improvement of Docker image location failure message Key: MESOS-1691 URL: https://issues.apache.org/jira/browse/MESOS-1691 Project: Mesos Issue Type: Improvement Reporter: Julien Eid Assignee: Timothy Chen Priority: Trivial I know this is pretty minor but is a bit confusing for people new to using the Docker containerizer. The error message for a malformed Docker image URL is No docker image found, skipping launch, which was pretty confusing to me as I had kept specifying the image and it was saying there was none instead of telling me the string was wrong. I think it would be better if it was Incorrect Docker image specified, Docker image URL's must start with docker:/// I wouldn't mind working on this issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
