Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compact tenant TSDBs after 3h inactivity #5909

Merged
merged 1 commit into from
Nov 22, 2022

Commits on Nov 20, 2022

  1. Compact tenant TSDBs after 3h inactivity

    The Receiver tenant retention mechanism has an edge case when a
    tenant TSDB gets evicted and uploaded to S3. Since there is a delay
    between uploads to S3 and downloads in Store Gateways, if a user
    executes a query between the upload and download time, they may
    not see the latest head block from the evicted tenant.
    
    As a result, this commit decouples head compaction from tenant eviction.
    Head compaction, as in Prometheus, will happen if there are no new appends
    after 1.5x max-block-size. This will also cause the compacted block to be
    uploaded to S3 by the shipper. Eviction will then kick in which will cause
    the tenant TSDB to be deleted.
    
    By this time, the latest head block would have been picked up by store-gateway
    and would be available during query execution.
    
    Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
    fpetkovski committed Nov 20, 2022
    Configuration menu
    Copy the full SHA
    1a033af View commit details
    Browse the repository at this point in the history