[
https://issues.apache.org/jira/browse/SPARK-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226506#comment-14226506
]
Marcelo Vanzin commented on SPARK-4584:
---------------------------------------
[~sowen] that was going to be my suggestion. For 1.2, I'll just remote the
security manager and declare "use System.exit() at your own risk" - the
behavior should then be the same as 1.1. Post 1.2, we could add some new
exception (e.g. {{SparkAppException}}) that users can throw if they want the
runtime to exit with a specific error code. But even that I don't think is
strictly necessary - just a nice to have.
BTW, we've tried to extend the security manager so that all operations except
for {{checkExit}} are no-ops, but even that doesn't help.
> 2x Performance regression for Spark-on-YARN
> -------------------------------------------
>
> Key: SPARK-4584
> URL: https://issues.apache.org/jira/browse/SPARK-4584
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.2.0
> Reporter: Nishkam Ravi
> Assignee: Marcelo Vanzin
> Priority: Blocker
>
> Significant performance regression observed for Spark-on-YARN (upto 2x) after
> 1.2 rebase. The offending commit is: 70e824f750aa8ed446eec104ba158b0503ba58a9
> from Oct 7th. Problem can be reproduced with JavaWordCount against a large
> enough input dataset in YARN cluster mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
