[
https://issues.apache.org/jira/browse/HDFS-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379865#comment-16379865
]
Chao Sun commented on HDFS-12975:
---------------------------------
Thanks Konstantin. Let me strip out the state part of the patch and leave the
rest for separate Jiras.
{quote}
May be we should have a separate doc or I can update the design. The main thing
is that we should configure NNs altogether the same way as it is currently done
{quote}
Yes, I think it would be useful to add a section for the configuration changes.
Currently I'm using a separate config:
{{dfs.ha.observer.namenode.<clustername>}}, to separate observer from
active/standby. I think this is similar to the choices #2 you mentioned.
{quote}
HAUtil.getConfForOtherNodes() the refactoring (otherNn -> otherNameNodes)
should go into trunk. Better avoid renaming even though the original choice of
the variable name is bad.
{quote}
Will create a Jira to address this.
> Changes to the NameNode to support reads from standby
> -----------------------------------------------------
>
> Key: HDFS-12975
> URL: https://issues.apache.org/jira/browse/HDFS-12975
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Konstantin Shvachko
> Assignee: Chao Sun
> Priority: Major
> Attachments: HDFS-12975.000.patch, HDFS-12975.001.patch
>
>
> In order to support reads from standby NameNode needs changes to add Observer
> role, turn off checkpointing and such.
--
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
