[
https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027179#comment-14027179
]
Konstantin Shvachko edited comment on HDFS-6469 at 6/10/14 11:04 PM:
---------------------------------------------------------------------
Sorry hit the submit button too early. Will repost shortly.
was (Author: shv):
h4. > Coordinated reads
The motivation for a configurable design based on file names is to make
coordinated reads available to other applications without changing them.
An alternative is to provide a new option (parameter) for read operations
specifying whether the read should be coordinated or not. Then the application
developers rather than administrators will be in full control of what they
coordinate.
*> Journals everywhere*
If I follow your logic correctly
> Coordinated replication of the namespace using ConsensusNode
> ------------------------------------------------------------
>
> Key: HDFS-6469
> URL: https://issues.apache.org/jira/browse/HDFS-6469
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Attachments: CNodeDesign.pdf
>
>
> This is a proposal to introduce ConsensusNode - an evolution of the NameNode,
> which enables replication of the namespace on multiple nodes of an HDFS
> cluster by means of a Coordination Engine.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
