Search

6.3.6. Removing Nodes from Districts

download PDF
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.
  1. 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-chk
    On the node hosts, run:
    # oo-accept-node
  2. 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
  3. Move all the gears from node2.example.com to node1.example.com by repeating the following command on the broker host for each gear on node2.example.com:
    # oo-admin-move --gear_uuid UUID -i node1.example.com
  4. Remove node2.example.com from the district:
    # oo-admin-ctl-district -c remove-node -n small_district -i node2.example.com
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.