In OceanBase Database, system management involves configuration management, storage management, memory management, process management, and disk management. For more information, see System management.
Configuration management
Function: Configuration management is used to adjust and optimize the running parameters of OceanBase Database, including system configuration items and system variables. Actions: By modifying system configuration items (such as memory_limit and cpu_count), you can control the resource usage and behavior of the database. System variables (such as sql_mode and time_zone) are used to adjust the behavior and results of SQL execution. Tools: You can perform configuration management through SQL statements or the OceanBase Cloud console.
Storage management
Function: Storage management is responsible for data storage and partition management, ensuring efficient data storage and access. Architecture: OceanBase Database uses an LSM-tree-based storage architecture. Data is divided into static baseline data (SSTable) and dynamic incremental data (MemTable). Data is first written to the MemTable and then flushed to the disk as an SSTable when it reaches a certain size. Partitions: OceanBase Database supports horizontal partitioning (such as HASH, RANGE, and LIST partitioning) and subpartitions. Data is distributed across nodes to ensure load balancing and high availability. Replicas: Each partition has multiple replicas, and the Paxos protocol is used to ensure data consistency and high availability.
Memory management
Function: Memory management is used to optimize memory usage in the database, ensuring efficient data operations and access. Architecture: OceanBase Database's memory is divided into system memory and tenant memory. System memory is used to run the database engine, while tenant memory is allocated to each tenant for storing incremental data (MemStore) and caching (KVCache). Multi-tenancy: Each tenant's memory is isolated. Administrators can allocate memory resources to tenants based on business needs. Monitoring: You can monitor memory usage through the OceanBase Cloud console and adjust memory allocation strategies as needed.
Process management
Function: Process management is responsible for monitoring and managing the processes of OceanBase Database to ensure stable service operation. Process types: The main processes include the OBServer process (responsible for the SQL engine, transaction engine, and storage engine) and the RootService process (responsible for cluster management and resource scheduling). High availability: The Paxos protocol is used to implement process high availability, ensuring that the standby process automatically takes over the service when the primary process fails.
Disk management
Function: Disk management is responsible for persistent data storage and disk resource allocation. Storage layer: Data is stored in SSTables and supports various compression algorithms to reduce storage costs. Disk monitoring: You can monitor disk usage through the console and perform disk expansion or data migration as needed. Backup and restore: Full backup, incremental backup, and log backup are supported to ensure data security and restore capability.