3.3 KiB
| title | description | menu | weight | alt_links | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Migrate data to InfluxDB Clustered | Migrate data from InfluxDB powered by TSM (OSS, Enterprise, or Cloud) to InfluxDB Clustered. |
|
104 |
|
Migrate data to InfluxDB Clustered powered by InfluxDB v3 from other InfluxDB instances powered by TSM including InfluxDB OSS 1.x, 2.x, InfluxDB Enterprise, and InfluxDB Cloud (TSM).
Should you migrate?
There are important things to consider with migrating to InfluxDB Clustered. The following questions will help guide your decision to migrate.
Are you currently limited by series cardinality?
Yes, you should migrate. Series cardinality is a major limiting factor with the InfluxDB TSM storage engine. The more unique series in your data, the less performant your database. The InfluxDB v3 storage engine supports near limitless series cardinality and is, without question, the better solution for high series cardinality workloads.
Do you want to use SQL to query your data?
Yes, you should migrate. InfluxDB Clustered lets you query your time series data with SQL. For more information about querying your data with SQL, see:
Do you want better InfluxQL performance?
Yes, you should migrate. One of the primary goals when designing the InfluxDB v3 storage engine was to enable performant implementations of both SQL and InfluxQL. When compared to querying InfluxDB powered by TSM (InfluxDB OSS 1.x, 2.x, and Enterprise), InfluxQL queries are more performant when querying InfluxDB powered by InfluxDB v3.
Are you reliant on Flux queries and Flux tasks?
You should not migrate. {{% product-name %}} doesn't support Flux.
Before you migrate
Before you migrate from InfluxDB 1.x or 2.x to {{< product-name >}}, there are schema design practices supported by the TSM storage engine that are not supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
- You can't use duplicate names for tags and fields
- By default, measurements can contain up to 250 columns where each column represents time, a field, or a tag.
For more information, see Schema restrictions.
If your schema does not adhere to these restrictions, you must update your schema before migrating to {{< product-name >}}.
Data migration guides
{{< children >}}