Return-Path: X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 609C3178DF for ; Fri, 26 Sep 2014 07:08:34 +0000 (UTC) Received: (qmail 70167 invoked by uid 500); 26 Sep 2014 07:08:34 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 70131 invoked by uid 500); 26 Sep 2014 07:08:33 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 70112 invoked by uid 99); 26 Sep 2014 07:08:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Sep 2014 07:08:33 +0000 Date: Fri, 26 Sep 2014 07:08:33 +0000 (UTC) From: "Chengwei Yang (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-1746) clear TaskStatus data to avoid OOM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148860#comment-14148860 ] Chengwei Yang commented on MESOS-1746: -------------------------------------- can anyone help to review? > clear TaskStatus data to avoid OOM > ---------------------------------- > > Key: MESOS-1746 > URL: https://issues.apache.org/jira/browse/MESOS-1746 > Project: Mesos > Issue Type: Bug > Environment: mesos-0.19.0 > Reporter: Chengwei Yang > Assignee: Chengwei Yang > > Spark on mesos may use TaskStatus to transfer computed result between worker and scheduler, the source code like below (spark 1.0.2) > {code} > val serializedResult = { > if (serializedDirectResult.limit >= execBackend.akkaFrameSize() - > AkkaUtils.reservedSizeBytes) { > logInfo("Storing result for " + taskId + " in local BlockManager") > val blockId = TaskResultBlockId(taskId) > env.blockManager.putBytes( > blockId, serializedDirectResult, StorageLevel.MEMORY_AND_DISK_SER) > ser.serialize(new IndirectTaskResult[Any](blockId)) > } else { > logInfo("Sending result for " + taskId + " directly to driver") > serializedDirectResult > } > } > {code} > And In our test environment, we enlarge akkaFrameSize to 128MB from default value (10MB) and this cause our mesos-master process will be OOM in tens of minutes when running spark tasks in fine-grained mode. > As you can see, even changed akkaFrameSize back to default value (10MB), it's very likely to make mesos-master OOM too, however more slower. > So I think it's good to delete data from TaskStatus since this is only designed to on-top framework and we don't interested in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)