Jaeger Elasticsearch Storage Backend Cache Staleness in v1.52

Elasticsearch Storage Backend Cache Configuration in Jaeger v1.52

The Elasticsearch storage backend in Jaeger implements query-level caching through the storage-backend-cache configuration option. This cache returns stale trace data when Elasticsearch index refresh intervals exceed the query timing windows, causing inconsistencies during high-throughput collection periods. The default cache TTL of 5 minutes may result in users retrieving outdated trace information without any built-in mechanism to detect or invalidate stale cache entries when underlying trace indices are updated.

Cache behavior differs significantly between Cassandra and Elasticsearch backends, with no unified staleness detection mechanism across storage implementations. Configuration changes to storage-backend-cache require service restart to take effect, and there are no cache invalidation hooks for real-time trace data consistency. During periods of intense trace collection, queries may return results that don't reflect the most recent trace data as Elasticsearch indices are refreshed on their configured schedule.

Key Questions

• Does the storage-backend-cache configuration in Jaeger v1.52 provide any mechanism to detect or mitigate stale cache results when Elasticsearch indices are refreshed?
• What is the recommended approach for handling cache staleness in high-throughput environments where Elasticsearch refresh intervals may cause inconsistent trace retrieval?
• How can operators configure or monitor cache behavior to ensure trace data consistency during active collection periods?