Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs][yba] Update On-prem provider in 2.16 #17715

Merged
merged 5 commits into from
Jun 8, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
review comments
  • Loading branch information
ddhodge committed Jun 8, 2023
commit 9b2cd657e66da2696b910e3bdbd1afa6c8a59ef0
Original file line number Diff line number Diff line change
Expand Up @@ -557,6 +557,16 @@ As an alternative to setting crontab permissions, you can install systemd-specif
/bin/systemctl restart yb-collect_metrics, \
/bin/systemctl enable yb-collect_metrics, \
/bin/systemctl disable yb-collect_metrics, \
/bin/systemctl start yb-bind_check, \
/bin/systemctl stop yb-bind_check, \
/bin/systemctl restart yb-bind_check, \
/bin/systemctl enable yb-bind_check, \
/bin/systemctl disable yb-bind_check, \
/bin/systemctl start yb-controller, \
/bin/systemctl stop yb-controller, \
/bin/systemctl restart yb-controller, \
/bin/systemctl enable yb-controller, \
/bin/systemctl disable yb-controller, \
/bin/systemctl daemon-reload
```

Expand Down Expand Up @@ -748,8 +758,6 @@ As an alternative to setting crontab permissions, you can install systemd-specif
WantedBy=timers.target
```

1. For CentOS 7, ensure that you also add the following service files to the `/etc/systemd/system` directory (set their ownerships to the `yugabyte` user and 0644 permissions):

`yb-bind_check.service`

```sh
Expand Down Expand Up @@ -826,7 +834,7 @@ As an alternative to setting crontab permissions, you can install systemd-specif

As described in [Eliminate an unresponsive node](../../../manage-deployments/remove-nodes/), when a node enters an undesirable state, you can delete the node, with YugabyteDB Anywhere clearing up all the remaining artifacts except the `prometheus` and `yugabyte` user.

You can manually remove Yugabyte components from existing server images. Before attempting this, you have to determine whether or not YugabyteDB Anywhere is operational. If it is, you either need to delete the universe or delete the nodes from the universe.
You can manually remove YugabyteDB components from existing server images. Before attempting this, you have to determine whether or not YugabyteDB Anywhere is operational. If it is, you either need to delete the universe or delete the nodes from the universe.

To completely eliminate all traces of YugabyteDB Anywhere and configuration, you should consider reinstalling the operating system image (or rolling back to a previous image, if available).

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ If a virtual machine or a physical server in a universe reaches its end of life

![Unreachable Node Actions](/images/ee/node-actions-unreachable.png)

When this happens, new Master leaders are elected for the underlying data shards, but since the universe enters a partially under-replicated state, it would not be able to tolerate additional failures. To remedy the situation, you can eliminate the unreachable node by taking actions in the following sequence:
When this happens, new Master leaders are elected for the underlying data shards, but because the universe enters a partially under-replicated state, it would not be able to tolerate additional failures. To remedy the situation, you can eliminate the unreachable node by taking actions in the following sequence:

- Step 1: [Remove node](#remove-node)
- Step 2: [Start a new Master process](#start-a-new-master-process), if necessary
Expand Down Expand Up @@ -74,6 +74,7 @@ A typical universe has an RF of 3 or 5. At the end of the [node removal](#remove
![Start master](/images/yp/start-master.png)

When you execute the start Master action, YugabyteDB Anywhere performs the following:

1. Configures the Master on the subject node.

2. Starts a new Master process on the subject node (in Shell mode).
Expand All @@ -82,7 +83,6 @@ When you execute the start Master action, YugabyteDB Anywhere performs the follo

4. Updates the Master addresses g-flag on all other nodes to inform them of the new Master.


## Release node instance

To release the IP address associated with the **yb-15-aws-ys-n6** node, click its corresponding **Actions > Release Instance**. This changes the value in the **Status** column from **Removed** to **Decommissioned**.
Expand Down