[
https://issues.apache.org/jira/browse/HDFS-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066297#comment-17066297
]
Íñigo Goiri commented on HDFS-12733:
------------------------------------
I guess [^HDFS-12733.008.patch] assumes that one would set
DFS_NAMENODE_EDITS_DIR_KEY to null to disable the local edits?
I think is fine; can we document this behavior in the HA QJM md file mentioning
that if we want to disable the local edits (assuming that the shared ones are
enoug), one needs to set dfs.namenode.edits.dir to blank?
In addition, in FSNameSystem let's add a log message when
{{!noSharedEditDirs.isEmpty()}} saying that the local edits are disabled and
that it will rely on the shared ones.
BTW, is there a need to check that at least there is one edits location
specified? I think that may already be implicit.
> Option to disable to namenode local edits
> -----------------------------------------
>
> Key: HDFS-12733
> URL: https://issues.apache.org/jira/browse/HDFS-12733
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode, performance
> Reporter: Brahma Reddy Battula
> Assignee: Xiaoqiao He
> Priority: Major
> Attachments: HDFS-12733-001.patch, HDFS-12733-002.patch,
> HDFS-12733-003.patch, HDFS-12733.004.patch, HDFS-12733.005.patch,
> HDFS-12733.006.patch, HDFS-12733.007.patch, HDFS-12733.008.patch
>
>
> As of now, Edits will be written in local and shared locations which will be
> redundant and local edits never used in HA setup.
> Disabling local edits gives little performance improvement.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
