[
https://issues.apache.org/jira/browse/HIVE-26632?focusedWorklogId=818083&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-818083
]
ASF GitHub Bot logged work on HIVE-26632:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Oct/22 17:08
Start Date: 18/Oct/22 17:08
Worklog Time Spent: 10m
Work Description: cnauroth commented on PR #3673:
URL: https://github.com/apache/hive/pull/3673#issuecomment-1282737625
http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-3673/1/tests
There are 2 CLI integration test failures that don't appear to be related to
this patch.
Issue Time Tracking
-------------------
Worklog Id: (was: 818083)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
