You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2018/01/20 01:47:00 UTC

[jira] [Updated] (MESOS-3794) Master should not store arbitrarily sized data in ExecutorInfo.

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

Gilbert Song updated MESOS-3794:
--------------------------------
      Priority: Major  (was: Critical)
    Issue Type: Improvement  (was: Bug)

Updated this to `Improvement` as type and `Major` as priority. Please change it back if necessary.

> 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: Improvement
>          Components: master
>            Reporter: Joseph Wu
>            Priority: Major
>              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
(v7.6.3#76005)