Use of TTL doubles data footprint with phantom records [DATAREDIS-1091] #1661
As per this section of code, the use of the TimeToLive doubles the data footprint in redis due to the creation of phantom records.
For those who are familiar with redis and just want to set a TTL on our objects, this is a very surprising and dangerous side effect as it effectively doubles the data footprint in redis.
I suggest that this should be an opt-in feature via application properties.
Affects: 2.2.4 (Moore SR4)
Referenced from: pull request #517
The text was updated successfully, but these errors were encountered: