InfluxDB Enterprise features
InfluxDB Enterprise runs on a network of independent servers, a cluster, to provide fault tolerance, availability, and horizontal scalability of the database.
Many InfluxDB Enterprise features are available when run with a single meta node and a single data node However this does not take advantage of the clustering capablity, and therefore does not provide high availablity assurances.
Nodes can be added to an existing cluster to improve database performance for querying and writing data. Certain configurations (e.g., 3 meta and 2 data node) provide high-availability assurances while making certain tradeoffs in query peformance when compared to a single node.
Further increasing the number of nodes can improve performance in both respects For example, a cluster with 4 data nodes and a replication factor of 2 can support a higher volume of write traffic than a single node could. It can also support a higher query workload, as the data is replicated in two locations. Performance of the queries may be on par with a single node in cases where the query can be answered directly by the node which receives the query.
For more information on clustering, see Clustering in InfluxDB Enterprise.
Enterprise authorization uses an expanded set of 16 user permissions and roles.
(InfluxDB OSS only has
Administrators can give users permission to read and write to databases,
create and remove databases, rebalance a cluster, and manage particular resources.
Organizations can automate managing permissions with the InfluxDB Enterprise Meta API.
Fine-grained authorization for particular data is also available.
InfluxDB Enterprise can also use LDAP for managing authentication.
For FIPS compliance, InfluxDB Enterprise password hashing alogrithms are configurable.
Kapacitor OSS can also delegate its LDAP and security setup to InfluxDB Enterprise. For details, see “Set up InfluxDB Enterprise authorizations”.
Hinted handoff (HH) is how InfluxDB Enterprise deals with data node outages while writes are happening. HH is essentially a durable disk based queue.
For more information, see “Hinted handoff”.
Anti-entropy is an optional services to eliminate edge cases related to cluster consistency.
For more information, see “Use Anti-Entropy service in InfluxDB Enterprise”.
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, the following resources are available:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.