-
Problem report
-
Resolution: Fixed
-
Minor
-
5.0.3
-
None
-
Sprint 69 (Oct 2020), Sprint 70 (Nov 2020), Sprint 71 (Dec 2020), Sprint 72 (Jan 2021), Sprint 73 (Feb 2021)
-
0.125
Redis Trigger prototype for "Memory usage is too high" is wrong:
The correct formula would be used_memory.last()/maxmemory. However, as can be seen on link above, the formula is maxmemory/used_memory.last().
Otherwise, it will always have an value higher than 100%, as the max memory will always be higher than the used memory.
I've changed it on a template and re-uploaded and that fixed it. Note that this is inside a discovery rule. So, you must have maxmemory set on the config.
Steps to reproduce:
- Set maxmemory value on Redis configuration
- Trigger prototype will be create
- Warning will show up: Problem: Redis: Memory usage is too high (over 90% in 5m)
Result:
Warning will show up: Problem: Redis: Memory usage is too high (over 90% in 5m)
Expected:
No warning. The calculation will always have an value higher than 100%, as the max memory will always be higher than the used memory. It shouldn't.