[
https://issues.apache.org/jira/browse/HDFS-16558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037571#comment-18037571
]
ASF GitHub Bot commented on HDFS-16558:
---------------------------------------
github-actions[bot] commented on PR #4230:
URL: https://github.com/apache/hadoop/pull/4230#issuecomment-3519306977
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Consider changing the lock of delegation token from write lock to read lock
> ---------------------------------------------------------------------------
>
> Key: HDFS-16558
> URL: https://issues.apache.org/jira/browse/HDFS-16558
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Yuanbo Liu
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-04-24-14-13-04-695.png,
> image-2022-04-24-14-13-52-867.png, image-2022-04-24-14-57-18-740.png,
> image-2022-04-24-14-58-25-294.png
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> In a very busy authed cluster, renewing/caneling/getting delegation token get
> slow and it will slow down the speed of handling rpcs from client. Since
> AbstractDelegationTokenSecretManager is a thread-safe manager, we propose to
> change the fs lock from write lock to read lock(protect editlog rolling)
> !image-2022-04-24-14-58-25-294.png|width=318,height=194!
> !image-2022-04-24-14-13-52-867.png|width=324,height=173!
> !image-2022-04-24-14-57-18-740.png|width=303,height=184!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
