How to fix "Mixed shard index types" on new _internal db?

f1outsourcing · November 27, 2018, 1:42pm

Nov 27 14:31:07 db1 influxd: ts=2018-11-27T13:31:07.796422Z lvl=warn msg="Mixed shard index types" log_id=0C1Lgl6W000 service=store tsi1_count=1 inmem_count=4 db_instance=_internal

How can I fix this? Maybe it is also related to the deleting?

github.com/influxdata/influxdb

tsdb: don't allow deletes to a database in mixed index mode

influxdata:master ← influxdata:jmw-tsdb-disallow-mixed-index

opened 08:01PM - 20 Nov 18 UTC

zeebo

+58 -16

TSI1 and inmem indexes have different properties during deletes. Specifically, …inmem shares a global index across all shards, where every tsi1 index is contained to a specific shard. When deleting a series, it may cause the last reference to the series across all shards to be dropped, necessitating a removal from the series file. Since the inmem index shares the index across all shards, removing the series when it's removed from the series file is sufficient. However, in the case of a mixed index database, if the last shard is a TSI1 shard, the other inmem indexes are not available when we discover that it was the last reference to the series. This ends up leaving the series in the inmem index without a series id in the series file, causing all sorts of misbehavior. Rather than continue curling ourselves into a ball to try to fix this unsupported mode, give a helpful error message to the user that they must run their database in a non-mixed index mode to allow deletes. Updates #9694.

Topic		Replies	Views
Retention policy with mix shard type influxdb	1	313	January 23, 2023
How to roll back tsi1 index to inmem in production	2	1202	September 11, 2018
Deleting Data in InfluxDB2 fails InfluxDB 2	8	2621	September 5, 2021
Influxdb 1.7.9 with tsi1 index cannot delete measurements	5	863	October 7, 2020
Influxdb memory issue	2	479	August 27, 2020

How to fix "Mixed shard index types" on new _internal db?

Related Topics