[ https://issues.apache.org/jira/browse/HDFS-13248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808863#comment-16808863 ]
He Xiaoqiao commented on HDFS-13248: ------------------------------------ Overall, we need to extend three method in #ClientProtocol: addBlock/getAdditionalDatanode/getBlockLocations. 1. In order to avoid compatibility issues, we could just add new method as aboves with additional only parameter #clientHostname. And keep all current interface. 2. The new interface just for Router in generally, of course it can invoke by client directly, but I think the risk is under control:(1) RBF final target is disable access from DFSClient to Namenode directly rather than through Router. (2) If not disable, I think DFSClient using a fake #clientHostname will not weaken data security. Welcome any more suggestions. Based on above conditions, I has implemented quick-and-dirty prototype and run on my test env for weeks. Anyway, it is necessary to vote and get suggestions through mail-list. I would like to push that forward if not any more suggestions here after this week. > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org