[
https://issues.apache.org/jira/browse/HDFS-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057235#comment-14057235
]
Konstantin Shvachko commented on HDFS-6469:
-------------------------------------------
[~atm] requested an answer to Todd's comment below, which I thought I answered,
but probably not precisely enough.
??a fully usable solution would be available to the community at large, whereas
the design you're proposing seems like it will only be usably implemented by a
proprietary extension (I don't consider the ZK "reference implementation"
likely to actually work in a usable fashion).??
# I don't know which ZK deficiencies you refer to. I previously commented on
performance issues, if this is the concern. If not please elaborate.
# If for some workloads or use cases ZK is impractical, there is always a way
to replace it with another engine. That is why we make it pluggable. E.g.
[~rakeshr] indicated in HADOOP-10641 an intention to extract ZAB library. Other
alternatives both open source and proprietary exist.
# I assume that by "proprietary extension" you mean WANdisco coordination
engine and your concern is that my company will be the main beneficiary of the
feature:
#* I truly believe open sourcing ConsensusNode will make Hadoop better.
#* It is the nature of this project, that different businesses contribute
features they need for the benefit of the community.
#* Historically Yahoo built Hadoop for its internal use. Building it in AFS
made it possible for others (including your company) to adopt and prosper from
that work.
#* Making changes in Hadoop for "proprietary extensions" is rather common. Two
examples from the top of my head: topology extension to support VMs
(HDFS-3601), Windows support (HADOOP-8562). And I don't remember anybody
bothered that ESX Server or Azure are proprietary.
> 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)
