[
https://issues.apache.org/jira/browse/HDFS-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066795#comment-17066795
]
Ayush Saxena commented on HDFS-12733:
-------------------------------------
Thanx [~hexiaoqiao] for the patch, Seems fine. Just a doubt, earlier if the
configuration was set blank, it would have taken default path, isn't it?\{{–>
L1603 FSN}}
Now, if it is set blank, there would be no local edits. Well I don't think we
have any other way without introducing a new config. I don't think people would
be relying on the blank string to get resolved to default. Until and unless I
am not missing any critical stuff. This should be fine..
> 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
