Functions

Cluster Management

• Creating a cluster: You can create CloudTable HBase, ClickHouse, or Doris clusters as required.
  • Pay-per-use: This mode provides instant availability and is suitable for short-term use.
  • Yearly/Monthly: You can purchase yearly/monthly clusters. This mode is recommended for long-term users.
• Connecting to a cluster: There are multiple methods for you to connect to an HBase, ClickHouse, or Doris cluster after the cluster is created.
• Restarting a cluster: Restarting a cluster may cause data loss in running services. If you have to restart a cluster, ensure that there is no running service and all data has been saved.
• Deleting a cluster: You can delete a cluster that is no longer needed. Deleting a cluster is risky and may cause data loss. Therefore, exercise caution when performing this operation.
• Restarting a node: If a CloudTable cluster node is abnormal, you can restart the node to restore the node status.

Cluster O&M

• Capacity adjustment: As the service volume increases, the current cluster specifications may not meet service requirements. In this case, you can adjust the cluster capacity as required. You can expand the capacity through node scaling, specification change, and disk capacity expansion.
• Monitoring and alarm reporting
  • Monitoring: CloudTable interconnects with Cloud Eye, which is critical to ensure CloudTable reliability, availability, and performance. You can monitor the running status of CloudTable servers.
  • Alarm reporting: Alarm management includes viewing and configuring alarm rules and subscribing to alarm information. In alarm rules, you can check the alarm statistics and details of the past week. This feature monitors common CloudTable alarms with pre-set rules and allows users to customize the alarm thresholds based on their service needs.
• Parameter configuration: To meet actual service requirements, you can modify cluster parameters on the CloudTable console to tune cluster performance.
• Cluster log management:
  • Cluster logs are collected and sent to Log Tank Service (LTS). You can check or dump the collected cluster logs on LTS.
  • CloudTable uses Cloud Trace Service (CTS) to record operations associated with CloudTable for later query, audit, and backtrack operations.

Cold and Hot Data Separation

For data analysis, it is common to query hot and cold data at varying frequencies and response speed. Storing all data locally as historical data grows can lead to resource waste. The cold and hot data separation feature enables cold and hot data to be stored separately on storage media with different costs. This not only accelerates query speeds and responsiveness for hot data but also cuts down on storage costs for cold data. Additionally, this feature offers adaptable configurations to align with the specific demands of various service scenarios. Hot and cold data is classified based on the data access frequency and update frequency.

• Hot data: This type of data experiences frequent access and updates. It is likely to be needed in future operations and demands swift response times due to its active nature.
• Cold data: In contrast, cold data is characterized by its static state; it is rarely updated or accessed and has minimal requirements for response speed.

User Permissions Configuration

User permissions management enables unified management of users, roles, and permissions on each node in the cluster. You can create roles, create users, and bind users to roles on the console to control user permissions. Operations of different users do not affect each other, improving service efficiency. For details, see Configuring Doris User Permissions and Configuring ClickHouse User Permissions.