Set redis timeout to 60s
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- [YES/NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
Google Cloud -
IBM
Does this introduce a breaking change?
- [YES/NO]
Currently, the Redis cache timeout is incorrectly set for 1hr. Elasticsearch backend cursors are only valid for 60s. They are hashed and cached by search service for security reasons. Since the cache timeout does not make that of the backend cursors, this causes an additional call to Elasticsearch that eventually fails.