[
https://issues.apache.org/jira/browse/HADOOP-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840372#comment-17840372
]
ASF GitHub Bot commented on HADOOP-19156:
-----------------------------------------
liubin101 opened a new pull request, #6767:
URL: https://github.com/apache/hadoop/pull/6767
### Description of PR
Currently, the Zookeeper-based state stores of RM, YARN Federation, and HDFS
Federation use the same ZK address config `hadoop.zk.address`. But in our
production environment, we hope that different services can use different ZKs
to avoid mutual influence.
This jira adds separate ZK address configs for each service.
### How was this patch tested?
unit test
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> ZooKeeper based state stores use different ZK address configs
> -------------------------------------------------------------
>
> Key: HADOOP-19156
> URL: https://issues.apache.org/jira/browse/HADOOP-19156
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: liu bin
> Priority: Major
>
> Currently, the Zookeeper-based state stores of RM, YARN Federation, and HDFS
> Federation use the same ZK address config `{{{}hadoop.zk.address`{}}}. But in
> our production environment, we hope that different services can use different
> ZKs to avoid mutual influence.
> This jira adds separate ZK address configs for each service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
