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

[ https://issues.apache.org/jira/browse/MESOS-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-2353: --- Sprint: Twitter Mesos Q1 Sprint 5 (was: Twitter Mesos Q1 Sprint 5, Twitter Mesos Q1 Sprint 6)

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

[ https://issues.apache.org/jira/browse/MESOS-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-2353: --- Story Points: 5 (was: 1) > Improve performance of the master's state.json endpoint for large

[jira] [Commented] (MESOS-2581) Document tips, best practices, guidelines for doing code reviews.

[ https://issues.apache.org/jira/browse/MESOS-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486417#comment-14486417 ] Benjamin Mahler commented on MESOS-2581: Core of the change is here: https://revie

[jira] [Updated] (MESOS-2581) Document tips, best practices, guidelines for doing code reviews.

[ https://issues.apache.org/jira/browse/MESOS-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-2581: --- Shepherd: Vinod Kone > Document tips, best practices, guidelines for doing code reviews. > ---

[jira] [Updated] (MESOS-2485) Add ability to distinguish slave removals metrics by reason.

[ https://issues.apache.org/jira/browse/MESOS-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-2485: --- Shepherd: Vinod Kone > Add ability to distinguish slave removals metrics by reason. >

[jira] [Commented] (MESOS-2485) Add ability to distinguish slave removals metrics by reason.

[ https://issues.apache.org/jira/browse/MESOS-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493431#comment-14493431 ] Benjamin Mahler commented on MESOS-2485: https://reviews.apache.org/r/33152/ https

[jira] [Commented] (MESOS-2191) Add ContainerId to the TaskStatus message

[ https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495123#comment-14495123 ] Benjamin Mahler commented on MESOS-2191: How does that work for custom executors r

[jira] [Commented] (MESOS-2620) Implement a mechanism which allows access control of endpoints

[ https://issues.apache.org/jira/browse/MESOS-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496583#comment-14496583 ] Benjamin Mahler commented on MESOS-2620: Hm, accessing the doc requires requesting

[jira] [Comment Edited] (MESOS-2144) Segmentation Fault in ExamplesTest.LowLevelSchedulerPthread

[ https://issues.apache.org/jira/browse/MESOS-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498789#comment-14498789 ] Benjamin Mahler edited comment on MESOS-2144 at 4/17/15 12:00 AM: --

[jira] [Assigned] (MESOS-2144) Segmentation Fault in ExamplesTest.LowLevelSchedulerPthread

[ https://issues.apache.org/jira/browse/MESOS-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-2144: -- Assignee: (was: Yan Xu) > Segmentation Fault in ExamplesTest.LowLevelSchedulerPthre

[jira] [Commented] (MESOS-2373) DRFSorter needs to distinguish resources from different slaves.

[ https://issues.apache.org/jira/browse/MESOS-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500907#comment-14500907 ] Benjamin Mahler commented on MESOS-2373: Committed these two: {noformat} commit a

[jira] [Commented] (MESOS-2636) Segfault in inline Try getIP(const std::string& hostname, int family)

[ https://issues.apache.org/jira/browse/MESOS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500938#comment-14500938 ] Benjamin Mahler commented on MESOS-2636: FYI [~evelinad] > Segfault in inline Try

[jira] [Commented] (MESOS-2498) Change Http Request log level to VLOG(1)

[ https://issues.apache.org/jira/browse/MESOS-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505843#comment-14505843 ] Benjamin Mahler commented on MESOS-2498: {quote}It doesn't even specify the source

[jira] [Comment Edited] (MESOS-1303) ExamplesTest.{TestFramework, NoExecutorFramework} flaky

[ https://issues.apache.org/jira/browse/MESOS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505927#comment-14505927 ] Benjamin Mahler edited comment on MESOS-1303 at 4/21/15 10:33 PM: --

[jira] [Resolved] (MESOS-2524) Mesos-containerizer not linked from main documentation page.

[ https://issues.apache.org/jira/browse/MESOS-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler resolved MESOS-2524. Resolution: Fixed {noformat} commit 4289616e1059bfab28555ba30356f37c257ba72d Author: James P

[jira] [Created] (MESOS-2643) Python scheduler driver disables implicit acknowledgments by default.

Benjamin Mahler created MESOS-2643: -- Summary: Python scheduler driver disables implicit acknowledgments by default. Key: MESOS-2643 URL: https://issues.apache.org/jira/browse/MESOS-2643 Project: Meso

[jira] [Assigned] (MESOS-2643) Python scheduler driver disables implicit acknowledgments by default.

[ https://issues.apache.org/jira/browse/MESOS-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-2643: -- Assignee: Benjamin Mahler > Python scheduler driver disables implicit acknowledgments b

[jira] [Commented] (MESOS-2643) Python scheduler driver disables implicit acknowledgments by default.

[ https://issues.apache.org/jira/browse/MESOS-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507992#comment-14507992 ] Benjamin Mahler commented on MESOS-2643: https://reviews.apache.org/r/33452/ > Py

[jira] [Updated] (MESOS-2643) Python scheduler driver disables implicit acknowledgments by default.

[ https://issues.apache.org/jira/browse/MESOS-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-2643: --- Fix Version/s: 0.22.1 > Python scheduler driver disables implicit acknowledgments by default.

[jira] [Updated] (MESOS-1721) Prevent overcommit of the slave for ports and ephemeral ports.

[ https://issues.apache.org/jira/browse/MESOS-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-1721: --- Assignee: (was: Benjamin Mahler) > Prevent overcommit of the slave for ports and ephemeral

[jira] [Updated] (MESOS-2308) Task reconciliation API should support data partitioning

[ https://issues.apache.org/jira/browse/MESOS-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-2308: --- Assignee: (was: Benjamin Mahler) > Task reconciliation API should support data partitionin

[jira] [Commented] (MESOS-2668) mesos-slave process enters failed state with "A slave (or child process) is still running, please check the process(es) '{ ... }' listed in /sys/fs/cgroup/cpu,cpuacct/m

[ https://issues.apache.org/jira/browse/MESOS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516122#comment-14516122 ] Benjamin Mahler commented on MESOS-2668: Linked in related tickets. cc [~jieyu] /

[jira] [Commented] (MESOS-2659) update pthread and python autoconf macros

[ https://issues.apache.org/jira/browse/MESOS-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516134#comment-14516134 ] Benjamin Mahler commented on MESOS-2659: Great, can you post them on ReviewBoard?

[jira] [Commented] (MESOS-2668) mesos-slave process enters failed state with "A slave (or child process) is still running, please check the process(es) '{ ... }' listed in /sys/fs/cgroup/cpu,cpuacct/m

[ https://issues.apache.org/jira/browse/MESOS-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516193#comment-14516193 ] Benjamin Mahler commented on MESOS-2668: [~tnachen] is it expected for the slave t

[jira] [Resolved] (MESOS-2679) Slave asked to shut down by master because 'health check timed out'

[ https://issues.apache.org/jira/browse/MESOS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler resolved MESOS-2679. Resolution: Not A Problem The slave needs to be run under a process which will restart it if

[jira] [Closed] (MESOS-2679) Slave asked to shut down by master because 'health check timed out'

[ https://issues.apache.org/jira/browse/MESOS-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler closed MESOS-2679. -- > Slave asked to shut down by master because 'health check timed out' >

[jira] [Commented] (MESOS-7828) Current approach to parse protobuf enum from JSON does not support upgrades

[ https://issues.apache.org/jira/browse/MESOS-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107853#comment-16107853 ] Benjamin Mahler commented on MESOS-7828: [~qianzhang] do you know how the protobuf

[jira] [Updated] (MESOS-7099) Quota can be exceeded due to coarse-grained offer technique.

[ https://issues.apache.org/jira/browse/MESOS-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7099: --- Labels: multitenancy (was: ) > Quota can be exceeded due to coarse-grained offer technique. >

[jira] [Updated] (MESOS-3338) Dynamic reservations are not counted as used resources in the master

[ https://issues.apache.org/jira/browse/MESOS-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-3338: --- Labels: mesosphere multitenancy persistent-volumes (was: mesosphere persistent-volumes) > Dy

[jira] [Updated] (MESOS-7258) Provide scheduler calls to subscribe to additional roles and unsubscribe from roles.

[ https://issues.apache.org/jira/browse/MESOS-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7258: --- Component/s: multitenancy > Provide scheduler calls to subscribe to additional roles and unsub

[jira] [Updated] (MESOS-7258) Provide scheduler calls to subscribe to additional roles and unsubscribe from roles.

[ https://issues.apache.org/jira/browse/MESOS-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7258: --- Component/s: (was: multitenancy) > Provide scheduler calls to subscribe to additional role

[jira] [Updated] (MESOS-7258) Provide scheduler calls to subscribe to additional roles and unsubscribe from roles.

[ https://issues.apache.org/jira/browse/MESOS-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7258: --- Labels: multitenancy (was: ) > Provide scheduler calls to subscribe to additional roles and u

[jira] [Commented] (MESOS-4941) Support update existing quota.

[ https://issues.apache.org/jira/browse/MESOS-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107934#comment-16107934 ] Benjamin Mahler commented on MESOS-4941: [~alexr] [~zhitao] are you guys still wor

[jira] [Updated] (MESOS-7402) Quota is over-allocated when used with hierarchical roles.

[ https://issues.apache.org/jira/browse/MESOS-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7402: --- Summary: Quota is over-allocated when used with hierarchical roles. (was: Allocated quota of

[jira] [Updated] (MESOS-7402) Quota is over-allocated when used with hierarchical roles.

[ https://issues.apache.org/jira/browse/MESOS-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7402: --- Priority: Critical (was: Blocker) Downgrading this to not be a 1.4 blocker, will call out thi

[jira] [Updated] (MESOS-7739) RegisterSlaveValidationTest.DropInvalidReregistration is flaky

[ https://issues.apache.org/jira/browse/MESOS-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7739: --- Description: Observed this on ASF CI. Seems a bit different from MESOS-7441. {code} [ RUN

[jira] [Updated] (MESOS-7739) RegisterSlaveValidationTest.DropInvalidReregistration is flaky

[ https://issues.apache.org/jira/browse/MESOS-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7739: --- Description: Observed this on ASF CI. Seems a bit different from MESOS-7441. {code} [ RUN

[jira] [Updated] (MESOS-7798) Improve libprocess message passing performance

[ https://issues.apache.org/jira/browse/MESOS-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7798: --- Sprint: Mesosphere Sprint 60 > Improve libprocess message passing performance > --

[jira] [Commented] (MESOS-6656) Nested containers can become unkillable

[ https://issues.apache.org/jira/browse/MESOS-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113839#comment-16113839 ] Benjamin Mahler commented on MESOS-6656: Bug filed here: MESOS-7858 > Nested cont

[jira] [Commented] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114988#comment-16114988 ] Benjamin Mahler commented on MESOS-7783: The bug occurs as follows: (1) Two (or m

[jira] [Assigned] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-7783: -- Assignee: Benjamin Mahler > Framework might not receive status update when a just launc

[jira] [Created] (MESOS-7863) Agent may drop pending kill task status updates.

Benjamin Mahler created MESOS-7863: -- Summary: Agent may drop pending kill task status updates. Key: MESOS-7863 URL: https://issues.apache.org/jira/browse/MESOS-7863 Project: Mesos Issue Type

[jira] [Assigned] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-7863: -- Assignee: Benjamin Mahler > Agent may drop pending kill task status updates. >

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Sprint: Mesosphere Sprint 60 > Agent may drop pending kill task status updates. >

[jira] [Updated] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7783: --- Target Version/s: 1.2.3, 1.3.2, 1.4.0 Fix Version/s: (was: 1.2.3)

[jira] [Updated] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7783: --- Fix Version/s: 1.4.0 1.3.2 1.2.3 > Framework might not r

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Target Version/s: 1.2.3, 1.3.2, 1.4.0 > Agent may drop pending kill task status updates. > ---

[jira] [Created] (MESOS-7865) Agent may process a kill task and still launch the task.

Benjamin Mahler created MESOS-7865: -- Summary: Agent may process a kill task and still launch the task. Key: MESOS-7865 URL: https://issues.apache.org/jira/browse/MESOS-7865 Project: Mesos Is

[jira] [Commented] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117569#comment-16117569 ] Benjamin Mahler commented on MESOS-7744: Thanks for reporting this and including t

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2 Priority: Critical (was: Minor) > Mesos Age

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0 (was: 1.1.3, 1.2.3, 1.3.2) > Mesos Agent Sends T

[jira] [Assigned] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-7744: -- Assignee: Benjamin Mahler > Mesos Agent Sends TASK_KILL status update to Master, and st

[jira] [Commented] (MESOS-920) Set GLOG_drop_log_memory=false in environment prior to logging initialization.

[ https://issues.apache.org/jira/browse/MESOS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117765#comment-16117765 ] Benjamin Mahler commented on MESOS-920: --- Looks like a fix was upstreamed, possibly ma

[jira] [Commented] (MESOS-7868) Support virtual filesystem in `Files` interface

[ https://issues.apache.org/jira/browse/MESOS-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118811#comment-16118811 ] Benjamin Mahler commented on MESOS-7868: [~zhitao] can you file a ticket to expose

[jira] [Updated] (MESOS-7747) Improve metrics around active subscribers.

[ https://issues.apache.org/jira/browse/MESOS-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7747: --- Labels: mesosphere metrics observability (was: mesosphere metrics reliability) > Improve met

[jira] [Updated] (MESOS-7815) Add gauge for master event processing time

[ https://issues.apache.org/jira/browse/MESOS-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7815: --- Labels: mesosphere metrics observability (was: mesosphere metrics reliability) > Add gauge f

[jira] [Updated] (MESOS-1719) Master should persist active frameworks information

[ https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-1719: --- Labels: mesosphere reliability (was: mesosphere) > Master should persist active frameworks in

[jira] [Created] (MESOS-7890) Agent's notion of "completed" frameworks is actually "idle" frameworks.

Benjamin Mahler created MESOS-7890: -- Summary: Agent's notion of "completed" frameworks is actually "idle" frameworks. Key: MESOS-7890 URL: https://issues.apache.org/jira/browse/MESOS-7890 Project: Me

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Sprint: Mesosphere Sprint 61 https://reviews.apache.org/r/61639/ > Agent may process a kill t

[jira] [Comment Edited] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115227#comment-16115227 ] Benjamin Mahler edited comment on MESOS-7863 at 8/15/17 7:07 AM: ---

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Story Points: 5 > Agent may drop pending kill task status updates. > -

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Story Points: 3 > Agent may process a kill task and still launch the task. > -

[jira] [Commented] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129236#comment-16129236 ] Benjamin Mahler commented on MESOS-7744: [~karya] [~alexr] any reason to drop the

[jira] [Comment Edited] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129236#comment-16129236 ] Benjamin Mahler edited comment on MESOS-7744 at 8/16/17 6:41 PM: ---

[jira] [Commented] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129261#comment-16129261 ] Benjamin Mahler commented on MESOS-7744: Ok, synced with [~alexr], looks like this

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Priority: Critical (was: Major) > Agent may process a kill task and still launch the task. >

[jira] [Updated] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7783: --- Priority: Blocker (was: Critical) > Framework might not receive status update when a just lau

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Priority: Blocker (was: Critical) > Agent may drop pending kill task status updates. > --

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Priority: Blocker (was: Critical) > Mesos Agent Sends TASK_KILL status update to Master, and

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Priority: Blocker (was: Critical) > Agent may process a kill task and still launch the task.

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0 (was: 1.2.3, 1.3.2, 1.4.0) > Agent may drop pend

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0 > Agent may process a kill task and still launch

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0, 1.5.0 (was: 1.2.3, 1.3.2, 1.4.0, 1.5.0) > Meso

[jira] [Updated] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7783: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0 (was: 1.2.3, 1.3.2, 1.4.0) > Framework might not

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Target Version/s: 1.2.3, 1.3.2, 1.4.0, 1.5.0 (was: 1.2.3, 1.3.2, 1.5.0, 1.4.1) > Mesos Agent

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Target Version/s: 1.1.3, 1.2.3, 1.3.2, 1.4.0 (was: 1.1.3, 1.2.3, 1.3.2, 1.4.0, 1.5.0) > Meso

[jira] [Updated] (MESOS-7513) Expose the container sandbox path to users via the API.

[ https://issues.apache.org/jira/browse/MESOS-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7513: --- Description: Currently, only the agent exposes the executor sandbox via a {{directory}} field

[jira] [Commented] (MESOS-7513) Expose the container sandbox path to users via the API.

[ https://issues.apache.org/jira/browse/MESOS-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129288#comment-16129288 ] Benjamin Mahler commented on MESOS-7513: [~zhitao] that's an option, after discuss

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Priority: Critical (was: Blocker) > Agent may process a kill task and still launch the task.

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Priority: Critical (was: Blocker) > Agent may drop pending kill task status updates. > --

[jira] [Updated] (MESOS-7744) Mesos Agent Sends TASK_KILL status update to Master, and still launches task

[ https://issues.apache.org/jira/browse/MESOS-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7744: --- Priority: Critical (was: Blocker) > Mesos Agent Sends TASK_KILL status update to Master, and

[jira] [Updated] (MESOS-7783) Framework might not receive status update when a just launched task is killed immediately

[ https://issues.apache.org/jira/browse/MESOS-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7783: --- Priority: Critical (was: Blocker) > Framework might not receive status update when a just lau

[jira] [Commented] (MESOS-6918) Prometheus exporter endpoints for metrics

[ https://issues.apache.org/jira/browse/MESOS-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136119#comment-16136119 ] Benjamin Mahler commented on MESOS-6918: [~jpe...@apache.org] [~xujyan] ideally yo

[jira] [Created] (MESOS-7911) Non-checkpointing framework's tasks should not be marked LOST when agent disconnects.

Benjamin Mahler created MESOS-7911: -- Summary: Non-checkpointing framework's tasks should not be marked LOST when agent disconnects. Key: MESOS-7911 URL: https://issues.apache.org/jira/browse/MESOS-7911

[jira] [Commented] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139261#comment-16139261 ] Benjamin Mahler commented on MESOS-7865: {noformat} commit 0b9c3dedb04e9bf2c3d1f16

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Fix Version/s: 1.1.3 > Agent may process a kill task and still launch the task. >

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Fix Version/s: 1.2.3 > Agent may process a kill task and still launch the task. >

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Fix Version/s: 1.3.2 > Agent may process a kill task and still launch the task. >

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Fix Version/s: 1.4.1 > Agent may process a kill task and still launch the task. >

[jira] [Commented] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139345#comment-16139345 ] Benjamin Mahler commented on MESOS-7865: [~karya] marking this fixed in 1.4.1 sinc

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Fix Version/s: 1.4.1 > Agent may drop pending kill task status updates. >

[jira] [Commented] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139377#comment-16139377 ] Benjamin Mahler commented on MESOS-7863: [~karya] marking this fixed in 1.4.1 sinc

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Fix Version/s: 1.3.2 > Agent may drop pending kill task status updates. >

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Fix Version/s: 1.2.3 > Agent may drop pending kill task status updates. >

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Fix Version/s: 1.1.3 > Agent may drop pending kill task status updates. >

[jira] [Updated] (MESOS-7865) Agent may process a kill task and still launch the task.

[ https://issues.apache.org/jira/browse/MESOS-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7865: --- Fix Version/s: (was: 1.5.0) > Agent may process a kill task and still launch the task. > -

[jira] [Updated] (MESOS-7863) Agent may drop pending kill task status updates.

[ https://issues.apache.org/jira/browse/MESOS-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7863: --- Fix Version/s: (was: 1.5.0) > Agent may drop pending kill task status updates. > -

[jira] [Updated] (MESOS-7921) process::EventQueue sometimes crashes

[ https://issues.apache.org/jira/browse/MESOS-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7921: --- Description: The following segfault is found on [ASF|https://builds.apache.org/job/Mesos-Buil

[jira] [Assigned] (MESOS-7912) Master WebUI not working in Chrome

[ https://issues.apache.org/jira/browse/MESOS-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-7912: -- Assignee: Alastair Montgomery > Master WebUI not working in Chrome > --

[jira] [Updated] (MESOS-7912) Master WebUI not working in Chrome.

[ https://issues.apache.org/jira/browse/MESOS-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler updated MESOS-7912: --- Summary: Master WebUI not working in Chrome. (was: Master WebUI not working in Chrome) > Mas

<    1   2   3   4   5   6   7   8   9   10   >