[
https://issues.apache.org/jira/browse/HDFS-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475022#comment-16475022
]
Anu Engineer edited comment on HDFS-13098 at 5/14/18 11:15 PM:
---------------------------------------------------------------
it is not only this feature, it is sum total of a set of JIRAs that adds to
being a large Jira and that is why I want this work to be moved to a branch.
When we interweave small features with large ones the benefits of open source
developement is lost. You are not getting enough bandwidth from community (as
is the case with JIRA, since you feel that that there is no interest). In case
of a branch merge, lots of committers will look at it. So it is a win-win
sceanerio to do this and other proposed RBF work in a branch.
I hope you agree that 100+ patches for this feature is quite a lot; much
smaller features are generally developed in its own branch.
was (Author: anu):
it is not only this feature, it is sum total of a set of JIRAs that adds to
being a large Jira and that is why I want this work to be moved to a branch.
When we interweave small features with large ones the benefits of open source
developement is lost. You are not getting enough bandwidth from community (as
is the case with JIRA, since you feel that that there is no interest). In case
of a branch merge, lots of committers will look at it. So it is a win-win
sceanerio to do this and other proposed RBF work in a branch.
I hope you agree that 100+ patches for this feature is quite a lot much
smaller features are generally developed in its own branch.
> RBF: Datanodes interacting with Routers
> ---------------------------------------
>
> Key: HDFS-13098
> URL: https://issues.apache.org/jira/browse/HDFS-13098
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Priority: Major
>
> Datanodes talk to particular Namenodes. We could use the Router
> infrastructure for the Datanodes to register/heartbeating into them and the
> Routers would forward this to particular Namenodes. This would make the
> assignment of Datanodes to subclusters potentially more dynamic.
> The implementation would potentially include:
> * Router to implement part of DatanodeProtocol
> * Forwarding DN messages into Routers
> * Policies to assign datanodes to subclusters
> * Datanodes to make blockpool configuration dynamic
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
