756321 - Memcache values have no ttl

Status: RESOLVED INVALID

(Cloud Services Graveyard :: Server: Sync, defect, P4)

Description

[Toby Elliott [:telliott]]

As it currently stands, no memcache data will exipire (it might get pushed out, obviously). That doesn't make a lot of sense. At the very least, we should be sticking a ttl on tab records, and I can't imagine we'd want to keep them if they haven't been accessed for, say, two months, so a logical fallback makes sense. Worst case, we write it with the expiry = max ttl on the actual tabs.

There are some advantages to keeping the other 3, but even there it might make sense to define sane expiration defaults. An occasional recalculation is not the end of the world.

Comment 1

[Ryan Kelly [:rfkelly]]

We should do something like this for sync1.5, taking the bug.

Comment 2

[Philip Jenvey [:pjenvey]]

We're no longer using memcache, closing as now invalid.