Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated DNS and user account information 

Removed reference to /etc/hosts file and added local user account requirements
pull/1387/head
mdevy-influxdata 2020-08-14 16:05:39 -07:00 committed by Scott Anderson
parent 7d4047e26f
commit a08b2b7201
1 changed files with 16 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
content/enterprise_influxdb/v1.8/install-and-deploy/production_installation/data_node_installation.md
View File

@ -59,16 +59,21 @@ InfluxDB Enterprise does not function as a load balancer.
You will need to configure your own load balancer to send client traffic to the
data nodes on port `8086` (the default port for the [HTTP API](/influxdb/v1.8/tools/api/)).
#### User account
The installation package creates user `influxdb` that is used to run the influxdb data service. `influxdb` user also owns certain files that are needed for the service to start successfully. 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.
# Data node setup
## Step 1: Add appropriate DNS entries for each of your servers
## Step 1: Modify the `/etc/hosts` file
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.
Ultimately, use entries similar to the following (hostnames and domain IP addresses are representative).
Add your servers' hostnames and IP addresses to **each** cluster server's `/etc/hosts`
file (the hostnames below are representative).
```
<Data_1_IP> enterprise-data-01
<Data_2_IP> enterprise-data-02
| Record Type | Hostname | IP |
|:------------|:-------------------------------------:|------------------:|
| A | ```enterprise-data-01.mydomain.com``` | ```<Data_1_IP>``` |
| A | ```enterprise-data-02.mydomain.com``` | ```<Data_2_IP>``` |
```
> **Verification steps:**
@ -82,10 +87,10 @@ servers are resolvable. Here is an example set of shell commands using `ping`:
ping -qc 1 enterprise-data-01
ping -qc 1 enterprise-data-02
If there are any connectivity issues resolve them before proceeding with the
installation.
A healthy cluster requires that every meta and data node can communicate
with every other meta and data node.
We highly recommend that each server be able to resolve the IP from the hostname alone as shown here.
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 data node services