-
Hi,
we are experiencing high memory usage and OOM kill loop while using Coroot in our GKE cluster. Coroot container tries to allocate up to 14GiB of memory before it is killed. Here is the complet…
-
Here's a sample trace zoomed in on a single compact. We see 17 hits and 9008 misses.
![image](https://user-images.githubusercontent.com/340884/223864552-2dcf76a7-9de4-4db7-81f7-5dbcd9dcda91.png)
…
jamii updated
3 weeks ago
-
### Describe the bug (actual behavior)
I recently installed the sentry helm chart and it seems that the sentry-ingestors is leaking postgres connections. After one day running with really low traff…
-
**Feature (What you would like to be added):**
There is support for compaction sub command in ETCD BR, see [here](https://github.com/gardener/etcd-backup-restore/pull/301). Compaction sub command act…
-
## Overview
Compaction can be configured to run highly concurrent for all in-memory operations. It use all the allocated threads (configurable) to perform
- Merge
- Creating indexes - sorted-inde…
-
### Nomad version
Reproduced on both:
* Nomad v0.12.4 (8efaee4ba5e9727ab323aaba2ac91c2d7b572d84)
* Nomad v0.11.4 (519afbec9aa4b03b681f5816758913b717df9649)
### Operating system and Environme…
-
**Describe the bug**
KeyDB never releases space from the Flash storage. Despite manually deleting keys, the amount of used storage does not significantly decrease.
**To reproduce**
1. Run Key…
-
**Current behaviour**
I have found that enabling auto-compaction in the Ruby GC is causing what appears to be random memory related bugs. This bug manifests in the following way:
***Manifestation …
-
Each segment has a partitionId which uniquely identifies the segment in a time chunk. Currently, you cannot compact segments with minor compaction (which uses the segment lock) if their partitionIds a…
-
**Describe the bug**
Context:
- We bumped our **tempo-distributed** chart from the version 1.15.2, tempo 2.5.0 to the version 1.1.8.0, tempo v2.6.0.
- Since we were not using any parameters related t…