You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Yuanbo Liu (Jira)" <ji...@apache.org> on 2022/04/24 06:29:00 UTC
[jira] [Commented] (HDFS-16558) Consider changing the lock of delegation token from write lock to read lock
[ https://issues.apache.org/jira/browse/HDFS-16558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526986#comment-17526986 ]
Yuanbo Liu commented on HDFS-16558:
-----------------------------------
cc: [~hexiaoqiao] [~stevel@apache.org] [~daryn] [~kihwal] to bring more discussion
here is the related issue: HDFS-13112
> 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
> Attachments: image-2022-04-24-14-13-04-695.png, image-2022-04-24-14-13-52-867.png
>
>
> 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-13-04-695.png|width=334,height=212!
> !image-2022-04-24-14-13-52-867.png|width=324,height=173!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org