[
https://issues.apache.org/jira/browse/HDFS-16283?focusedWorklogId=788462&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-788462
]
ASF GitHub Bot logged work on HDFS-16283:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jul/22 03:17
Start Date: 07/Jul/22 03:17
Worklog Time Spent: 10m
Work Description: Hexiaoqiao commented on PR #4524:
URL: https://github.com/apache/hadoop/pull/4524#issuecomment-1177004299
@ayushtkn It is not related with any security issue when I propose to use
path as one parameter of renewLease. Actually in my opinion, it will be
confused and poor readable with both namespaces and router name at client side,
without other strong support points.
> For MultipleDestinationMount, it could forward to different NS when
request with file path only, especially for DestinationOrder.RANDOM and related
order.
As mentioned above, for MultipleDestinationMount it will be difficult to
reduce requests to NameNode at Router side. (I am limited by my internal case
where no MultipleDestination with DestinationOrder.RANDOM hash configured.)
In conclusion, I agree that the current approach (expose namespaces to
client and use ns to renewLease) will be more general solution, especially for
MultipleDestinationMount cases. Thanks all for your detailed explanation.
Issue Time Tracking
-------------------
Worklog Id: (was: 788462)
Time Spent: 5h 20m (was: 5h 10m)
> RBF: improve renewLease() to call only a specific NameNode rather than make
> fan-out calls
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-16283
> URL: https://issues.apache.org/jira/browse/HDFS-16283
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Priority: Major
> Labels: pull-request-available
> Attachments: RBF_ improve renewLease() to call only a specific
> NameNode rather than make fan-out calls.pdf
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Currently renewLease() against a router will make fan-out to all the
> NameNodes. Since renewLease() call is so frequent and if one of the NameNodes
> are slow, then eventually the router queues are blocked by all renewLease()
> and cause router degradation.
> We will make a change in the client side to keep track of NameNode Id in
> additional to current fileId so routers understand which NameNodes the client
> is renewing lease against.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
