Slow retrieval of nested keys

[datamc-pdetomasi]

I am experiencing an issue with retrieving keys inside a nested folder.

If I have /folder1/Key then it can retrieve the key instantly, whether this is using Rundeck's Key Storage browser or through a job itself.

If I have /folder1/folder2/Key then there is about an 8 second delay PER key.
Thus when i have a job which references 5 keys, there is a considerable delay just to get the keys and start the job.

I am running:

• Rundeck 3.0.21-20190424
• vault-storage-1.3.2-SNAPSHOT.jar
• Vault 1.1.2

Rundeck is running in a docker and vault is running in a docker on a seperate system which they are on an intranet together.
I can't see any considerable CPU or RAM usage spiking on either system.

Any idea why this is happening? any help would be much appreciated

[datamc-pdetomasi]

Bump
does anyone have a solution for me yet?

[chagaspa]

Hi having trouble configuring the integration can you share your configuration in the docker yaml ?
are you using the env VARIABLES or using the remco template ?

Thanks in advance
Paulo

[datamc-pdetomasi]

Hi Paulo, A colleague of mine solved this issue, he had to debug the code a little and found the place where it failed and then retried a few times. Solved by reducing the timeout of this stage to almost zero Regards, Patrick From: chagaspa <[email protected]> Sent: Wednesday, 15 April 2020 2:09 AM To: rundeck-plugins/vault-storage <[email protected]> Cc: Patrick De Tomasi <[email protected]>; Author <[email protected]> Subject: Re: [rundeck-plugins/vault-storage] Slow retrieval of nested keys (#18) Hi having trouble configuring the integration can you share your configuration in the docker yaml ? are you using the env VARIABLES or using the remco template ? Thanks in advance Paulo — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMLAS3RML66S7VWNVXXGJALRMSDBLANCNFSM4IXKMK5Q>.

[padraiglennon]

I've been hit by this issue as well. The following was a workaround for now

config.retryIntervalMilliseconds=50

[ElfoLiNk]

Upgrading to 'vault-java-driver', version: '5.1.0' will solve the issue due to

Changes the retry behavior, to no longer attempt retries on 4xx response codes (for which retries generally won't succeed anyway). This is the only (mildly) breaking change in this release, necessitating a major version bump. (PR #176) BetterCloud/vault-java-driver#176