You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@spark.apache.org by twinkle sachdeva <tw...@gmail.com> on 2014/09/01 13:27:52 UTC

Has anybody faced SPARK-2604 issue regarding Application hang state

Hi,

Has anyone else also experienced
https://issues.apache.org/jira/browse/SPARK-2604?

It is an edge case scenario of mis configuration, where the executor memory
asked is same as the maximum allowed memory by yarn. In such situation,
application stays in hang state, and the reason is not logged in verbose
manner to be debugged easily.

As per the fix, it gets detected and corresponding reasons are logged
before failing the application.

I will prefer the fix to be in open source code version, please share your
thoughts.

Thanks,