Installing your influx enterprise cluster

Katy Farmer, Developer Advocate
April 12, 2018
Getting Started Series
Installing your
InfluxEnterprise Cluster

© 2018 InfluxData. All rights reserved.2 © 2018 InfluxData. All rights reserved.2
The Market-Leading
Time Series Platform
Built specifically for
metrics, events, and
other time-based data
Fastest Time to Awesome
Take Action While it Matters
Fast, Scalable, Available

© 2018 InfluxData. All rights reserved.3
InfluxData Products and Offerings
InfluxData Platform
Commercial Offerings
Open Source Core
PRODUCTION
DEVELOPMENT
✓ Clustering
✓ Manageability
✓ Security
Chronograf
InfluxDB
Kapacitor
Telegra
f
Agent collecting and
reporting Metrics
and Events
Complete Interface for the InfluxData Platform
Purpose-Built Time Series Database
Real-Time Streaming Data Processing Engine
InfluxEnterprise
InfluxCloud

✓ What is InfluxEnterprise and
InfluxCloud
✓ What is an InfluxDB Cluster
Meta vs. Data Nodes
✓ What type of hardware should I
run my cluster on
✓ Demo of the installation of an
InfluxEnterprise cluster
Agenda

What is InfluxEnterprise?
• Full InfluxData components of the TICK Stack: Telegraf, InfluxDB, Chronograf, & Kapacitor
• With the added features only in InfluxEnterprise
– InfluxDB Clustering capabilities:
• High-Availability
• Scalability
– Kapacitor Clustering capabilities:
• High-Availability
• Scalability (coming)
– Enhanced backup and restore
– Fine-grained auth
– Enhanced Security
– Battle Tested and hardened
– Enhanced production deployment capabilities
• InfluxCloud also includes these InfluxEnterprise features

InfluxDB:
Time Series
Index (TSI)
Considerations
• To Support High Cardinality workloads (>10
million series)
• Scale out with TSI or # of nodes in your
cluster
– 1.5 million series/16GB/RF
• Enabling TSI
– Higher CPU load
– Increased Disk I/O

InfluxData Project Architecture

InfluxEnterprise Architecture
• An InfluxEnterprise installation
consists of three separate software
processes
– Data nodes
– Meta nodes
– Chronograf
• To run an InfluxDB cluster, only the
meta & data nodes are required

Meta Nodes
• Keep the meta-state consistent
across the cluster
– Users
– Databases
– Continuous Queries
– Retention Policies
– Shard Locations
– Servers
• 3 meta nodes for High Availability
Typically Meta nodes do not need
a large amount of resources

Data Nodes
• Store time series data
• Respond to queries
• Do not participate in consensus
• 2 Data Nodes for High Availability
Typically Data nodes need a large
number of resources.

Chronograf
• User Management
• Pre-built Dashboards
• Custom Dashboards
• Database Management
• Retention Policy Management

InfluxEnterprise Monitoring
• A complete InfluxEnterprise
installation should include an
dedicated InfluxDB instance that
monitors the InfluxDB Cluster
– Separate InfluxDB instance
– Telegraf on each node
– Chronograf for visualization

General Cluster Advice
• Put a load balancer in front of each of your data nodes so that
queries are spread across each node in the cluster.
• Higher replication factors result in lower query latency, but
higher write latency.

Hardware Recommendations
• Data nodes
– 4 CPU cores (minimum)
– 16G RAM (minimum)
• Meta nodes
– 1 CPU core
– 2G RAM
– Need to have an odd # of Meta nodes

Replication Factor and Anti-Entropy
Cluster M
Meta nodes and Data nodes
MM
D D
Shards
Replication Factor 1
D1
D2
RF = 2
12-12:59
time
1 2 3 4
2-2:591-1:59 3-3:59

How to utilize Replication Factor
When creating a Database
When creating a Retention Policy
CREATE DATABASE mydb WITH REPLICATION 2
CREATE RETENTION POLICY myrp ON mydb DURATION 1h REPLICATION 1

General Cluster Advice
Higher replication factors result in lower query latency, but higher
write latency.

How to Setup a 2 Data Node Cluster
• Get a License Key
• Start 5 Machines
– 3 Meta Instances
– 2 Data Instances
• Meta Instances
– Download the Package
– Configure the Nodes
– Start the Nodes
– Join the Nodes
• Data Instances
– Download the Package
– Configure the Nodes
– Start the Nodes
– Add the Nodes

Enterprise Kapacitor
• High Availability
– Each Kapacitor node needs to be
configured the same
– Only one event will be triggered from
the set
• Scalability on the roadmap

Demo

InfluxEnterprise commands
$influxd-meta config
reporting-disabled = false
bind-address = “”
hostname = “”
[enterprise]
registration-enabled = false
registration-server-url = “”
license-key = “”
license-path = “”
[meta]
dir = “/Users/katy/.influxdb/meta”
retention-autocreate = true
logging-enabled = true
bind-address = “:8089”
auth-enabled = false
http-bind-address = “:8091”
https-enabled = false
https-certificate = “”
https-private-key = “”
https-insecure-tls = false
gossip--frequency = “5s”
announcement-expiration = “30s”
...

Shards (Shard Groups technically)
12-12:59
time
Cluster M
Meta nodes and Data nodes
MM
D D
Shards 1 2 3 4
2-2:591-1:59 3-3:59

Installing your influx enterprise cluster

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Installing your influx enterprise cluster

Similar to Installing your influx enterprise cluster (20)

Recently uploaded

Recently uploaded (20)

Installing your influx enterprise cluster