Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/19396
Thanks @jerryshao for the comment.
> IMO I think it might be better to throw an exception instead of not
starting shuffle service. Since user want to use external shuffle explicitly,
letting user to know the issues and fix the issue would be better.
I considered this before creating PR but the Node Manager continues to run
when spark shuffle service gets BindException, thought to make the behavior
inline with NM spark shuffle.
Please let me know if you think to make the Worker to go down on external
shuffle service start failure I can update this PR.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
