[jira] [Created] (SPARK-20426) OneForOneStreamManager occupies too much memory.

["jin xing (JIRA)" <ji...@apache.org>]

jin xing created SPARK-20426:
--------------------------------

             Summary: OneForOneStreamManager occupies too much memory.
                 Key: SPARK-20426
                 URL: https://issues.apache.org/jira/browse/SPARK-20426
             Project: Spark
          Issue Type: Bug
          Components: Shuffle
    Affects Versions: 2.1.0
            Reporter: jin xing


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*. 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 metadata(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