[
https://issues.apache.org/jira/browse/HDFS-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067442#comment-17067442
]
Xiaoqiao He commented on HDFS-12733:
------------------------------------
Thanks [~elgoiri],[~ayushtkn] for your great feedback. v008 does rely on set
`dfs.namenode.edits.dir` to blank to disable local edit. Yes, we need more
information to clear this changes. It is true that their actions are different,
IMO it is feasible to unify it that we disable local edits if config blank and
tell our end user explicitly. Of course, patch v008 is not a complete story
currently. I would like to update the patch if no objection. Thanks again
[~elgoiri],[~ayushtkn] for your suggestions.
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
