[
https://issues.apache.org/jira/browse/HDFS-12733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855738#comment-16855738
]
He Xiaoqiao commented on HDFS-12733:
------------------------------------
Thanks [~brahmareddy] for your suggestion.
{quote}The problem might be when Shared storage crashed we can't do
"INITIALIZESHAREDEDITS" incase user dn't want to use this( as might not care
about performance,he might care reliability). By considering I have given the
patch.{quote}
[^HDFS-12733-003.patch] is a good solution and it is compatible with current
implement with one config.
For the case you mentioned above, IIRC, NameNode only read edit from shared
storage and replay in HA mode, even shared storage crashed. Unless we update
logic about {{FSEditLog#initSharedJournalsForRead}} in HA mode. anyway, I
confused about set only local storage in HA mode. Please correct me if
something wrong. Thanks again.
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
