Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
Currently we have ZooKeeper based store implementations for multiple state stores like RM, YARN Federation, HDFS router-based federation, RM queue configs etc. This jira proposes to unify the curator based ZK communication to eliminate redundancies.
Attachments
Attachments
Issue Links
- breaks
-
TEZ-3874 NPE in TezClientUtils when "yarn.resourcemanager.zk-address" is present in Configuration
-
- Closed
-
- is depended upon by
-
HDFS-10631 Federation State Store ZooKeeper implementation
-
- Resolved
-
-
YARN-6840 Implement zookeeper based store for scheduler configuration updates
-
- Resolved
-
-
YARN-6900 ZooKeeper based implementation of the FederationStateStore
-
- Resolved
-
- is related to
-
HADOOP-15093 Deprecation of yarn.resourcemanager.zk-address is undocumented
-
- Resolved
-
- relates to
-
HADOOP-14773 Extend ZKCuratorManager API for more reusability
-
- Resolved
-
-
YARN-8405 RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773
-
- Resolved
-
-
HDFS-13533 RBF: Configuration for RBF in namenode/datanode
-
- Open
-
-
YARN-7053 Move curator transaction support to ZKCuratorManager
-
- Resolved
-
-
YARN-8568 Replace the deprecated zk-address property in the HA config example in ResourceManagerHA.md
-
- Resolved
-
-
YARN-10246 Enable YARN Router to have a dedicated Zookeeper
-
- Patch Available
-