[
https://issues.apache.org/jira/browse/HDFS-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804663#comment-16804663
]
Ayush Saxena commented on HDFS-13248:
-------------------------------------
Thanx Everyone for the discussion here.
Agreed that this isn't the best solution. But guess shall serve the purpose ,
with some minor cost and I don't think there would be anything at stake too
with it.
If we make the change in the getBlockLocations() as suggested. This should be a
workable solution as of now.
[~ferhui] [~elgoiri] plans taking it forward? Or something that blocks?
One doubt too: In the idle solution if the client node isn't available it tends
to go to client local rack. Will this be handled with the favouredNode concept
over here?
> RBF: Namenode need to choose block location for the client
> ----------------------------------------------------------
>
> Key: HDFS-13248
> URL: https://issues.apache.org/jira/browse/HDFS-13248
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Weiwei Wu
> Assignee: Íñigo Goiri
> Priority: Major
> Attachments: HDFS-13248.000.patch, HDFS-13248.001.patch,
> HDFS-13248.002.patch, HDFS-13248.003.patch, HDFS-13248.004.patch,
> HDFS-13248.005.patch, clientMachine-call-path.jpeg, debug-info-1.jpeg,
> debug-info-2.jpeg
>
>
> When execute a put operation via router, the NameNode will choose block
> location for the router, not for the real client. This will affect the file's
> locality.
> I think on both NameNode and Router, we should add a new addBlock method, or
> add a parameter for the current addBlock method, to pass the real client
> information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
