Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7A454200C69 for ; Fri, 21 Apr 2017 11:54:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 78FF8160BA2; Fri, 21 Apr 2017 09:54:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C32CE160B97 for ; Fri, 21 Apr 2017 11:54:09 +0200 (CEST) Received: (qmail 59738 invoked by uid 500); 21 Apr 2017 09:54:07 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 59729 invoked by uid 99); 21 Apr 2017 09:54:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2017 09:54:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E1BB4C1862 for ; Fri, 21 Apr 2017 09:54:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id nx_HNcpvh8cv for ; Fri, 21 Apr 2017 09:54:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 59B455FD9A for ; Fri, 21 Apr 2017 09:54:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CF311E0D75 for ; Fri, 21 Apr 2017 09:54:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5B91D21B5B for ; Fri, 21 Apr 2017 09:54:04 +0000 (UTC) Date: Fri, 21 Apr 2017 09:54:04 +0000 (UTC) From: "Saisai Shao (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-20426) OneForOneStreamManager occupies too much memory. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 21 Apr 2017 09:54:10 -0000 [ https://issues.apache.org/jira/browse/SPARK-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978415#comment-15978415 ] Saisai Shao commented on SPARK-20426: ------------------------------------- Currently I don't have a clear fix about this issue, I'm not sure if your proposal is a best choice, or there're other choices like lazy initialization of {{FileSegmentManagedBuffer}}. You could go ahead if you have a concrete plan. > OneForOneStreamManager occupies too much memory. > ------------------------------------------------ > > Key: SPARK-20426 > URL: https://issues.apache.org/jira/browse/SPARK-20426 > Project: Spark > Issue Type: Improvement > Components: Shuffle > Affects Versions: 2.1.0 > Reporter: jin xing > Attachments: screenshot-1.png, screenshot-2.png > > > Spark jobs are running on yarn cluster in my warehouse. We enabled the external shuffle service(*--conf spark.shuffle.service.enabled=true*). Recently NodeManager runs OOM now and then. Dumping heap memory, we find that *OneFroOneStreamManager*'s footprint is huge. NodeManager is configured with 5G heap memory. While *OneForOneManager* costs 2.5G and there are 5503233 *FileSegmentManagedBuffer* objects. Is there any suggestions to avoid this other than just keep increasing NodeManager's memory? Is it possible to stop *registerStream* in OneForOneStreamManager? Thus we don't need to cache so many metadatas(i.e. StreamState). -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org