Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38623787
@CodingCat, the problem with that is that the StopDAGScheduler event will
get added to the queue, so it looks like the DAGScheduler can keep
processing more events while it's in it's bad state, until the
StopDAGScheduler event gets to the front of the queue?
On Tue, Mar 25, 2014 at 2:30 PM, Kay Ousterhout
<[email protected]>wrote:
> Also, Mark, you're the Akka expert here -- should we be catching this
> exception using Akka's supervisor mechanism (
> http://doc.akka.io/docs/akka/2.2.1/scala/fault-tolerance.html) rather
> than our own try/catch? It looks like that's the expected way to catch
> exceptions in an Akka actor?
>
>
> On Tue, Mar 25, 2014 at 2:27 PM, Mark Hamstra
<[email protected]>wrote:
>
>> Only if there is no rc2 :)
>>
>> --
>> Reply to this email directly or view it on
GitHub<https://github.com/apache/spark/pull/186#issuecomment-38623099>
>> .
>>
>
>
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
