Add support for a lazy refresh #625
Assignees
Labels
priority: p0
Highest priority. Critical issue. P0 implies highest priority.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
enocom
added
type: feature request
enocom
added a commit
that referenced
this issue
May 6, 2024
When clients run the Proxy in environments where the CPU may be throttled, the background connection info refresh operation can fail to complete, causing connection errors. This commit introduces an option for a lazy refresh. Connection info is retrieved on an as needed-basis and cached based on the associated certificate's expiration. No background goroutine runs, unlike the default refresh ahead cache. Enable it like so: ./alloydb-auth-proxy <INSTANCE_URI> --lazy-refresh A lazy refresh may result in increased latency (more requests will be subject to waiting for the refresh to complete), but gains in reliability. Fixes #625
enocom
added a commit
that referenced
this issue
May 15, 2024
When clients run the Proxy in environments where the CPU may be throttled, the background connection info refresh operation can fail to complete, causing connection errors. This commit introduces an option for a lazy refresh. Connection info is retrieved on an as needed-basis and cached based on the associated certificate's expiration. No background goroutine runs, unlike the default refresh ahead cache. Enable it like so: ./alloydb-auth-proxy <INSTANCE_URI> --lazy-refresh A lazy refresh may result in increased latency (more requests will be subject to waiting for the refresh to complete), but gains in reliability. Fixes #625
enocom
added a commit
that referenced
this issue
May 15, 2024
When clients run the Proxy in environments where the CPU may be throttled, the background connection info refresh operation can fail to complete, causing connection errors. This commit introduces an option for a lazy refresh. Connection info is retrieved on an as needed-basis and cached based on the associated certificate's expiration. No background goroutine runs, unlike the default refresh ahead cache. Enable it like so: ./alloydb-auth-proxy <INSTANCE_URI> --lazy-refresh A lazy refresh may result in increased latency (more requests will be subject to waiting for the refresh to complete), but gains in reliability. Fixes #625
enocom
added a commit
that referenced
this issue
May 15, 2024
When clients run the Proxy in environments where the CPU may be throttled, the background connection info refresh operation can fail to complete, causing connection errors. This commit introduces an option for a lazy refresh. Connection info is retrieved on an as needed-basis and cached based on the associated certificate's expiration. No background goroutine runs, unlike the default refresh ahead cache. Enable it like so: ./alloydb-auth-proxy <INSTANCE_URI> --lazy-refresh A lazy refresh may result in increased latency (more requests will be subject to waiting for the refresh to complete), but gains in reliability. Fixes #625
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to:
The text was updated successfully, but these errors were encountered: