-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0.4
-
Component/s: TTL
-
None
-
ALL
Hi Team,
We are using mongodb V 3.0.4 and storage engine of "WiredTiger". In one of our collections', we are storing the security/auth tokens with TTL index on token expiry time. We are aware that, as per our mongo documentation, we will have a latency of around 1 min. But in our system we are seeing a latency of around 15 - 20 mins. As we are planning to implement authentication based on the same, it would be a major security concern.
Another interesting fact we found here is, even after 15 mins, the TTL logic is only deleting the oldest record and not all the expired records. Say for example, if TTL indexed column is having timestamps, 10:25am, 10:26am, 10:28 am etc... and while we check at around 10:40am only record with 10:25am is getting deleted and not all the expired data, similarly say at 10:45 am it is deleting only record with 10:26am and not all the expired data.
We checked if any option to reduce the sync time, but as per mongo documentation, we couldn't find a one.
Kindly guide us on the same.
Regards,
Kingsly J
- duplicates
-
SERVER-19334 TTL index deletions cannot always keep up with insertions with WiredTiger
- Closed