Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.0.2, 1.1.0
-
None
Description
The ApplicationClient sets yarnJobManager to None until it has connected to a newly elected JobManager. A shutdown message to the application master is discarded while the ApplicationClient tries to reconnect. The ApplicationClient should retry to shutdown the cluster when it is connected to the new leader. It may also time out (which currently is always the case).
Attachments
Issue Links
- depends upon
-
FLINK-3667 Generalize client<->cluster communication
- Closed