DBService Basic Principles
Overview
DBService is a HA storage system for relational databases, which is applicable to the scenario where a small amount of data (about 10 GB) needs to be stored, for example, component metadata. DBService can only be used by internal components of a cluster and provides data storage, query, and deletion functions.
DBService is a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, CDL, Flink, HuteEngine, Kafka, Metadata, and Ranger store their metadata in DBService, and provide the metadata backup and restoration functions using DBService.
DBService Architecture
DBService in the cluster works in active/standby mode. Two DBServer instances are deployed and each instance contains three modules: HA, Database, and FloatIP.
Figure 1 shows the DBService logical architecture.
Table 1 describes the modules shown in Figure 1
|
Name |
Description |
|---|---|
|
HA |
HA management module. The active/standby DBServer uses the HA module for management. |
|
Database |
Database module. This module stores the metadata of the Client module. |
|
FloatIP |
Floating IP address that provides the access function externally. It is enabled only on the active DBServer instance and is used by the Client module to access Database. |
|
Client |
Client using the DBService component, which is deployed on the component instance node. The client connects to the database by using FloatIP and then performs metadata adding, deleting, and modifying operations. |
Relationship Between DBService and Other Components
DBService is a basic component of a cluster. Components such as Hive, Hue, Oozie, Metadata, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions using DBService.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
