cacheDuration impact of setting this to 100ms

Open

#1,089 opened on Feb 2, 2021 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Stale
Tech stack: java
Domain: api

Research direction

Start by reading the context.cacheDuration behavior described here and the related cf-java-client issue 749, then trace how cached 404 responses and connection timeouts are handled during UAA access-token refreshes. Done means an agreed caching or retry design prevents transient errors from being cached indefinitely, with its impact on 100 ms and 1 ms durations established.

Written by the indexing model from the issue text.

Description

reactor triaged

We recently experienced issues with the cf-java-client where the cache duration was set to indefinite by default as detailed in the issue https://github.com/cloudfoundry/cf-java-client/issues/749. However, this happened in an able that had otherwise been stable but had to refresh its access token. Upon attempting to refresh the application received a connection timeout or a sporadic 404 from the uaa server (likely during a repave of the foundation or for some unknown reason). This resulted in some requests from the same application caching the 404 or the connection timeout which rendered some operations inoperable. We have debated setting the context.cacheDuration equal to 100 ms or 1 ms to avoid this possibility but was concerned with what the potential impact this would have? We also would like to lobby for a completely different approach to be taken for caching these stable payloads such as adding exception handling that will retry in the case of IOexceptions instead of caching the error condition indefinitely.

Dominant language: Java
Stars: 334
Forks: 319
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[BUG] Unified agent on Bedrock Converse with no tools is unusable: an empty `toolConfig` is emitted and Bedrock rejects the request Open

bug untriaged

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

opensearch-project/ml-commons#5094 · Opened Sep 22, 2026
[Bug report] iceberg rest server load_table with refs fails precondition check "Cannot set metadata location with changes to table metadata: %s changes" for snapshots with statistics Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

apache/gravitino#13452 · Opened Sep 22, 2026
Support Test Project Creation for New Projects Open

emitter:client:csharp feature

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

microsoft/typespec#12027 · 1 comment · 1 reaction · Opened Sep 22, 2026
Job worker stops polling silently when a poll throws an Error Open

affects/8.10 affects/8.9 component/clients kind/bug likelihood/mid severity/mid

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

camunda/camunda#63825 · Opened Sep 22, 2026
Two open-case totals on one screen: the Programs tile says 15,858 and the nav badge says 15,868 Open

bug frontend maui-pilot

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

Taleef7/workwell#651 · 1 comment · Opened Sep 22, 2026

More Java issues