[
https://issues.apache.org/jira/browse/HDFS-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856603#comment-16856603
]
Ayush Saxena commented on HDFS-12733:
-------------------------------------
{quote}IMO, having one config to have this shouldn't be problem, we can mention
in release notes about the new config.
{quote}
I pose agreement to this, I agree there are too many configurations but still
we can allow this at least.
bq. I agree that we should do not load dfs.namenode.edits.dir anymore in HA
mode if we has config dfs.namenode.shared.edits.dir item.
Well doing this way wouldn't be an imcompatible change. We don't have a very
genuine use case for the local edits, but someone may have. As I said in HA
there isn't much use of local edits in general case, but I guess that can still
has some critical information, that can help in scenarios such as Disaster
Recovery or may be used in times Shared Storage Crash as even Brahma mentioned.
IMO, the present approach having a configuration seems better.
> 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: Brahma Reddy Battula
> Priority: Major
> Attachments: HDFS-12733-001.patch, HDFS-12733-002.patch,
> HDFS-12733-003.patch, HDFS-12733.004.patch, HDFS-12733.005.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
