mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-3794) Master should not store arbitrarily sized data in ExecutorInfo.
Date Wed, 02 Nov 2016 11:50:58 GMT

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

Alexander Rukletsov updated MESOS-3794:
---------------------------------------
    Summary: Master should not store arbitrarily sized data in ExecutorInfo.  (was: Master
should not store arbitrarily sized data in ExecutorInfo)

> Master should not store arbitrarily sized data in ExecutorInfo.
> ---------------------------------------------------------------
>
>                 Key: MESOS-3794
>                 URL: https://issues.apache.org/jira/browse/MESOS-3794
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>            Reporter: Joseph Wu
>            Priority: Critical
>              Labels: mesosphere
>
> From a comment in [MESOS-3771]:
> Master should not be storing the {{data}} fields from {{ExecutorInfo}}.  We currently
[store the entire object|https://github.com/apache/mesos/blob/master/src/master/master.hpp#L262-L271],
which means master would be at high risk of OOM-ing if a bunch of executors were started with
big {{data}} blobs.
> * Master should scrub out unneeded bloat from {{ExecutorInfo}} before storing it.
> * We can use an alternate internal object, like we do for {{TaskInfo}} vs {{Task}}; see
[this|https://github.com/apache/mesos/blob/master/src/messages/messages.proto#L39-L41].



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

Mime
View raw message