HIVE-26632: Update DelegationTokenSecretManager current key ID to pre… #3673
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…vent erroneous database updates.
What changes were proposed in this pull request?
Update DelegationTokenSecretManager current key ID to prevent erroneous database updates.
Why are the changes needed?
When multiple HiveMetaStore processes share a database for
MASTER_KEYS
, this bug can cause incorrect update attempts and increased database load.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Run multiple HiveMetaStore processes sharing the same database. To make it easier to expose the problem, downtune configuration properties related to master key rollover to artificially low values:
hive.cluster.delegation.token.gc-interval
hive.cluster.delegation.key.update-interval
hive.cluster.delegation.token.max-lifetime
WIthout the patch, stack traces like this are visible in the logs:
After applying the patch, the problem goes away.
The exact timing makes it difficult to reproduce accurately in a unit test.