OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

Kubernetes operator for OceanBase

V2.3.4Community Edition
  • Overview
  • Quick start
  • Deploy
  • Upgrade
  • User guide
    • Cluster management
      • Manage clusters
      • Create a cluster
      • Zone management
        • Add zones to a cluster
        • Delete zones from a cluster
      • Server management
        • Add OBServer nodes to zones
        • Delete OBServer nodes from zones
      • Upgrade a cluster
      • Manage parameters
      • Update resources
      • Delete a cluster
    • Tenant management
      • Manage tenants
      • Create a tenant
      • Modify tenant
        • Manage resources
        • Manage replicas
        • Modify other parameters
      • Delete a tenant
      • Perform tenant O&M operations
    • High availability
      • High availability
      • Recover from node failure
      • Back up a tenant
      • Restore data from a backup
      • Physical standby tenant
      • Inter K8s cluster management
  • Configure
  • Appendix
    • Deploy OceanBase Database and web app in a Kubernetes cluster
    • FAQ
  • Changelog

Download PDF

Document Feedback
  1. Documentation Center
  2. Kubernetes operator for OceanBase
  3. V2.3.4

Delete OBServer nodes from zones

Last Updated:2026-09-04 08:21:43

Prerequisites
Procedure

This topic describes how to scale in a cluster by removing OBServer nodes from zones in the cluster.

Prerequisites

  • The OceanBase cluster is in the Running state.
  • After the OBServer nodes are deleted, the cluster has sufficient resources for the units of tenants.

Procedure

Assume that the current cluster has three zones, zone1, zone2, and zone3, each zone contains two OBServer nodes, and you want to delete one OBServer node from each zone so that each zone contains one OBServer node.

  1. Open the obcluster.yaml configuration file and change the value of the replica parameter of each zone from 2 to 1.

    # For example, assume that an OceanBase cluster has three zones.
    topology:
      - zone: zone1
        replica: 2
      - zone: zone2
        replica: 2
      - zone: zone3
        replica: 2
    
    # Delete an OBServer node from each zone.
    topology:
      - zone: zone1
        replica: 1
      - zone: zone2
        replica: 1
      - zone: zone3
        replica: 1  
    
  2. Run the following command for the modification to take effect:

    kubectl apply -f obcluster.yaml
    
  3. Query the status of custom resources in the OceanBase cluster to check whether the operation succeeds. Run the following command to query the status of the OceanBase cluster.

kubectl get obclusters.oceanbase.oceanbase.com test -n oceanbase -o yaml

# obcluster desired output, only displays status here
status:
  image: oceanbase/oceanbase-cloud-native:4.2.0.0-101000032023091319
  obzones:
  - status: running
    zone: obcluster-1-zone1
  - status: running
    zone: obcluster-1-zone2
  - status: running
    zone: obcluster-1-zone3
  parameters: []
  status: running

Run the following command to check whether the number of OBServer nodes is correct and whether they are all in the Running state:

kubectl get observers.oceanbase.oceanbase.com -n oceanbase

# observer desired output, only displays status here
oceanbase     obcluster-1-zone1-7b0e9f7e7675   10.42.0.241   running   7h48m
oceanbase     obcluster-1-zone2-67f3d1fe0b40   10.42.0.251   running   28m
oceanbase     obcluster-1-zone3-914ef208ac46   10.42.0.252   running   28m

Previous topic

Add OBServer nodes to zones
Last

Next topic

Upgrade a cluster
Next
on this page
Prerequisites
Procedure