Documentation

Renew or update a license key or file

Use this procedure to renew or update an existing license key or file, switch from a license key to a license file, or switch from a license file to a license key.

Note: To request a new license to renew or expand your InfluxDB Enterprise cluster, contact sales@influxdb.com.

To update a license key or file, do the following:

  1. If you are switching from a license key to a license file (or vice versa), delete your existing license key or file.
  2. Add the license key or file to your meta nodes and data nodes configuration settings. For more information, see how to configure InfluxDB Enterprise clusters.
  3. On each meta node, run service influxdb-meta restart, and wait for the meta node service to come back up successfully before restarting the next meta node. The cluster should remain unaffected as long as only one node is restarting at a time.
  4. On each data node, run killall -s HUP influxd to signal the influxd process to reload its configuration file.

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: