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

OceanBase Database

KV - V4.3.5
  • OBKV overview
  • Architecture
  • OBKV-Table
    • Introduction to OBKV-Table
      • Overview
      • OBKV-Table operation types
      • Core features of OBKV-Table
      • Differences between replace and insert_or_update
      • Supported value types
      • OBKV-Table data models
    • Use the OBKV-Table Java client
      • Java development guide for OBKV-Table
      • Prepare for development with OBKV-Table
      • Use the OBKV-Table Java client to connect to a cluster
      • Set client parameters
      • Supported client interfaces
      • Use the OBKV-Table Java client
    • Use the OBKV-Table GO client
      • Use the OBKV-Table Go client to connect to a cluster
      • Overview of the Go client
      • Individual API operations
      • Batch operations
      • About queries
      • Aggregation API
      • Filters
    • FAQ
  • OBKV-HBase
    • Overview
    • OBKV-HBase core features
    • Compatibility with HBase
    • Deployment
    • Application development with OBKV-HBase
      • Overview of OBKV-HBase application development
      • Data model
      • Data model design
      • Connect to a cluster using the OBKV-HBase client
      • Migrate HBase business code to OBKV-HBase
      • Data operation examples
      • Delete expired data
    • OBKV-HBase migration guide
    • OBKV-HBase management
      • Overview
      • High availability
      • Security and permissions
      • Monitoring metrics
    • Performance test
    • OBKV-HBase integrations
      • Flink
        • Synchronize data to OBKV-HBase by using Flink
    • Views
    • FAQ

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Database
  3. KV
  4. V4.3.5

Overview

Last Updated:2026-09-29 10:40:08

Cluster management
Tenant management
Replica management
High availability
Security and permissions
Backup and restore
Logs
Monitoring metrics

This topic describes the O&M and management operations in OBKV-HBase.

Cluster management

An OBKV-HBase cluster is a normal OceanBase cluster for a MySQL tenant. The O&M and management operations on an OBKV-HBase cluster are the same as the general O&M and management operations on an OceanBase cluster.

For more information, see topics under Manage clusters.

Tenant management

An OBKV-HBase tenant is a normal MySQL tenant. The O&M and management operations on an OBKV-HBase tenant are the same as the general O&M and management operations on an OceanBase Database tenant.

For more information, see topics under Manage tenants.

Replica management

The replica O&M and management operations in OBKV-HBase are the same as the general replica O&M and management operations in OceanBase Database.

For more information, see topics under Manage replicas.

High availability

The high availability of OBKV-HBase relies on the high availability of the entire link, namely, the high availability of OBServer nodes, OceanBase Database Proxy (ODP), and the client on the link. OBKV-HBase inherits the high availability capability of OceanBase Database on the server side, and supports deployment for direction connection and connection through ODP respectively.

OceanBase Database provides a variety of technologies for ensuring high availability of services, including intra-cluster multi-replica disaster recovery, arbitration-based disaster recovery, and inter-cluster Physical Standby Database disaster recovery. For more information, see topics under High availability.

For more information about high availability of OBKV-HBase, see High availability.

Security and permissions

As the final data carrier, OceanBase Database prioritizes data security. OceanBase Database provides a full range of enterprise-level security features to ensure data security for users. The security features include identity authentication, access control, and data encryption.

For more information about security and permissions in OBKV-HBase, see Security and permissions.

Backup and restore

OBKV-HBase reuses the backup and restore capability of OceanBase Database.

For more information, see topics under Backup and restore.

Logs

For information about log levels and how to view logs, see topics under Logs.

Monitoring metrics

For information about monitoring metrics in OBKV-HBase, see Monitoring metrics.

Previous topic

OBKV-HBase migration guide
Last

Next topic

High availability
Next
on this page
Cluster management
Tenant management
Replica management
High availability
Security and permissions
Backup and restore
Logs
Monitoring metrics