Updated default redis expiration value
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [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?
- [NO]
What is the current behavior?
redisExpiration = Integer.MAX_VALUE;
What is the new/expected behavior?
redisExpiration = 300;
Merge request reports
Activity
changed milestone to %M19 - Release 0.22
added GC label
requested review from @Stanislav_Riabokon and @Rustam_Lotsmanenko
assigned to @Dmitrii_Novikov
mentioned in commit fed025eb
picked the changes into the branch
cherry-pick-fed025eb
with commit e72f34d2mentioned in commit e72f34d2
mentioned in merge request !399 (merged)
changed milestone to %M18 - Release 0.21
Please register or sign in to reply