Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
4.0.0
-
None
-
None
-
None
Description
When ZKRegistryBase detects new ZK nodes it maintains path based cache and host based cache. The host based cached already handles multiple instances running in same host. But even if single instance is removed all instances belonging to the host are removed.
Another issue is that, if single host has multiple instances it returns a Set with no ordering. Ideally, we want the newest instance to be top of the set (use TreeSet maybe?).
Attachments
Attachments
Issue Links
- relates to
-
TEZ-4179 [Kubernetes] Extend NodeId in tez to support unique worker identity
- Resolved