spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saisai Shao (JIRA)" <>
Subject [jira] [Commented] (SPARK-20426) OneForOneStreamManager occupies too much memory.
Date Fri, 21 Apr 2017 09:54:04 GMT


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:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message