Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156603725
> Besides, still I think there's a race condition between querying loss
reason and process completed containers,
That's true. It's probably unlikely that it would be hit (since the
"executor disconnects, ask for loss reason" path is much quicker than the "nm
sees process has died, nm notifies rm, spark am wakes up from sleep and sends
heartbeat to rm and sees container has exited" path), But better be safe.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
