[
https://issues.apache.org/jira/browse/HDFS-17958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103721#comment-18103721
]
ASF GitHub Bot commented on HDFS-17958:
---------------------------------------
arshadmohammad opened a new pull request, #8671:
URL: https://github.com/apache/hadoop/pull/8671
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Please read the jira description
### How was this patch tested?
Have written UT
### For code changes:
- [ ] Does the title of this PR start 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? *Note:
Automated CI
testing doesn't cover all cases so manual testing with cloud storage
is still
required.*
- [ ] 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?
### AI Tooling
If an AI tool was used:
- [ ] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [ ] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> Support NameNode-scoped configuration for dfs.namenode.observer.enabled
> -----------------------------------------------------------------------
>
> Key: HDFS-17958
> URL: https://issues.apache.org/jira/browse/HDFS-17958
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.4.1
> Reporter: Mohammad Arshad
> Assignee: Mohammad Arshad
> Priority: Major
>
> *Background:*
> I installed the HDFS service with HA enabled, using two NameNodes—one active
> and one standby. All HDFS components currently share the same set of
> configuration files.
> I now want to add a third NameNode as an Observer NameNode. However, I've run
> into a limitation:
> * If I set dfs.namenode.observer.enabled=true to designate the third
> NameNode as an observer, all the NameNodes start as observers, since they
> share the same configuration.
> * Alternatively, I can start the third NameNode as an observer by passing
> the -observer flag at startup. But since I'm using a cluster installation
> tool, this approach requires me to separately track which NameNode is the
> observer and apply that information during startup—which adds unwanted
> complexity.
>
>
> *Proposed Change:*
> Similar to other existing NameNode-scoped configurations, I propose adding a
> NameNode-scoped configuration:
> dfs.namenode.observer.enabled.<nameserviceId>.<namenodeId>
> This configuration would be set only in the configuration of the specific
> NameNode we want to designate as the observer.
> As a result, only that NameNode would start as an Observer NameNode, leaving
> the other NameNodes unaffected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
