[
https://issues.apache.org/jira/browse/HDFS-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416873#comment-16416873
]
Yiqun Lin commented on HDFS-13248:
----------------------------------
Hi, [~elgoiri],
{quote}Currently, hadoop-hdfs-rbf depends on hadoop-hdfs, not the other way
around.
If we do this, we would have a cyclic dependency.
{quote}
How about move the logic {{setCallerContext}} in hadoop-hdfs. It will be good
to make the logic of constructing/parsing CallerContext in the same place and
supply corresponding method. Otherwise, it's hard to understand.
In addition, would you mind adding a simple test for this (maybe in test, the
client and the Router are the same address)?
> 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,
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
