Affects Version/s: 0.23.1
Fix Version/s: None
It doesn't seem that Yarn components, for example the ResourceManager or NodeManager, do build/package version checking before trying to communicate with each other.
The objective of this ticket is to support the following requirements / use cases:
- New versions can be marked incompatible with old versions, and services should be prevented from communicating with each other in such case. This will avoid non-deterministic behavior/problems resulting from incompatible components trying to communicate with each other.
- Permitting a policy for running different - but compatible - versions on the same cluster (for example, in a rolling upgrade scenario). See
HDFS-2983for the corresponding HDFS implementation.
There are no Sub-Tasks for this issue.