Marcus Teixeira

I have the exact same problem. In my case, my configuration is with GCS Backend `loki-linux-amd64[14413]: level=error ts=2022-02-10T18:57:03.226397424Z caller=retry.go:73 org_id=fake traceID=5ff7c24474ace112 msg="error processing request" try=0 err="context canceled"`

Great Work! One thing we can put in the role, is when timescaledb_install is set to true, already running timescaledb-tune. Ref: https://docs.timescale.com/latest/getting-started/configuring

In this example, show the fingerprint data in search of elasticsearch.  only main_test.go which does not seem to work but is still detecting the problem.

@ageis, @mattbostock, @simonpasquier

> Hi. any updates ? Could you share your configuration file here and your environment details? I initially reported this issue, but I am no longer affected by OOM cases.

I think I can add some comments on this. I updated the version from 2.8 to 2.9.1, to use the multi-store index-support concept. Previously I was already using TSDB Shipper...

@nektarios-d How are your configurations related to `storage_config`? `shared_store` assignments?