feat: expose max_memory_samples parameter for redis/elasticache

[alouvion-aneo]

linked to infra pr : link

As described in the official Redis documentation :
Redis LRU eviction is not a perfect LRU but use sampling : link
=> during the eviction process by default batchs of 5 random keys are challenged and the oldest one is removed
=> This can lead to data loss in our running job.
Depending of the user workload it can be helpful to expose the sampling number in the configuration of redis/elasticache
It will not fix the problem, but it will reduce the frequency of its occurrence.
test validation screenshot on AWS

[CLAassistant]

All committers have signed the CLA.

[ngruelaneo]

Perhaps you should add this to the GCP deployment also?

[alouvion-aneo]

Perhaps you should add this to the GCP deployment also?

We can't set this variable on GCP
cf link :
https://cloud.google.com/memorystore/docs/redis/supported-redis-configurations?hl=fr
https://cloud.google.com/memorystore/docs/redis/reference/rest/v1/projects.locations.instances?hl=fr#Instance.FIELDS.redis_configs

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud