Bartlomiej Plotka

> I think the issue we're describing here is not considered backfilling. At the current stage, we can't tolerate an outage longer than about 1h or we'll lose data. Where...

I guess the boundary is then 1.5x block size (once we exceed WAL (3h))?

Actually user can change that, so we can make even 2 years WAL. If some one will not upload things for 2y and suddenly want to put 2y old sample,...

> Sounds like concretely for this, we need a way to cut a head block safely that doesn't have the 1.5x time requirement/heuristic. What do you mean? When would you...

Can you share those ideas Ganesh? On Fri, 5 Jun 2020 at 09:05, Marco Pracucci wrote: > *This is still valid. @codesome has some > ideas he wanna experiment.* >...

Sorry I am missing what is the solution here... > Enable vertical compaction and querier and make that check optional - upstream will enable the check whereas Cortex and Thanos...

Sorry - no, proposal has to be in place, that's what I meant. (: Relabel-like config makes sense but essentially we are talking about rewrite in compactor for this right?

Some offline discussions revealed that users still do it with Thanos, but using federation + Thanos on top. ``` The point was to shard ingestion and execute recording rules against...

Extra context can be found here: https://github.com/prometheus/prometheus/issues/1381

The current plan is to first tackle https://github.com/thanos-io/thanos/issues/1598 then try to implement this. Putting this issue as GSoC project as well. > This is being worked on prometheus, once done...