Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-6071

Table-specific Max Lookback Age

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.1.1, 4.16.1, 4.17.0
    • Component/s: None
    • Labels:
      None

      Description

      PHOENIX-5645 / PHOENIX-5881 introduced max lookback age, which prevents all mutations from being purged by major compaction for a fixed moving window of time. These earlier JIRAs had a single cluster-wide window, but operators may want to vary this for different tables (or exempt some entirely).

      This is especially important given max lookback age's interactions with HBase TTL where due to nature of the HBase compaction hooks, an HBase TTL will override the max lookback age to be max(TTL, max lookback age), which might be longer than operators want for a particular table. For tables with no indexes that have HBase TTLs, operators will likely want to turn max lookback age off for them.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gjacoby Geoffrey Jacoby
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: