Using InfluxDB v1.8 right now, and looking at moving to InfluxDB v2. While doing some experiments in InfluxDB Cloud, it complained about cardinality already, and I’m just getting started… Am I correct that “field keys” (v1 terminology) count towards cardinality in v2, as if all metrics are stored in a table with just one column?
The reason I embraced InfluxDB is because I have quite a few “wide” measurements, some even a few dozen different fields per measurement. For one of my test cases (for a single system):
- 22 measurements selected
- 19 measurements produced (because we don’t have all resources)
- 1433 series (measurement plus tags)
- 162 unique (measurement, field-key) pairs
- 113 unique field-keys
- 13752 unique (measurement plus tags, field-key) pairs
Where v1.8 was just happy with the 1433, v2 seems concerned about the 13,752 cardinality. I think this shows that on average I have 10 fields per series.
For real-life deployment, we would have 100 times more series, and cardinality of 150,000 seems doable with v1. But 10-20 times more in v2 might not be so bright. Should I worry? -Rob