Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.1.2
-
None
-
None
-
Reviewed
Description
In Kubernetes, the a node may go down and then come back later with a different IP address. YARN clients which are already running will be unable to rediscover the node after it comes back up due to caching the original IP address. This is problematic for cases such as Spark HA on Kubernetes, as the node containing the resource manager may go down and come back up, meaning existing node managers must then also be restarted.
Attachments
Issue Links
- causes
-
YARN-10803 [JDK 11] TestRMFailoverProxyProvider and TestNoHaRMFailoverProxyProvider fails by ClassCastException
- Resolved
- depends upon
-
HADOOP-16938 Make non-HA proxy providers pluggable
- Resolved
- links to