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

Merge branch 'master' into telegraf-v1.33.0

pull/5708/head
Scott Anderson 2024-12-16 10:09:34 -07:00 committed by GitHub
parent 6b50cf93a1 0d63cb833a
commit 53094a8a9d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 123 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
content/enterprise_influxdb/v1/administration/manage/clusters/rebalance.md
View File

@ -100,7 +100,7 @@ The following command lists every shard in our cluster:
influxd-ctl show-shards
```
The expected output is similar to the items in the codeblock below:
The output is similar to the following:
```
Shards
@ -134,16 +134,19 @@ Take note of the cold shard's `ID` (for example: `22`) and the TCP address of
one of its owners in the `Owners` column (for example:
`enterprise-data-01:8088`).
> **Note:**
>
Use the following command string to determine the size of the shards in
your cluster:
>
find /var/lib/influxdb/data/ -mindepth 3 -type d -exec du -h {} \;
> [!Note]
>
> To determine the size of shards in
> your cluster, enter the following command:
>
> ```bash
> find /var/lib/influxdb/data/ -mindepth 3 -type d -exec du -h {} \;
> ```
In general, we recommend moving larger shards to the new data node to increase the
available disk space on the original data nodes.
Users should note that moving shards will impact network traffic.
_Moving shards will impact network traffic._
### Step 3: Copy Cold Shards

38
content/enterprise_influxdb/v1/introduction/installation/meta_node_installation.md
View File

@ -47,11 +47,26 @@ for high availability and redundancy.
We typically recommend three meta nodes.
If your servers have chronic communication or reliability issues, you can try adding nodes.
{{% note %}}
Deploying multiple meta nodes on the same server is strongly discouraged
since it creates a larger point of potential failure if that particular server is unresponsive.
InfluxData recommends deploying meta nodes on relatively small footprint servers.
{{% /note %}}
> [!Note]
>
> #### Run meta nodes on separate servers
>
> Avoid deploying multiple meta nodes on the same server.
> Doing so increases the risk of failure if the server becomes unresponsive.
> InfluxData recommends deploying meta nodes on separate, low-resource servers
> to minimize risks and optimize performance.
>
> #### Using a single meta node for non-production environments
>
> Installing and running InfluxDB Enterprise on a single server, or node, is an
alternative to using [InfluxDB OSS 1.x](/influxdb/v1).
> To start a {{% product-name %}} cluster with a single meta node,
> pass the `-single-server flag` when starting the node.
>
> _A cluster with only one meta node is **not** recommended for
> production environments._
>
> For more information, see how to [install InfluxDB Enterprise on a single server](/enterprise_influxdb/v1/introduction/installation/single-server/).
_See [Clustering in InfluxDB Enterprise](/enterprise_influxdb/v1/concepts/clustering/)
for more information about cluster architecture._
@ -292,19 +307,12 @@ Run the following command to search for a running `influxdb-meta` process:
ps aux | grep -v grep | grep influxdb-meta
```
You should see output similar to:
The output is similar to the following:
```
influxdb 3207 0.8 4.4 483000 22168 ? Ssl 17:05 0:08 /usr/bin/influxd-meta -config /etc/influxdb/influxdb-meta.conf
```
{{% note %}}
It is possible to start the cluster with a single meta node but you
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.
{{% /note %}}
{{% /expand %}}
{{< /expand-wrapper >}}
@ -350,9 +358,9 @@ enterprise-meta-02:8091 {{< latest-patch >}}-c{{< latest-patch >}}
enterprise-meta-03:8091 {{< latest-patch >}}-c{{< latest-patch >}}
```
Note that your cluster must have at least three meta nodes.
_Your cluster must have at least three meta nodes.
If you do not see your meta nodes in the output, retry adding them to
the cluster.
the cluster._
{{% /expand %}}
{{< /expand-wrapper >}}

108
content/enterprise_influxdb/v1/introduction/installation/single-server.md
View File

@ -9,7 +9,7 @@ menu:
parent: Install
---
Installing and running InfluxDB Enterprise on a single server or node is an
Installing and running InfluxDB Enterprise on a single server, or node, is an
alternative to using [InfluxDB OSS 1.x](/influxdb/v1).
InfluxDB Enterprise provides advanced functionality such as
[LDAP authentication](/enterprise_influxdb/v1/administration/configure/security/ldap/),
@ -75,11 +75,11 @@ through server restarts.
## Set up, configure, and start the meta service
The InfluxDB Enterprise meta process oversees and manages the InfluxDB Enterprise
data process. In multi-node clusters, meta nodes manage data syncing and high
availability of data nodes. In a single-node installation, the meta process
data process. In multi-node clusters, meta nodes (typically 3 nodes) manage data syncing and high
availability of data nodes. In a single-server (single-node) installation, a meta process
and the accompanying [`influxd-ctl` utility](/enterprise_influxdb/v1/tools/influxd-ctl/)
still manage the "cluster", even though the meta and data processes exist on the
same server.
still manage the "cluster", but with a single meta node and the data
processes running on the same server.
1. **Download and install the InfluxDB Enterprise meta service**:
@ -174,10 +174,11 @@ The `license-key` and `license-path` settings are mutually exclusive and one mus
internal-shared-secret = "<internal-shared-secret>"
```
3. **Start the InfluxDB Enterprise meta service**:
3. **Start the InfluxDB Enterprise meta service in single-server mode**:
Run the command appropriate to your operating system's service manager.
<!-- Include the `-single-server` flag when starting the service. -->
Run the `start` command appropriate to your operating system's service manager.
In the command, include the `-single-server` flag, which ensures that the single meta node
is the leader and has all the metadata for the cluster.
{{< tabs-wrapper >}}
{{% tabs "small" %}}
@ -185,24 +186,93 @@ The `license-key` and `license-path` settings are mutually exclusive and one mus
[systemd](#)
{{% /tabs %}}
{{% tab-content %}}
<!-----------------------------BEGIN SYSVINIT---------------------------------->
Edit the `influxdb-meta` init script to include the `-single-server` flag:
<!-- Potential TODO: Add instructions for passing the -single-server flag to sysvinit -->
1. Open the init script for editing, for example:
```sh
service influxdb-meta start
```
```bash
sudo nano /etc/init.d/influxdb-meta
```
2. Find the section of the script that starts the `influxdb-meta` service and add the `-single-server` flag--for example:
```sh
case "$1" in
start)
echo "Starting InfluxDB Meta..."
/usr/bin/influxdb-meta -single-server &
;;
stop)
echo "Stopping InfluxDB Meta..."
killall influxdb-meta
;;
restart)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac
exit 0
```
3. Restart the service to apply the changes:
```bash
sudo service influxdb-meta restart
```
For more information about sysvinit and initscripts, see the [sysvinit](https://wiki.gentoo.org/wiki/Sysvinit) Gentoo Linux documentation.
<!-------------------------------END SYSVINIT---------------------------------->
{{% /tab-content %}}
{{% tab-content %}}
<!------------------------------BEGIN SYSTEMD---------------------------------->
Edit the `influxdb-meta` service unit file or a drop-in configuration file to
include the `-single-server` flag--for example:
<!-- Potential TODO: Add instructions for passing the -single-server flag to systemd -->
1. Use `systemctl edit` with the `--drop-in` option to create the drop-in configuration file for the service:
```sh
sudo systemctl start influxdb-meta
```
```bash
sudo systemctl edit --drop-in influxdb-meta
```
2. Add the following to the drop-in configuration file to include the -single-server flag in the startup command:
```systemd
[Service]
ExecStart=
ExecStart=/usr/bin/influxdb-meta -single-server
```
3. Start the service using `systemctl`:
```bash
sudo systemctl start influxdb-meta
```
4. Reload the Systemd Daemon: Reload the systemd daemon to apply the changes:
```bash
sudo systemctl daemon-reload
```
5. Start the service using systemctl:
```bash
sudo systemctl start influxdb-meta
```
For more information about systemd unit files, see the Arch Linux documentation
for [Writing unit files](https://wiki.archlinux.org/title/Systemd#Writing_unit_files)
<!--------------------------------END SYSTEMD---------------------------------->
{{% /tab-content %}}
{{< /tabs-wrapper >}}
4. **Ensure the `influxdb-meta` process is running**:
1. **Ensure the `influxdb-meta` process is running**:
Use `ps aux` to list running processes and `grep` to filter the list of
running process to those that contain `influxdb-meta` and filter out the
@ -218,7 +288,7 @@ sudo systemctl start influxdb-meta
influxdb 3207 0.8 4.4 483000 22168 ? Ssl 17:05 0:08 /usr/bin/influxd-meta -config /etc/influxdb/influxdb-meta.conf
```
5. **Use `influxd-ctl` to add the meta process to the InfluxDB Enterprise "cluster"**:
2. **Use `influxd-ctl` to add the meta process to the InfluxDB Enterprise "cluster"**:
```sh
influxd-ctl add-meta <your-host-name>:8091
@ -230,7 +300,7 @@ sudo systemctl start influxdb-meta
Added meta node x at <your-host-name>:8091
```
6. **Use `influxd-ctl` to verify the meta node was added to the InfluxDB Enterprise "cluster"**:
3. **Use `influxd-ctl` to verify the meta node was added to the InfluxDB Enterprise "cluster"**:
```sh
influxd-ctl show