[
https://issues.apache.org/jira/browse/HADOOP-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029930#comment-18029930
]
ASF GitHub Bot commented on HADOOP-18864:
-----------------------------------------
github-actions[bot] commented on PR #5984:
URL: https://github.com/apache/hadoop/pull/5984#issuecomment-3404077836
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Multiple token access is supported in HA noZK KMS environment
> -------------------------------------------------------------
>
> Key: HADOOP-18864
> URL: https://issues.apache.org/jira/browse/HADOOP-18864
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 3.3.6
> Reporter: kuper
> Priority: Minor
> Labels: pull-request-available
> Attachments: image-2023-08-24-19-53-24-665.png
>
>
> When there is no configuration of ZooKeeper synchronization for secrets on
> the KMS server (hadoop.kms.authentication.signer.secret.provider is null),
> the YARN MapReduce job fails to run successfully. The reason is that the KMS
> returns an error "invalidToken" as it cannot find the corresponding token in
> the cache.
> !image-2023-08-24-19-53-24-665.png!
> Is it possible to achieve fault tolerance by accessing multiple KMS services
> without configuring zookeeper for synchronization in KMS?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
