bug: writing block: closing index writer: postings offset table size exceeds 4 bytes: 5078829125 #7715
-
compactor error log:
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Can you give us the following parameters please?
Do you have any tips on reproducing the problem? |
Beta Was this translation helpful? Give feedback.
-
mimir git commit revision: 71ff092 I use Helm to deploy mimir on k8s |
Beta Was this translation helpful? Give feedback.
-
This to me is an indication that your block index is too big, and you will need to configure series sharding in the compactor, so that series are stored into multiple blocks. See https://grafana.com/docs/mimir/latest/references/architecture/components/compactor/#compaction-algorithm for details, and especially |
Beta Was this translation helpful? Give feedback.
-
Converting to a discussion, since it shouldn't be an actual bug. See @pstibrany's answer above. |
Beta Was this translation helpful? Give feedback.
-
@pstibrany also notes that a potential improvement would be if Mimir could detect this scenario, and provide a more helpful error message. |
Beta Was this translation helpful? Give feedback.
This to me is an indication that your block index is too big, and you will need to configure series sharding in the compactor, so that series are stored into multiple blocks. See https://grafana.com/docs/mimir/latest/references/architecture/components/compactor/#compaction-algorithm for details, and especially
-compactor.split-and-merge-shards
parameter.