Daniel Blando

**Describe the bug** Cortex after finishing compacting a block marks it to be deleted. The way cortex does that is adding a `deletion-marker` at the storage level. Currently, Cortex uploads...

**What this PR does**: As mentioned in the feature, it would be nice if we know ingesters are empty to safely scale it down. This extends the existent api on...

New ring state READONLY to be used by ingesters

8

**What this PR does**: This PR creates a new status in ring called READONLY. When an ingester is in READONLY it will not receive write requests but it will receive...

Alternative to scaling down ingesters

3

**Is your feature request related to a problem? Please describe.** Today, scaling down ingesters is a complicated and highly manual process. As described on the [website](https://cortexmetrics.io/docs/guides/ingesters-scaling-up-and-down/#scaling-down), scaling down requires ensuring...

**What this PR does**: When cleanUpUser takes long it might delay compaction cleaner metrics leaving the user blind to what is happening. This approach separate metrics in another go routine...

Shipper is blocked when block has corrupted meta.json

3

Thanos: v0.38.0 **What happened**: The head compaction created a corrupted `meta.json` file for one of the new blocks. When shipper tried to Sync blocks to objstore(my case S3), it failed...

Do not use ignoreDeletionMarker filter for bucketindex lister

1

**What this PR does**: This is yet another case of double compaction which can create an unwanted group. The fetcher when using bucketIndex strategy have a limit visibility of activeBlocks...

Replace active series with head stale metric

1

**Is your feature request related to a problem? Please describe.** Cortex has a `cortex_ingester_active_series` metric to export data of recently ingester series by user. This data is controlled by Cortex...