From 4dedca8d54f73ec74b9e85a69d50ee839927a950 Mon Sep 17 00:00:00 2001 From: Bill Maxwell Date: Mon, 10 Jun 2019 11:59:41 -0700 Subject: [PATCH] Added link from RKE install page Also added cluster.yml reference. --- .../v2.x/en/installation/ha/kubernetes-rke/_index.md | 2 ++ .../v2.x/en/installation/options/etcd/_index.md | 10 ++++++++-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md b/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md index 88dbcb7e8f9..b57911e5fb2 100644 --- a/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md +++ b/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md @@ -52,6 +52,8 @@ RKE has many configuration options for customizing the install to suit your spec Please see the [RKE Documentation]({{< baseurl >}}/rke/latest/en/config-options/) for the full list of options and capabilities. +For tuning your etcd cluster for larger Rancher installations see the [etcd settings guide]({{< baseurl >}}/rancher/v2.x/en/installation/options/etcd/). + ### Run RKE ``` diff --git a/content/rancher/v2.x/en/installation/options/etcd/_index.md b/content/rancher/v2.x/en/installation/options/etcd/_index.md index 8209b3fef47..33357564133 100644 --- a/content/rancher/v2.x/en/installation/options/etcd/_index.md +++ b/content/rancher/v2.x/en/installation/options/etcd/_index.md @@ -12,19 +12,24 @@ The etcd data set is automatically cleaned up on a five minute interval by Kuber If you ever run into `mvcc: database space exceeded` errors, once you compact, defrag and disarm to recover you should consider increasing the keyspace to mitigate this issue. -**Example: This snippet increases the key space size to 5GB** +**Example: This snippet of the RKE cluster.yml file increases the key space size to 5GB** ```yaml +# RKE cluster.yml +... services: etcd: extra_args: quota-backend-bytes: 5368709120 +... ``` -## Scaling etcd Disk Performance ## +## Scaling etcd disk performance ## To reduce IO contention on the disks for etcd, you can split the data and WAL directories onto separate devices. To do so, you need to provision nodes with devices and format them before running etcd on them. Based on etcd best practices, mirroring array configurations are unnecessary because etcd replicates the data between the nodes. However, you can use stripping RAID configurations to increase the IOPS available to etcd. To configure dedicated arrays, you can configure this in the RKE cluster.yml file with the following snippet. ```yaml +# RKE cluster.yml +... services: etcd: extra_args: @@ -33,6 +38,7 @@ services: extra_binds: - "/var/lib/etcd/data:/var/lib/rancher/etcd/data" - "/var/lib/etcd/wal:/var/lib/rancher/etcd/wal" +... ``` For the solution above to work, this requires `/var/lib/etcd/data` and `/var/lib/etcd/wal` to be mounted and formated on the underlying host. Note the addition of the 'wall_dir' directory in the extra_args section. Without this directory being defined, etcd tries to modify the root directory and without sufficient permissions. \ No newline at end of file