Administering InfluxDB Enterprise
Introduction The anti-entropy service tries to ensure that each data node has all the shards that it needs according to the meta store. This guide covers some of the basic situations where the anti-entropy service takes effect.
Concepts The anti-entropy service examines each node to see whether it has all the shards that the meta store says it should have, and if any shards are missing, the service will copy existing shards from owners to the node that is missing the shard.
Overview and use of backup and restore utilities in InfluxDB Enterprise.
Content Using configuration files Meta node configuration sections Global settings [enterprise] [meta] Data node configuration sections Global settings [enterprise] [meta] [data] [cluster] [retention] [shard-precreation] [monitor] [subscriber] [http] [graphite] [collectd] [opentsdb] [udp] [continuous-queries] [hinted-handoff] [anti-entropy] # Using configuration files Print a default configuration file The following commands print out a TOML-formatted configuration with all available settings set to their default values.
influxd-meta config Data configuration:
influxd config Create a configuration file On POSIX systems, generate a new configuration file by redirecting the output of the command to a file.
Host renaming The following instructions allow you to rename a host within your InfluxDB Enterprise instance.
First, spend write and query activity to the cluster.
Meta node: Find the meta node leader with curl localhost:8091/status. The leader field in the JSON output reports the leader meta node. We will start with the two meta nodes that are not leaders. On a non-leader meta node, run influxd-ctl remove-meta. Once removed, confirm by running influxd-ctl show on the meta leader.
Use the “influxd-ctl” and “influx” command line tools to interact with your InfluxDB Enterprise cluster and data.
Logging locations Redirecting HTTP request logging Structured logging Tracing InfluxDB writes log output, by default, to stderr. Depending on your use case, this log information can be written to another location. Some service managers may override this default.
Logging locations Running InfluxDB directly If you run InfluxDB directly, using influxd, all logs will be written to stderr. You may redirect this log output as you would any output to stderr like so:
Some customers may choose to install InfluxDB Enterprise with public internet access, however doing so can inadvertently expose your data and invite unwelcome attacks on your database. Check out the sections below for how protect the data in your InfluxDB Enterprise instance.
Enabling authentication Password protect your InfluxDB Enterprise instance to keep any unauthorized individuals from accessing your data.
Resources: Set up Authentication
Managing users and permissions Restrict access by creating individual users and assigning them relevant read and/or write permissions.
Upgrading to InfluxDB Enterprise 1.5.4 Version 1.5 includes the first official Time Series Index (TSI) release. Although you can install without enabling TSI, you are encouraged to begin leveraging the advantages the TSI indexing offers.
Upgrading InfluxDB Enterprise 1.3.x-1.5.x clusters to 1.5.4 (rolling upgrade) Step 0: Back up your cluster before upgrading to version 1.5.4. Create a full backup of your InfluxDB Enterprise cluster before performing an upgrade. If you have incremental backups created as part of your standard operating procedures, make sure to trigger a final incremental backup before proceeding with the upgrade.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community!
We welcome and encourage your feedback and bug reports for InfluxDB and this documentation.
To find support, use the following resources:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.