Skip to content
This repository was archived by the owner on May 30, 2024. It is now read-only.
This repository was archived by the owner on May 30, 2024. It is now read-only.

InvalidCacheLoadException when redis returns null feature flag #68

@jhinch

Description

@jhinch
com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key <REDACTED>
at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2350) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2320)
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2282) 
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2197)
at com.google.common.cache.LocalCache.get(LocalCache.java:3937)
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3941)
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4824)
at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4830)
at com.launchdarkly.client.RedisFeatureStore.get(RedisFeatureStore.java:145)
at com.launchdarkly.client.LDClient.evaluate(LDClient.java:202)
...

The client does catch the exception and log it, but it seems like a null value from the redis cache is an expected return, so it spams the logs with stacktraces

I experienced this in v1.0.1 of the client but it appears like it would be present in v2.0.0 as well

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions