AMBARI-25479. Set Keytab: Kerberos Client operation takes lot of time and timing out (dgrinenko) #3183
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.
What changes were proposed in this pull request?
Kerberos keytab injection to the agent command were optimized to be executed much more faster. Previously, we have created descriptors on the fly by reading them from the stack and merging in-to one. However, we have repeated this procedure each time we needed the descriptor.
In current particular place, we can't effectively cache already loaded descriptors without implementing their expire time as well as expire time on state change on the disk. Due to this fact, the idea were changed - now we will load them as part of the meta information, where are they locating now, and do not generate much IO operations when we creating a bunch of descriptors.
How was this patch tested?
Manually on a perf cluster and performance analyze on profiler snapshot,