[
https://issues.apache.org/jira/browse/HDFS-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384919#comment-16384919
]
Konstantin Shvachko commented on HDFS-12975:
--------------------------------------------
Also was thinking about the startup sequence. I think it wouldn't be right to
use a configuration variable to identify, which nodes are observers. NameNodes
can transition back and force in run-time, while the config file will not be up
to date with these changes. So we should stick to option (1) above that is
explicitly transition standbys to observers via an admin command.
> 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,
> HDFS-12975.002.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
