HADOOP-18864.Multiple token access is supported in ha nozk kms environment #5984
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.
Description of PR
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.
Is it possible to achieve fault tolerance by accessing multiple KMS services without configuring zookeeper for synchronization in KMS?
How was this patch tested?
unit test.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?