InfluxDB Enterprise link audit
Scott Anderson
parent
857bddc2bd
commit
800ae418c7
|
|
@ -435,7 +435,6 @@ Shard 21179 removed from repair queue
|
|||
|
||||
Joins a meta node and/or data node to a cluster.
|
||||
By default, `influxd-ctl` joins the local meta node and/or data node into a new cluster.
|
||||
Use `join` instead of the [`add-meta`](#add-meta) or [`add-data`](#add-data) arguments when performing a [QuickStart Installation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation/cluster_installation/) of an InfluxDB Enterprise cluster.
|
||||
|
||||
#### Syntax
|
||||
|
||||
|
|
@ -456,8 +455,6 @@ Print verbose information about the join.
|
|||
Address of a meta node in an existing cluster.
|
||||
Use this argument to add the un-joined meta node and/or data node to an existing cluster.
|
||||
|
||||
Resources: [QuickStart installation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation/cluster_installation/)
|
||||
|
||||
#### Examples
|
||||
|
||||
###### Joining a meta and data node into a cluster
|
||||
|
|
@ -574,7 +571,6 @@ Killed shard copy 39 from cluster-data-node-02:8088 to cluster-data-node-03:8088
|
|||
#### `leave`
|
||||
|
||||
Removes a meta node and/or data node from the cluster.
|
||||
Use `leave` instead of the [`remove-meta`](#remove-meta) and [`remove-data`](#remove-data) arguments if you set up your InfluxDB Enterprise cluster with the [QuickStart Installation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation/cluster_installation/) process.
|
||||
|
||||
{{% warn %}}The `leave` argument is destructive; it erases all metastore information from meta nodes and all data from data nodes.
|
||||
Use `leave` only if you want to *permanently* remove a node from a cluster.
|
||||
|
|
|
|||
|
|
@ -9,11 +9,4 @@ menu:
|
|||
|
||||
Here are the options available for installing and deploying InfluxDB Enterprise clusters.
|
||||
|
||||
|
||||
## [Install an InfluxDB Enterprise cluster for evaluation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation/)
|
||||
|
||||
Covers steps to install an InfluxDB Enterprise cluster using two physical servers with five cluster nodes. This installation is not intended for production environments, but provides a simpler installation for evaluation and learning.
|
||||
|
||||
## [Install an InfluxDB Enterprise cluster for production](/enterprise_influxdb/v1.6/install-and-deploy/production_installation/)
|
||||
|
||||
Covers steps to install an InfluxDB Enterprise cluster for production use.
|
||||
{{< children >}}
|
||||
|
|
|
|||
|
|
@ -13,7 +13,6 @@ menu:
|
|||
This section covers deploying InfluxDB Enterprise clusters on the cloud provider of your choice.
|
||||
For information on manually installing and configuring InfluxDB Enterprise clusters, see:
|
||||
|
||||
* [Install an InfluxDB Enterprise cluster for evaluation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation/)
|
||||
* [Install an InfluxDB Enterprise cluster for production](/enterprise_influxdb/v1.6/install-and-deploy/production_installation/)
|
||||
|
||||
## [Deploy an InfluxDB Enterprise cluster on Google Cloud Platform](/enterprise_influxdb/v1.6/install-and-deploy/deploying/google-cloud-platform/)
|
||||
|
|
|
|||
|
|
@ -16,15 +16,7 @@ deploy InfluxDB Enterprise in a production environment.
|
|||
The following steps will get you up and running with the first essential component of
|
||||
your InfluxDB Enterprise cluster: the meta nodes.
|
||||
|
||||
> If you wish to evaluate InfluxDB Enterprise in a non-production
|
||||
environment, feel free to follow the instructions outlined in the
|
||||
[QuickStart installation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation) section.
|
||||
Please note that if you install InfluxDB Enterprise with the QuickStart Installation process you
|
||||
will need to reinstall InfluxDB Enterprise with the Production Installation
|
||||
process before using the product in a production environment.
|
||||
|
||||
<br>
|
||||
# Meta node setup description and requirements
|
||||
## Meta node setup description and requirements
|
||||
|
||||
The Production Installation process sets up three [meta nodes](/enterprise_influxdb/v1.6/concepts/glossary/#meta-node), with each meta node running on its own server.
|
||||
<br>
|
||||
|
|
@ -61,9 +53,8 @@ If the meta nodes cannot reach `portal.influxdata.com` on port `80` or `443`,
|
|||
you'll need to set the `license-path` setting instead of the `license-key`
|
||||
setting in the meta node configuration file.
|
||||
|
||||
<br>
|
||||
# Meta node setup
|
||||
## Step 1: Modify the `/etc/hosts` File
|
||||
## Meta node setup
|
||||
### Step 1: Modify the `/etc/hosts` File
|
||||
|
||||
Add your servers' hostnames and IP addresses to **each** cluster server's `/etc/hosts`
|
||||
file (the hostnames below are representative).
|
||||
|
|
@ -90,27 +81,27 @@ installation.
|
|||
A healthy cluster requires that every meta node can communicate with every other
|
||||
meta node.
|
||||
|
||||
## Step 2: Set up, configure, and start the meta services
|
||||
### Step 2: Set up, configure, and start the meta services
|
||||
|
||||
Perform the following steps on each meta server.
|
||||
|
||||
### I. Download and install the meta service
|
||||
#### I. Download and install the meta service
|
||||
|
||||
#### Ubuntu & Debian (64-bit)
|
||||
##### Ubuntu & Debian (64-bit)
|
||||
|
||||
```
|
||||
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.6.6-c1.6.6_amd64.deb
|
||||
sudo dpkg -i influxdb-meta_1.6.6-c1.6.6_amd64.deb
|
||||
```
|
||||
|
||||
#### RedHat & CentOS (64-bit)
|
||||
##### RedHat & CentOS (64-bit)
|
||||
|
||||
```
|
||||
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.6.6_c1.6.6.x86_64.rpm
|
||||
sudo yum localinstall influxdb-meta-1.6.6_c1.6.6.x86_64.rpm
|
||||
```
|
||||
|
||||
### II. Edit the configuration file
|
||||
#### II. Edit the configuration file
|
||||
|
||||
In `/etc/influxdb/influxdb-meta.conf`:
|
||||
|
||||
|
|
@ -125,7 +116,7 @@ The `license-key` and `license-path` settings are mutually exclusive and one mus
|
|||
```
|
||||
# Hostname advertised by this host for remote addresses. This must be resolvable by all
|
||||
# other nodes in the cluster
|
||||
hostname="<enterprise-meta-0x>"
|
||||
hostname="<enterprise-meta-0x>"
|
||||
|
||||
[enterprise]
|
||||
# license-key and license-path are mutually exclusive, use only one and leave the other blank
|
||||
|
|
@ -135,7 +126,7 @@ hostname="<enterprise-meta-0x>"
|
|||
license-path = "/path/to/readable/JSON.license.file" # Mutually exclusive with license-key
|
||||
```
|
||||
|
||||
### III. Start the meta service
|
||||
#### III. Start the meta service
|
||||
|
||||
On sysvinit systems, enter:
|
||||
```
|
||||
|
|
@ -165,7 +156,7 @@ must pass the `-single-server flag` when starting the single meta node.
|
|||
Please note that a cluster with only one meta node is **not** recommended for
|
||||
production environments.
|
||||
|
||||
## Step 3: Join the meta nodes to the cluster
|
||||
### Step 3: Join the meta nodes to the cluster
|
||||
|
||||
From one and only one meta node, join all meta nodes including itself.
|
||||
In our example, from `enterprise-meta-01`, run:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Installation options (⏰ Please Read!)
|
||||
title: Installation options
|
||||
aliases:
|
||||
- /enterprise_influxdb/v1.6/introduction/meta_node_installation/
|
||||
- /enterprise_influxdb/v1.6/introduction/data_node_installation/
|
||||
|
|
@ -10,22 +10,6 @@ menu:
|
|||
parent: Introduction
|
||||
---
|
||||
|
||||
Please review the sections below before you begin working with InfluxDB Enterprise.
|
||||
|
||||
## Which installation is right for me?
|
||||
|
||||
Two options are described for installing InfluxDB Enterprise.
|
||||
|
||||
The [QuickStart installation](/enterprise_influxdb/v1.6/install-and-deploy/quickstart_installation/) process is intended for users looking to quickly get up and running with InfluxDB Enterprise and for users who want to evaluate it.
|
||||
The QuickStart installation process **is not** intended for use
|
||||
in a production environment.
|
||||
|
||||
The [Production installation](/enterprise_influxdb/v1.6/install-and-deploy/production_installation/) process is recommended for users intending to deploy the InfluxDB Enterprise installation in a production environment.
|
||||
|
||||
> **Note:** If you install InfluxDB Enterprise with the QuickStart installation process you will need to reinstall InfluxDB Enterprise with the Production installation process before using the product in a production environment.
|
||||
|
||||
There are [deployment options](/enterprise_influxdb/v1.6/install-and-deploy/deploying/) available to easily install an InfluxDB Enterprise cluster in select environments.
|
||||
|
||||
## Requirements for InfluxDB Enterprise clusters
|
||||
|
||||
For an overview of the architecture and concepts in an InfluxDB Enterprise Cluster, review [Clustering Guide](/enterprise_influxdb/v1.6/concepts/clustering/).
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ To choose a strategy that best suits your use case, we recommend considering you
|
|||
|
||||
- [Backup and restore utilities](#backup-and-restore-utilities) (suits **most InfluxDB Enterprise applications**)
|
||||
- [Export and import commands](#export-and-import-commands) (best for **backfill or recovering shards as files**)
|
||||
- [Take AWS snapshot with EBS volumes as backup for data recovery](#take-aws-snapshots-with-ebs-volumes) (optimal **convenience if budget permits**)
|
||||
- [Take AWS snapshots as backup](/backup-and-restore/#take-aws-snapshots-as-backup) (optimal **convenience if budget permits**)
|
||||
- [Run two clusters in separate AWS regions](#run-two-clusters-in-separate-aws-regions) (also optimal **convenience if budget permits**, more custom work upfront)
|
||||
|
||||
> Test your backup and restore strategy for all applicable scenarios.
|
||||
|
|
@ -91,7 +91,7 @@ For a complete list of the global `influxd-ctl` options, see the [influxd-ctl do
|
|||
|
||||
### Backup examples
|
||||
|
||||
{{%expand "> Store incremental backups in different directories" %}}
|
||||
{{% expand "Store incremental backups in different directories" %}}
|
||||
|
||||
> If you're backing up different units, for example all retention policies in a database and a specific retention policy, store backups in different directories.
|
||||
|
||||
|
|
@ -102,9 +102,9 @@ influxd-ctl backup -db myfirstdb ./myfirstdb-allrp-backup
|
|||
influxd-ctl backup -db myfirstdb -rp autogen ./myfirstdb-autogen-backup
|
||||
```
|
||||
|
||||
{{% /expand%}}
|
||||
{{% /expand %}}
|
||||
|
||||
{{%expand "> Store incremental backups in the same directory" %}}
|
||||
{{%expand "Store incremental backups in the same directory" %}}
|
||||
|
||||
> If you're backing up multiple copies of the same database, store backups in the same directory.
|
||||
|
||||
|
|
@ -116,7 +116,7 @@ influxd-ctl backup -db myfirstdb ./myfirstdb-allrp-backup
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Perform an incremental back up" %}}
|
||||
{{%expand "Perform an incremental back up" %}}
|
||||
|
||||
> Perform an incremental backup into the current directory with the command below.
|
||||
|
||||
|
|
@ -144,7 +144,7 @@ $ ls
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Perform an full back up" %}}
|
||||
{{%expand "Perform an full back up" %}}
|
||||
|
||||
> Perform a full backup into a specific directory with the command below:
|
||||
|
||||
|
|
@ -171,7 +171,7 @@ Backed up to backup_dir in 51.388233ms, transferred 333793 bytes
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Perform an incremental back up on a single database" %}}
|
||||
{{%expand "Perform an incremental back up on a single database" %}}
|
||||
|
||||
> Point at a remote meta server and back up only one database into a given directory (the directory must already exist):
|
||||
|
||||
|
|
@ -242,7 +242,7 @@ For a complete list of the global `influxd-ctl` options, see the [influxd-ctl do
|
|||
|
||||
#### Restore examples
|
||||
|
||||
{{%expand "> Restore from an incremental backup" %}}
|
||||
{{% expand "Restore from an incremental backup" %}}
|
||||
|
||||
```bash
|
||||
influxd-ctl restore <path-to-backup-directory>
|
||||
|
|
@ -262,7 +262,7 @@ Restored from my-incremental-backup/ in 83.892591ms, transferred 588800 bytes
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Restore from a full backup" %}}
|
||||
{{% expand "Restore from a full backup" %}}
|
||||
|
||||
```bash
|
||||
influxd-ctl restore -full <path-to-manifest-file>
|
||||
|
|
@ -281,7 +281,7 @@ Restored from my-full-backup in 58.58301ms, transferred 569344 bytes
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Restore from an incremental backup for a single database and give the database a new name" %}}
|
||||
{{% expand "Restore from an incremental backup for a single database and give the database a new name" %}}
|
||||
|
||||
```bash
|
||||
influxd-ctl restore -db <src> -newdb <dest> <path-to-backup-directory>
|
||||
|
|
@ -301,7 +301,7 @@ Restored from my-incremental-backup/ in 66.715524ms, transferred 588800 bytes
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Restore from an incremental backup for a single database and give the database a new name" %}}
|
||||
{{% expand "Restore from an incremental backup for a single database and give the database a new name" %}}
|
||||
|
||||
> Your `telegraf` database was mistakenly dropped, but you have a recent backup so you've only lost a small amount of data.
|
||||
|
||||
|
|
@ -345,11 +345,11 @@ time written
|
|||
|
||||
#### Common issues with restore
|
||||
|
||||
{{%expand "> Restore writes information not part of the original backup" %}}
|
||||
{{% expand "Restore writes information not part of the original backup" %}}
|
||||
|
||||
##### Restore writes information not part of the original backup
|
||||
|
||||
If a [restore from an incremental backup](#syntax-to-restore-from-an-incremental-backup) does not limit the restore to the same database, retention policy, and shard specified by the backup command, the restore may appear to restore information that was not part of the original backup.
|
||||
If a [restore from an incremental backup](#restore-examples) does not limit the restore to the same database, retention policy, and shard specified by the backup command, the restore may appear to restore information that was not part of the original backup.
|
||||
Backups consist of a shard data backup and a metastore backup.
|
||||
The **shard data backup** contains the actual time series data: the measurements, tags, fields, and so on.
|
||||
The **metastore backup** contains user information, database names, retention policy names, shard metadata, continuous queries, and subscriptions.
|
||||
|
|
@ -364,13 +364,13 @@ The unintended data, however, include only the metastore information, not the sh
|
|||
|
||||
{{% /expand%}}
|
||||
|
||||
{{%expand "> Restore a backup created prior to version 1.2.0" %}}
|
||||
{{% expand "Restore a backup created prior to version 1.2.0" %}}
|
||||
|
||||
##### Restore a backup created prior to version 1.2.0
|
||||
|
||||
InfluxDB Enterprise introduced incremental backups in version 1.2.0.
|
||||
To restore a backup created prior to version 1.2.0, be sure to follow the syntax
|
||||
for [restoring from a full backup](#syntax-to-restore-from-a-full-backup).
|
||||
for [restoring from a full backup](#restore-examples).
|
||||
|
||||
{{% /expand%}}
|
||||
|
||||
|
|
@ -412,7 +412,7 @@ Use AWS snapshots of data nodes to recover data by exporting line protocol of hi
|
|||
|
||||
1. Schedule AWS snapshots. For example, take snapshots of data node directories (include `/data` directory at minimum, `wal` directory, and other directories as needed.)
|
||||
2. To recover data from a snapshot, create an EC2 system with InfluxDB data node programs (the data node process doesn't need to run).
|
||||
3. Attach the snapshot to your recovery EC2 system. Attach additional volumes as needed for more space.
|
||||
3. Attach the snapshot to your recovery EC2 system. Attach additional volumes as needed for more space.
|
||||
>**Note:** Extracting shards via `influx_inspect` (using compress) uses roughly 1.5 times the space as the shard. We recommend provisioning 2.5 times the space that the shards use on disk. (See AWS documentation for procedures to upsize AWS volumes in use.)
|
||||
4. Use `influx_inspect export` to extract line protocol (based on database, rp and time) as needed.
|
||||
5. [Re-import extracted line protocol](#import-data).
|
||||
|
|
|
|||
|
|
@ -441,7 +441,6 @@ Shard 21179 removed from repair queue
|
|||
|
||||
Joins a meta node and/or data node to a cluster.
|
||||
By default, `influxd-ctl` joins the local meta node and/or data node into a new cluster.
|
||||
Use `join` instead of the [`add-meta`](#add-meta) or [`add-data`](#add-data) arguments when performing a [QuickStart Installation](/enterprise_influxdb/v1.7/quickstart_installation/cluster_installation/) of an InfluxDB Enterprise cluster.
|
||||
|
||||
#### Syntax
|
||||
|
||||
|
|
@ -462,8 +461,6 @@ Print verbose information about the join.
|
|||
Address of a meta node in an existing cluster.
|
||||
Use this argument to add the un-joined meta node and/or data node to an existing cluster.
|
||||
|
||||
Resources: [QuickStart installation](/enterprise_influxdb/v1.7/quickstart_installation/cluster_installation/)
|
||||
|
||||
#### Examples
|
||||
|
||||
##### Join a meta and data node into a cluster
|
||||
|
|
@ -580,9 +577,9 @@ Killed shard copy 39 from cluster-data-node-02:8088 to cluster-data-node-03:8088
|
|||
### `leave`
|
||||
|
||||
Removes a meta node and/or data node from the cluster.
|
||||
Use `leave` instead of the [`remove-meta`](#remove-meta) and [`remove-data`](#remove-data) arguments if you set up your InfluxDB Enterprise cluster with the [QuickStart Installation](/enterprise_influxdb/v1.7/quickstart_installation/cluster_installation/) process.
|
||||
|
||||
{{% warn %}}The `leave` argument is destructive; it erases all metastore information from meta nodes and all data from data nodes.
|
||||
{{% warn %}}
|
||||
The `leave` argument is destructive; it erases all metastore information from meta nodes and all data from data nodes.
|
||||
Use `leave` only if you want to *permanently* remove a node from a cluster.
|
||||
{{% /warn %}}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ menu:
|
|||
|
||||
|
||||
* [Logging locations](#logging-locations)
|
||||
* [Redirecting HTTP request logging](#redirecting-http-request-logging)
|
||||
* [Redirecting HTTP request logging](#redirecting-http-access-logging)
|
||||
* [Structured logging](#structured-logging)
|
||||
* [Tracing](#tracing)
|
||||
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ sudo yum localinstall influxdb-meta-1.7.10_c1.7.10.x86_64.rpm
|
|||
|
||||
Migrate any custom settings from your previous meta node configuration file.
|
||||
|
||||
To enable HTTPS, you must update the meta node configuration file (`influxdb-meta.conf`). For information, see [Enable HTTPS within the configuration file for each Meta Node](/enterprise_influxdb/v1.7/guides/https_setup/#step-3-enable-https-within-the-configuration-file-for-each-meta-node).
|
||||
To enable HTTPS, you must update the meta node configuration file (`influxdb-meta.conf`). For information, see [Enable HTTPS within the configuration file for each Meta Node](/enterprise_influxdb/v1.7/guides/https_setup/#setup-https-in-an-influxdb-enterprise-cluster).
|
||||
|
||||
### Restart the `influxdb-meta` service
|
||||
|
||||
|
|
@ -164,7 +164,7 @@ sudo yum localinstall influxdb-data-1.7.10_c1.7.10.x86_64.rpm
|
|||
|
||||
Migrate any custom settings from your previous data node configuration file.
|
||||
|
||||
- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](/enterprise_influxdb/v1.7/guides/https_setup/#step-4-enable-https-within-the-configuration-file-for-each-data-node).
|
||||
- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](/enterprise_influxdb/v1.7/guides/https_setup/#setup-https-in-an-influxdb-enterprise-cluster).
|
||||
|
||||
- To enable TSI, open `/etc/influxdb/influxdb.conf`, and then adjust and save the settings shown in the following table.
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ For information about installing and setting up meta nodes, see
|
|||
|
||||
{{% note %}}
|
||||
#### Add the OSS instance to the meta /etc/hosts files
|
||||
When [modifying the `/etc/hosts` file](/enterprise_influxdb/v1.7/install-and-deploy/production_installation/meta_node_installation/#step-1-modify-the-etc-hosts-file)
|
||||
When [modifying the `/etc/hosts` file](/enterprise_influxdb/v1.7/install-and-deploy/production_installation/meta_node_installation/#step-1-add-appropriate-dns-entries-for-each-of-your-servers)
|
||||
on each meta node, include the IP and host name of your InfluxDB OSS instance so
|
||||
meta nodes can communicate with the OSS instance.
|
||||
{{% /note %}}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Install and deploy InfluxDB Enterprise
|
||||
title: Install and deploy InfluxDB Enterprise
|
||||
description: Install InfluxDB Enterprise to on-premise or cloud providers, including Google Cloud Platform, Amazon Web Services, and Azure.
|
||||
aliases:
|
||||
- /enterprise_influxdb/v1.7/install-and-deploy/deploying/google-cloud-platform/
|
||||
|
|
@ -12,7 +12,7 @@ menu:
|
|||
Install or deploy an InfluxDB Enterprise cluster in the environment of your choice:
|
||||
|
||||
- [Your cloud provider](#your-cloud-provider)
|
||||
- [Your own environment](#your-production-environment)
|
||||
- [Your own environment](#your-own-environment)
|
||||
|
||||
## Your cloud provider
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ Learn how to deploy a cluster on the cloud provider of your choice:
|
|||
|
||||
- [GCP](/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform/)
|
||||
- [AWS](/enterprise_influxdb/v1.7/install-and-deploy/aws/)
|
||||
- [Azure](/enterprise_influxdb/v1.7/install-and-deploy/deploying/azure/)
|
||||
- [Azure](/enterprise_influxdb/v1.7/install-and-deploy/azure/)
|
||||
|
||||
## Your own environment
|
||||
|
||||
|
|
|
|||
|
|
@ -16,4 +16,4 @@ Complete the following steps to install an InfluxDB Enterprise cluster in your o
|
|||
2. [Install InfluxDB data nodes](/enterprise_influxdb/v1.7/install-and-deploy/production_installation/data_node_installation/)
|
||||
3. [Install Chronograf](/enterprise_influxdb/v1.7/install-and-deploy/production_installation/chrono_install/)
|
||||
|
||||
> **Note:** If you're looking for cloud infrastructure and services, check out how to deploy InfluxDB Enterprise (production-ready) on a cloud provider of your choice: [Azure](/enterprise_influxdb/v1.7/install-and-deploy/deploying/azure/), [GCP](/enterprise_influxdb/v1.7/install-and-deploy/deploying/google-cloud-platform/), or [AWS](/enterprise_influxdb/v1.7/install-and-deploy/aws/).
|
||||
> **Note:** If you're looking for cloud infrastructure and services, check out how to deploy InfluxDB Enterprise (production-ready) on a cloud provider of your choice: [Azure](/enterprise_influxdb/v1.7/install-and-deploy/azure/), [GCP](/enterprise_influxdb/v1.7/install-and-deploy/deploying/google-cloud-platform/), or [AWS](/enterprise_influxdb/v1.7/install-and-deploy/aws/).
|
||||
|
|
|
|||
|
|
@ -16,15 +16,7 @@ deploy InfluxDB Enterprise in a production environment.
|
|||
The following steps will get you up and running with the first essential component of
|
||||
your InfluxDB Enterprise cluster: the meta nodes.
|
||||
|
||||
> If you wish to evaluate InfluxDB Enterprise in a non-production
|
||||
environment, feel free to follow the instructions outlined in the
|
||||
[QuickStart installation](/enterprise_influxdb/v1.7/install-and-deploy/quickstart_installation) section.
|
||||
Please note that if you install InfluxDB Enterprise with the QuickStart Installation process you
|
||||
will need to reinstall InfluxDB Enterprise with the Production Installation
|
||||
process before using the product in a production environment.
|
||||
|
||||
<br>
|
||||
# Meta node setup description and requirements
|
||||
## Meta node setup description and requirements
|
||||
|
||||
The Production Installation process sets up three [meta nodes](/enterprise_influxdb/v1.7/concepts/glossary/#meta-node), with each meta node running on its own server.
|
||||
<br>
|
||||
|
|
@ -61,9 +53,8 @@ If the meta nodes cannot reach `portal.influxdata.com` on port `80` or `443`,
|
|||
you'll need to set the `license-path` setting instead of the `license-key`
|
||||
setting in the meta node configuration file.
|
||||
|
||||
<br>
|
||||
# Meta node setup
|
||||
## Step 1: Add appropriate DNS entries for each of your servers
|
||||
## Meta node setup
|
||||
### Step 1: Add appropriate DNS entries for each of your servers
|
||||
|
||||
Ensure that your servers' hostnames and IP addresses are added to your network's DNS environment.
|
||||
The addition of DNS entries and IP assignment is usually site and policy specific; contact your DNS administrator for assistance as necessary.
|
||||
|
|
@ -91,27 +82,27 @@ Resolve any connectivity issues before proceeding with the installation.
|
|||
A healthy cluster requires that every meta node can communicate with every other
|
||||
meta node.
|
||||
|
||||
## Step 2: Set up, configure, and start the meta services
|
||||
### Step 2: Set up, configure, and start the meta services
|
||||
|
||||
Perform the following steps on each meta server.
|
||||
|
||||
### I. Download and install the meta service
|
||||
#### I. Download and install the meta service
|
||||
|
||||
#### Ubuntu & Debian (64-bit)
|
||||
##### Ubuntu & Debian (64-bit)
|
||||
|
||||
```
|
||||
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.7.10-c1.7.10_amd64.deb
|
||||
sudo dpkg -i influxdb-meta_1.7.10-c1.7.10_amd64.deb
|
||||
```
|
||||
|
||||
#### RedHat & CentOS (64-bit)
|
||||
##### RedHat & CentOS (64-bit)
|
||||
|
||||
```
|
||||
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.7.10_c1.7.10.x86_64.rpm
|
||||
sudo yum localinstall influxdb-meta-1.7.10_c1.7.10.x86_64.rpm
|
||||
```
|
||||
|
||||
#### Verify the authenticity of release download (recommended)
|
||||
##### Verify the authenticity of release download (recommended)
|
||||
|
||||
For added security, follow these steps to verify the signature of your InfluxDB download with `gpg`.
|
||||
|
||||
|
|
@ -140,7 +131,7 @@ For added security, follow these steps to verify the signature of your InfluxDB
|
|||
gpg: Good signature from "InfluxDB Packaging Service <support@influxdb.com>" [unknown]
|
||||
```
|
||||
|
||||
### II. Edit the configuration file
|
||||
#### II. Edit the configuration file
|
||||
|
||||
In `/etc/influxdb/influxdb-meta.conf`:
|
||||
|
||||
|
|
@ -155,7 +146,7 @@ The `license-key` and `license-path` settings are mutually exclusive and one mus
|
|||
```
|
||||
# Hostname advertised by this host for remote addresses. This must be resolvable by all
|
||||
# other nodes in the cluster
|
||||
hostname="<enterprise-meta-0x>"
|
||||
hostname="<enterprise-meta-0x>"
|
||||
|
||||
[enterprise]
|
||||
# license-key and license-path are mutually exclusive, use only one and leave the other blank
|
||||
|
|
@ -165,7 +156,7 @@ hostname="<enterprise-meta-0x>"
|
|||
license-path = "/path/to/readable/JSON.license.file" # Mutually exclusive with license-key
|
||||
```
|
||||
|
||||
### III. Start the meta service
|
||||
#### III. Start the meta service
|
||||
|
||||
On sysvinit systems, enter:
|
||||
```
|
||||
|
|
@ -195,7 +186,7 @@ must pass the `-single-server flag` when starting the single meta node.
|
|||
Please note that a cluster with only one meta node is **not** recommended for
|
||||
production environments.
|
||||
|
||||
## Step 3: Join the meta nodes to the cluster
|
||||
### Step 3: Join the meta nodes to the cluster
|
||||
|
||||
From one and only one meta node, join all meta nodes including itself.
|
||||
In our example, from `enterprise-meta-01`, run:
|
||||
|
|
|
|||
|
|
@ -10,10 +10,6 @@ menu:
|
|||
weight: 20
|
||||
---
|
||||
|
||||
To get up and running with InfluxDB Enterprise, complete the following tasks:
|
||||
Get up and running with InfluxDB Enterprise:
|
||||
|
||||
## [Download InfluxDB Enterprise](/enterprise_influxdb/v1.7/introduction/download/)
|
||||
|
||||
## [Install InfluxDB Enterprise](/enterprise_influxdb/v1.7/introduction/installation_guidelines/)
|
||||
|
||||
## [Get started with InfluxDB Enterprise](/enterprise_influxdb/v1.7/introduction/getting-started/)
|
||||
{{< children >}}
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ menu:
|
|||
**Known issues**
|
||||
|
||||
* [Why do I see entropy when rebalancing shards?]
|
||||
(#why-do-I-see-entropy-when-rebalancing-shards?)
|
||||
(#why-do-i-see-entropy-when-rebalancing-shards)
|
||||
|
||||
**Log errors**
|
||||
|
||||
|
|
|
|||
|
|
@ -420,7 +420,7 @@ The unintended data, however, include only the metastore information, not the sh
|
|||
|
||||
InfluxDB Enterprise introduced incremental backups in version 1.2.0.
|
||||
To restore a backup created prior to version 1.2.0, be sure to follow the syntax
|
||||
for [restoring from a full backup](#syntax-to-restore-from-a-full-backup).
|
||||
for [restoring from a full backup](#restore-from-a-full-backup).
|
||||
|
||||
## Exporting and importing data
|
||||
|
||||
|
|
|
|||
|
|
@ -454,7 +454,6 @@ Shard 21179 removed from repair queue
|
|||
|
||||
Joins a meta node and/or data node to a cluster.
|
||||
By default, `influxd-ctl` joins the local meta node and/or data node into a new cluster.
|
||||
Use `join` instead of the [`add-meta`](#add-meta) or [`add-data`](#add-data) arguments when performing a [QuickStart Installation](/enterprise_influxdb/v1.8/quickstart_installation/cluster_installation/) of an InfluxDB Enterprise cluster.
|
||||
|
||||
#### Syntax
|
||||
|
||||
|
|
@ -475,8 +474,6 @@ Print verbose information about the join.
|
|||
Address of a meta node in an existing cluster.
|
||||
Use this argument to add the un-joined meta node and/or data node to an existing cluster.
|
||||
|
||||
Resources: [QuickStart installation](/enterprise_influxdb/v1.8/quickstart_installation/cluster_installation/)
|
||||
|
||||
#### Examples
|
||||
|
||||
##### Join a meta and data node into a cluster
|
||||
|
|
@ -593,9 +590,9 @@ Killed shard copy 39 from cluster-data-node-02:8088 to cluster-data-node-03:8088
|
|||
### `leave`
|
||||
|
||||
Removes a meta node and/or data node from the cluster.
|
||||
Use `leave` instead of the [`remove-meta`](#remove-meta) and [`remove-data`](#remove-data) arguments if you set up your InfluxDB Enterprise cluster with the [QuickStart Installation](/enterprise_influxdb/v1.8/quickstart_installation/cluster_installation/) process.
|
||||
|
||||
{{% warn %}}The `leave` argument is destructive; it erases all metastore information from meta nodes and all data from data nodes.
|
||||
{{% warn %}}
|
||||
The `leave` argument is destructive; it erases all metastore information from meta nodes and all data from data nodes.
|
||||
Use `leave` only if you want to *permanently* remove a node from a cluster.
|
||||
{{% /warn %}}
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ menu:
|
|||
|
||||
|
||||
* [Logging locations](#logging-locations)
|
||||
* [Redirect HTTP request logging](#redirect-http-request-logging)
|
||||
* [Redirect HTTP request logging](#redirect-http-access-logging)
|
||||
* [Structured logging](#structured-logging)
|
||||
* [Tracing](#tracing)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Upgrade InfluxDB Enterprise clusters
|
||||
description: Upgrade to the latest version of InfluxDB Enterprise.
|
||||
description: Upgrade to the latest version of InfluxDB Enterprise.
|
||||
aliases:
|
||||
- /enterprise/v1.8/administration/upgrading/
|
||||
menu:
|
||||
|
|
@ -68,7 +68,7 @@ sudo yum localinstall influxdb-meta-1.8.0_c1.8.0.x86_64.rpm
|
|||
|
||||
Migrate any custom settings from your previous meta node configuration file.
|
||||
|
||||
To enable HTTPS, you must update the meta node configuration file (`influxdb-meta.conf`). For information, see [Enable HTTPS within the configuration file for each Meta Node](/enterprise_influxdb/v1.8/guides/https_setup/#step-3-enable-https-within-the-configuration-file-for-each-meta-node).
|
||||
To enable HTTPS, you must update the meta node configuration file (`influxdb-meta.conf`). For information, see [Enable HTTPS within the configuration file for each Meta Node](/enterprise_influxdb/v1.8/guides/https_setup/#set-up-https-in-an-influxdb-enterprise-cluster).
|
||||
|
||||
### Restart the `influxdb-meta` service
|
||||
|
||||
|
|
@ -165,7 +165,7 @@ sudo yum localinstall influxdb-data-1.8.0_c1.8.0.x86_64.rpm
|
|||
|
||||
Migrate any custom settings from your previous data node configuration file.
|
||||
|
||||
- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](/enterprise_influxdb/v1.8/guides/https_setup/#step-4-enable-https-within-the-configuration-file-for-each-data-node).
|
||||
- To enable HTTPS, see [Enable HTTPS within the configuration file for each Data Node](/enterprise_influxdb/v1.8/guides/https_setup/#set-up-https-in-an-influxdb-enterprise-cluster).
|
||||
|
||||
- To enable TSI, open `/etc/influxdb/influxdb.conf`, and then adjust and save the settings shown in the following table.
|
||||
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ For information about installing and setting up meta nodes, see
|
|||
|
||||
{{% note %}}
|
||||
#### Add the OSS instance to the meta /etc/hosts files
|
||||
When [modifying the `/etc/hosts` file](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation/#step-1-modify-the-etc-hosts-file)
|
||||
When [modifying the `/etc/hosts` file](/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation/#step-1-add-appropriate-dns-entries-for-each-of-your-servers)
|
||||
on each meta node, include the IP and host name of your InfluxDB OSS instance so
|
||||
meta nodes can communicate with the OSS instance.
|
||||
{{% /note %}}
|
||||
|
|
|
|||
|
|
@ -57,15 +57,15 @@ curl -k https://localhost:8091/status
|
|||
|
||||
### Replace meta nodes in a functional cluster
|
||||
|
||||
If all meta nodes in the cluster are fully functional, simply follow the steps for [replacing meta nodes](#replacing-meta-nodes-in-an-influxdb-enterprise-cluster).
|
||||
If all meta nodes in the cluster are fully functional, simply follow the steps for [replacing meta nodes](#replace-meta-nodes-in-an-influxdb-enterprise-cluster).
|
||||
|
||||
### Replace an unresponsive meta node
|
||||
|
||||
If replacing a meta node that is either unreachable or unrecoverable, you need to forcefully remove it from the meta cluster. Instructions for forcefully removing meta nodes are provided in the [step 2.2](#2-2-remove-the-non-leader-meta-node) of the [replacing meta nodes](#replacing-meta-nodes-in-an-influxdb-enterprise-cluster) process.
|
||||
If replacing a meta node that is either unreachable or unrecoverable, you need to forcefully remove it from the meta cluster. Instructions for forcefully removing meta nodes are provided in the [step 2.2](#2-2-remove-the-non-leader-meta-node) of the [replacing meta nodes](#replace-meta-nodes-in-an-influxdb-enterprise-cluster) process.
|
||||
|
||||
### Replace responsive and unresponsive data nodes in a cluster
|
||||
|
||||
The process of replacing both responsive and unresponsive data nodes is the same. Simply follow the instructions for [replacing data nodes](#replacing-data-nodes-in-an-influxdb-enterprise-cluster).
|
||||
The process of replacing both responsive and unresponsive data nodes is the same. Simply follow the instructions for [replacing data nodes](#replace-data-nodes-in-an-influxdb-enterprise-cluster).
|
||||
|
||||
### Reconnect a data node with a failed disk
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ This guide requires the following:
|
|||
- Microsoft Azure account with access to the [Azure Marketplace](https://azuremarketplace.microsoft.com/).
|
||||
- SSH access to cluster instances.
|
||||
|
||||
To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deploy InfluxDB Enterprise](/enterprise_influxdb/v1.8/install-and-deploy/_index).
|
||||
To deploy InfluxDB Enterprise clusters on platforms other than Azure, see [Deploy InfluxDB Enterprise](/enterprise_influxdb/v1.8/install-and-deploy/).
|
||||
|
||||
## Deploy a cluster
|
||||
|
||||
|
|
|
|||
|
|
@ -16,15 +16,7 @@ deploy InfluxDB Enterprise in a production environment.
|
|||
The following steps will get you up and running with the first essential component of
|
||||
your InfluxDB Enterprise cluster: the meta nodes.
|
||||
|
||||
> If you wish to evaluate InfluxDB Enterprise in a non-production
|
||||
environment, feel free to follow the instructions outlined in the
|
||||
[QuickStart installation](/enterprise_influxdb/v1.8/install-and-deploy/quickstart_installation) section.
|
||||
Please note that if you install InfluxDB Enterprise with the QuickStart Installation process you
|
||||
will need to reinstall InfluxDB Enterprise with the Production Installation
|
||||
process before using the product in a production environment.
|
||||
|
||||
<br>
|
||||
# Meta node setup description and requirements
|
||||
## Meta node setup description and requirements
|
||||
|
||||
The Production Installation process sets up three [meta nodes](/enterprise_influxdb/v1.8/concepts/glossary/#meta-node), with each meta node running on its own server.
|
||||
<br>
|
||||
|
|
@ -65,9 +57,8 @@ setting in the meta node configuration file.
|
|||
|
||||
The installation package creates an `influxdb` user used to run the influxdb meta service. The `influxdb` user also owns certain files needed to start the service. In some cases, local policies may prevent the local user account from being created and the service fails to start. Contact your systems administrator for assistance with this requirement.
|
||||
|
||||
<br>
|
||||
# Meta node setup
|
||||
## Step 1: Add appropriate DNS entries for each of your servers
|
||||
## Meta node setup
|
||||
### Step 1: Add appropriate DNS entries for each of your servers
|
||||
|
||||
Ensure that your servers' hostnames and IP addresses are added to your network's DNS environment.
|
||||
The addition of DNS entries and IP assignment is usually site and policy specific; contact your DNS administrator for assistance as necessary.
|
||||
|
|
@ -95,27 +86,27 @@ Resolve any connectivity issues before proceeding with the installation.
|
|||
A healthy cluster requires that every meta node can communicate with every other
|
||||
meta node.
|
||||
|
||||
## Step 2: Set up, configure, and start the meta services
|
||||
### Step 2: Set up, configure, and start the meta services
|
||||
|
||||
Perform the following steps on each meta server.
|
||||
|
||||
### I. Download and install the meta service
|
||||
#### I. Download and install the meta service
|
||||
|
||||
#### Ubuntu & Debian (64-bit)
|
||||
##### Ubuntu & Debian (64-bit)
|
||||
|
||||
```
|
||||
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.8.0-c1.8.0_amd64.deb
|
||||
sudo dpkg -i influxdb-meta_1.8.0-c1.8.0_amd64.deb
|
||||
```
|
||||
|
||||
#### RedHat & CentOS (64-bit)
|
||||
##### RedHat & CentOS (64-bit)
|
||||
|
||||
```
|
||||
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.8.0_c1.8.0.x86_64.rpm
|
||||
sudo yum localinstall influxdb-meta-1.8.0_c1.8.0.x86_64.rpm
|
||||
```
|
||||
|
||||
#### Verify the authenticity of release download (recommended)
|
||||
##### Verify the authenticity of release download (recommended)
|
||||
|
||||
For added security, follow these steps to verify the signature of your InfluxDB download with `gpg`.
|
||||
|
||||
|
|
@ -144,7 +135,7 @@ For added security, follow these steps to verify the signature of your InfluxDB
|
|||
gpg: Good signature from "InfluxDB Packaging Service <support@influxdb.com>" [unknown]
|
||||
```
|
||||
|
||||
### II. Edit the configuration file
|
||||
#### II. Edit the configuration file
|
||||
|
||||
In `/etc/influxdb/influxdb-meta.conf`:
|
||||
|
||||
|
|
@ -159,7 +150,7 @@ The `license-key` and `license-path` settings are mutually exclusive and one mus
|
|||
```
|
||||
# Hostname advertised by this host for remote addresses. This must be resolvable by all
|
||||
# other nodes in the cluster
|
||||
hostname="<enterprise-meta-0x>"
|
||||
hostname="<enterprise-meta-0x>"
|
||||
|
||||
[enterprise]
|
||||
# license-key and license-path are mutually exclusive, use only one and leave the other blank
|
||||
|
|
@ -169,7 +160,7 @@ hostname="<enterprise-meta-0x>"
|
|||
license-path = "/path/to/readable/JSON.license.file" # Mutually exclusive with license-key
|
||||
```
|
||||
|
||||
### III. Start the meta service
|
||||
#### III. Start the meta service
|
||||
|
||||
On sysvinit systems, enter:
|
||||
```
|
||||
|
|
@ -199,7 +190,7 @@ must pass the `-single-server flag` when starting the single meta node.
|
|||
Please note that a cluster with only one meta node is **not** recommended for
|
||||
production environments.
|
||||
|
||||
## Step 3: Join the meta nodes to the cluster
|
||||
### Step 3: Join the meta nodes to the cluster
|
||||
|
||||
From one and only one meta node, join all meta nodes including itself.
|
||||
In our example, from `enterprise-meta-01`, run:
|
||||
|
|
|
|||
|
|
@ -10,10 +10,6 @@ menu:
|
|||
weight: 20
|
||||
---
|
||||
|
||||
To get up and running with InfluxDB Enterprise, complete the following tasks:
|
||||
Get up and running with InfluxDB Enterprise:
|
||||
|
||||
## [Download InfluxDB Enterprise](/enterprise_influxdb/v1.8/introduction/download/)
|
||||
|
||||
## [Install InfluxDB Enterprise](/enterprise_influxdb/v1.8/introduction/installation_guidelines/)
|
||||
|
||||
## [Get started with InfluxDB Enterprise](/enterprise_influxdb/v1.8/introduction/getting-started/)
|
||||
{{< children >}}
|
||||
|
|
|
|||
|
|
@ -4,6 +4,6 @@
|
|||
<span class="expand-toggle"></span><span>{{ $expandLabel }}</span>
|
||||
</p>
|
||||
<div class="expand-content" style="display: none;" >
|
||||
{{ .Inner | safeHTML}}
|
||||
{{ .Inner | markdownify | safeHTML }}
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in New Issue