Details
-
Improvement
-
Resolution: Fixed
-
Major
-
5.0.0
Description
High-level plan is:
- Impose a bucket-wide TTL that is used as a mandatory maximum TTL. i.e if mutations are received with a higher (or no) TTL set, the bucket-TTL will be used.
- Can be changed dynamically
- Not imposed retrospectively - only applies to updates received after TTL is set.
- Manual compaction is required to expunge items from disk
- All ways of receving mutations (CRUD / XDCR / Restore) will be subject to this policy
Attachments
Issue Links
For Gerrit Dashboard: MB-26729 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
86969,17 | MB-26729: [2/n] Allow memcached to limit expiry | master | kv_engine | Status: MERGED | +2 | +1 |
87483,4 | MB-26729: [1/n] Add a unit test for part of mc_time | master | kv_engine | Status: MERGED | +2 | +1 |
87526,10 | MB-26729: [3/n] Use max_ttl when creating or touching items | master | kv_engine | Status: MERGED | +2 | +1 |
87598,10 | MB-26729: [4/n] Update set_param so max_ttl is a dynamic setting | master | kv_engine | Status: MERGED | +2 | +1 |
87979,6 | MB-26729: Enforce MaxTTL on SetWithMeta | master | kv_engine | Status: MERGED | +2 | +1 |