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 "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/28 01:11:00 UTC

[jira] [Updated] (HDFS-17270) RBF: Fix ZKDelegationTokenSecretManagerImpl use closed zookeeper client to get token in some case

     [ https://issues.apache.org/jira/browse/HDFS-17270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shilun Fan updated HDFS-17270:
------------------------------
     Target Version/s: 3.4.0
    Affects Version/s: 3.4.0

> RBF: Fix ZKDelegationTokenSecretManagerImpl use closed zookeeper client  to get token in some case
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-17270
>                 URL: https://issues.apache.org/jira/browse/HDFS-17270
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: rbf
>    Affects Versions: 3.4.0
>            Reporter: lei w
>            Assignee: lei w
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>         Attachments: CuratorFrameworkException
>
>
> Now, we use CuratorFramework to simplifies using ZooKeeper in ZKDelegationTokenSecretManagerImpl and we always hold the same zookeeperClient after initialization ZKDelegationTokenSecretManagerImpl. But in some cases like network problem , CuratorFramework may close current zookeeperClient and create new one. In this case , we will use  a zkclient which has been closed  to get token. We encountered this situation in our cluster，exception information in attachment.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org