Distributed Data Management ​

Distributed data management leverages distributed virtual bus to manage application data and user data distributed on different devices. Under such management, user data is no longer bound to a single physical device, service logic is decoupled from storage, and applications are running across devices.

Distributed data management is ported from the upstream OpenHarmony 3.2 Release. It consists of the following components.

For more information about distributed data management, see section Data Management in the OpenHarmony document .

Installation ​

Distributed data management has been integrated in openEuler 22.03 LTS SP4 by default. You can directly install it.

dnf install distributeddatamgr_kv_store distributeddatamgr_relational_store distributeddatamgr_datamgr_service distributeddatamgr_data_object

Service Startup ​

1. You can run the start_services.sh script to start the DDS.

   shell

   /system/bin/start_services.sh datamgr

2. You can run the ps command to check whether the distributed data management service is started.

   shell

   ps -ef | grep distributeddata

Usage ​

1. Create the /data directory required for running the demo. OpenHarmony applications require specific directories for running. Therefore, you need to create the directories in openEuler.

   shell

   mkdir -p /data/app/el0/0/database/com.example.distributed.rdb/rdb
   mkdir -p /data/app/el1/0/database/distributeddata/kvdb
   mkdir -p /data/service/el1/public/database/distributeddata/meta
   mkdir -p /data/service/el1/public/database/distributeddata/kvdb
   mkdir -p /data/service/el1/public/database/distributeddata/meta/backup

2. Write the client programs for the three databases (kv_store, data_object, and relational_store) to use the distributed data function.

   For details about how to write the client programs, see the demo source code of each database in Repository. The source code is stored in the demo directory in the directory corresponding to each database, for example, kv_store/demo. You can use the build.sh script in the demo directory for compilation.

   Notice

   It is recommended that the database path db specified by the demo be the same as the path of the sample demo. Otherwise, the path may not exist or the permission may be insufficient.

3. Stop the distributed management service datamgr_service.

   shell

   ./stop_services.sh all #Stop all services.
   ./stop_services.sh datamgr #Stop only the datamgr service.

FAQs ​

• When a service is started, the error message "Binder Driver died " is displayed.

  Cause: Binder is not enabled in the system. You can check whether the /dev/binder file exists. If the file does not exist, Binder is not enabled.

  Solution: Enable the binder function. For details, see communication_ipc Repository Description.

• The softbus_server service fails to be started, and the error message "GetNetworkIfIp ifName:eth0 fail" is displayed.

  Cause: Run the ip a command to view the name of the NIC in the current system and check whether the wired NIC eth0 exists. The softbus_server service obtains information such as the IP address through the wired NIC eth0. If eth0 does not exist, softbus_server cannot be started.

  Solution 1: Change the NIC name to eth0.

  Solution 2: Modify the softbus_server source code and change the name of the dependent wired NIC to that of the NIC in the current system.

References ​

hmdfs Distributed File System Overview