Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.2.0
-
None
Description
It's better to let the NodeManager get down rather than take a port retry when `spark.shuffle.service.port` has been conflicted during starting the Spark Yarn Shuffle Server, because the retry mechanism will make the inconsistency of shuffle port and also make client fail to find the port.