You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/14 22:19:00 UTC
[jira] [Updated] (HIVE-26632) Update DelegationTokenSecretManager current key ID to prevent erroneous database updates.
[ https://issues.apache.org/jira/browse/HIVE-26632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HIVE-26632:
----------------------------------
Labels: pull-request-available (was: )
> Update DelegationTokenSecretManager current key ID to prevent erroneous database updates.
> -----------------------------------------------------------------------------------------
>
> Key: HIVE-26632
> URL: https://issues.apache.org/jira/browse/HIVE-26632
> Project: Hive
> Issue Type: Bug
> Components: Standalone Metastore
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While rolling a new master key, {{TokenStoreDelegationTokenSecretManager}} does not update a base class member variable that tracks the current key ID. This can cause situations later where it attempts to update a key using an incorrect ID. This update attempt fails, even though the process had successfully generated a new master key. Since it appears to be a failure though, the thread immediately attempts to roll a new master key again, resulting in excess database load.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)