From 49e8eaad23a1a348d0585f9c53618fbd9782a3c8 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Fri, 8 Sep 2023 12:07:08 -0400 Subject: [PATCH] Edits to efm PR4788 --- product_docs/docs/efm/4/05_using_efm.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index 6a7c7601131..e12d056f786 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -81,7 +81,7 @@ When the new node joins the cluster, Failover Manager sends a notification to th If your Failover Manager cluster includes more than one standby server, you can use the `efm set-priority` command to influence the promotion priority of a standby node. Invoke the command on any existing member of the Failover Manager cluster, and specify a priority value after the IP address of the member. -For example, the following command instructs Failover Manager that the `acctg` cluster member that is monitoring `10.0.1.9` is the primary standby `(1)`: +For example, the following command instructs Failover Manager that the `acctg` cluster member that's monitoring `10.0.1.9` is the primary standby `(1)`: ```shell efm set-priority acctg 10.0.1.9 1 @@ -184,7 +184,7 @@ The command causes all Failover Manager agents to exit. Terminating the Failover ### Removing a node from a cluster -The `efm disallow-node` command removes the IP address of a node from the Failover Manager Allowed Node host list. Assume the identity of efm or the OS superuser on any existing node that is currently part of the running cluster. Then invoke the `efm disallow-node` command, specifying the cluster name and the IP address of the node: +The `efm disallow-node` command removes the IP address of a node from the Failover Manager Allowed Node host list. Assume the identity of efm or the OS superuser on any existing node that's currently part of the running cluster. Then invoke the `efm disallow-node` command, specifying the cluster name and the IP address of the node: `efm disallow-node
` @@ -265,9 +265,9 @@ After creating the `acctg.properties` and `sales.properties` files, create a ser ### RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, copy the service file `/usr/lib/systemd/system/edb-efm-4..service` to `/etc/systemd/system` with a new name that is unique for each cluster. +If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, copy the service file `/usr/lib/systemd/system/edb-efm-4..service` to `/etc/systemd/system` with a new name that's unique for each cluster. -For example, if you have two clusters named `acctg` and `sales` managed by Failover Manager 4.7, the unit file names might be `efm-acctg.service` and `efm-sales.service`, and they can be created with: +For example, if you have two clusters named `acctg` and `sales` managed by Failover Manager 4.7, the unit file names might be `efm-acctg.service` and `efm-sales.service`. You can create them with: ```shell cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-acctg.service @@ -277,7 +277,7 @@ cp /usr/lib/systemd/system/edb-efm-4.7.service /etc/systemd/system/efm-sales.ser Then use `systemctl edit` to edit the `CLUSTER` variable in each unit file, changing the specified cluster name from `efm` to the new cluster name. Also update the value of the `PIDfile` parameter to match the new cluster name. -In our example, edit the `acctg` cluster by running `systemctl edit efm-acctg.service` and write: +In this example, edit the `acctg` cluster by running `systemctl edit efm-acctg.service` and write: ```ini [Service] @@ -285,7 +285,7 @@ Environment=CLUSTER=acctg PIDFile=/run/efm-4.7/acctg.pid ``` -And edit the `sales` cluster by running `systemctl edit efm-sales.service` and write: +Edit the `sales` cluster by running `systemctl edit efm-sales.service` and write: ```ini [Service] @@ -294,7 +294,7 @@ PIDFile=/run/efm-4.7/sales.pid ``` !!!Note -You could also have edited the files in `/etc/systemd/system` directly, but then you'll have to run `systemctl daemon-reload`, which is unecessary when using `systemd edit` to change the override files. +You can also edit the files in `/etc/systemd/system` directly, but then you have to run `systemctl daemon-reload`. This step is unecessary when using `systemd edit` to change the override files. !!! After saving the changes, enable the services: