<commit_before>---
title: Step 2 - Data Node Installation
menu:
  enterprise_1_0:
    weight: 20
    parent: Introduction
---

InfluxEnterprise offers highly scalable clusters on your infrastructure
and a management UI for working with clusters.
The next steps will get you up and running with the second essential component of
your InfluxEnterprise cluster: the data nodes.

If you have not set up your meta nodes, please visit
[Meta Node Installation](/enterprise/v1.0/introduction/meta_node_installation/).
Bad things can happen if you complete the following steps without meta nodes.

# Requirements

To get started, you'll need the license key that you received at
[InfluxPortal](https://portal.influxdata.com/) as well as several servers.
The steps below set up two
[data nodes](/enterprise/v1.0/concepts/glossary#data-node) with each data node
on its own server.

Please note that there is no requirement to use that number of servers.
The data processes can run on the same or different servers.
For high availability and redundancy your cluster should have at least two
data nodes.
See the
[Clustering Guide](/enterprise/v1.0/concepts/clustering.md#optimal-server-counts)
for more on cluster architecture.

The data node servers will need to be able to reach `portal.influxdata.com`
on port `80` or `443`.
If the data nodes cannot reach `portal.influxdata.com` on port `80` or `443`,
the configuration section describes how to use a license file.

> **Note:** By default, data and meta nodes communicate with each other on
ports `8091` and `8088`.
In a clustered setup you’ll want to configure a load balancer to send client
traffic to the data nodes on port `8086`, the default port for the
[HTTP API](https://docs.influxdata.com/influxdb/v1.0/tools/api/) for writing and
querying data.

# Data Node Setup

## Modify the /etc/hosts file

Add your servers' hostnames and IP addresses to **each** cluster server's `/etc/hosts`
file (the hostnames are representative):

```
<Data_1_IP> enterprise-data-01
<Data_2_IP> enterprise-data-02
```<commit_msg>Update data_node_installation.md<commit_after>---
title: Step 2 - Data Node Installation
menu:
  enterprise_1_0:
    weight: 20
    parent: Introduction
---

InfluxEnterprise offers highly scalable clusters on your infrastructure
and a management UI for working with clusters.
The next steps will get you up and running with the second essential component of
your InfluxEnterprise cluster: the data nodes.

If you have not set up your meta nodes, please visit
[Meta Node Installation](/enterprise/v1.0/introduction/meta_node_installation/).
Bad things can happen if you complete the following steps without meta nodes.

# Requirements

To get started, you'll need the license key that you received at
[InfluxPortal](https://portal.influxdata.com/) as well as several servers.
The steps below set up two
[data nodes](/enterprise/v1.0/concepts/glossary#data-node) with each data node
on its own server.

Please note that there is no requirement to use that number of servers.
The data processes can run on the same or different servers.
For high availability and redundancy your cluster should have at least two
data nodes.
See the
[Clustering Guide](/enterprise/v1.0/concepts/clustering.md#optimal-server-counts)
for more on cluster architecture.

The data node servers will need to be able to reach `portal.influxdata.com`
on port `80` or `443`.
If the data nodes cannot reach `portal.influxdata.com` on port `80` or `443`,
the configuration section describes how to use a license file.

> **Note:** By default, data and meta nodes communicate with each other on
ports `8088`, `8089`, and `8091`.
In a clustered setup you’ll want to configure a load balancer to send client
traffic to the data nodes on port `8086`, the default port for the
[HTTP API](https://docs.influxdata.com/influxdb/v1.0/tools/api/) for writing and
querying data.

# Data Node Setup

## Modify the /etc/hosts file

Add your servers' hostnames and IP addresses to **each** cluster server's `/etc/hosts`
file (the hostnames are representative):

```
<Data_1_IP> enterprise-data-01
<Data_2_IP> enterprise-data-02
```
{'fraction_non_alphanumeric': 0.07697876447876448, 'fraction_numerical': 0.020752895752895753, 'mean_word_length': 4.541443850267379, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 9, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2368512', 'n_tokens_mistral': 1233, 'n_tokens_neox': 1162, 'n_words': 556}