Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/1358#issuecomment-59724452
@mateiz - @KashiErez and I went on a different route. The killer issue was
that there is a System.exit(1) in BlockManagerMasterActor which was a huge
robustness issue for us. @taboola we are running some pretty large clusters
(process many tera bytes of data / day) which do real time calculations and are
mission critical. So - we fixed the issue and it's been running successfully in
our production for a while now.
I opened a new ticket - https://issues.apache.org/jira/browse/SPARK-4006
And a pull request - https://github.com/apache/spark/pull/2854
What do you think about our fix?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
