Show Table of Contents
6.3.6. Removing Nodes from Districts
If many gears on a node host become idle over time, you can compact the district by decommissioning or re-purposing the node host. Use the
oo-admin-ctl-district and oo-admin-move commands in combination to remove the gears from the node host, and then remove the host from its district.
Procedure 6.4. To Remove Nodes from Districts:
The following steps demonstrate an example situation where district
small_district has two node hosts, node1.example.com and node2.example.com. The second node host, node2.example.com, has a high number of idle gears.
- Run the following commands and fix any problems that are found. This prevents future problems caused by moving a broken gear. On the broker host, run:
#
oo-admin-chkOn the node hosts, run:#
oo-accept-node - Deactivate the node you want to remove to prevent applications from being created on or moved to the node. Existing gears continue running. On the broker host, run:
#
oo-admin-ctl-district -c deactivate-node -n small_district -i node2.example.com - Move all the gears from
node2.example.comtonode1.example.comby repeating the following command on the broker host for each gear onnode2.example.com:#
oo-admin-move --gear_uuid UUID -i node1.example.com - Remove
node2.example.comfrom the district:#
oo-admin-ctl-district -c remove-node -n small_district -i node2.example.com

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.