Metadata Repository #
Background #
DBPlusEngine provides different metadata persistence methods for different running modes. Users can choose an appropriate way to store metadata while configuring the running mode.
Parameters #
ZooKeeper Repository #
Type: ZooKeeper
Mode: Cluster
Attributes:
| Name | Type | Description | Default Value |
|---|---|---|---|
| retryIntervalMilliseconds | int | Milliseconds of retry interval | 500 |
| maxRetries | int | Max retries of client connection | 3 |
| timeToLiveSeconds | int | Seconds of ephemeral data live | 60 |
| operationTimeoutMilliseconds | int | Milliseconds of operation timeout | 500 |
| digest | String | Login password |
Etcd Repository #
Type: Etcd
Mode: Cluster
Attributes:
| Name | Type | Description | Default Value |
|---|---|---|---|
| timeToLiveSeconds | long | Seconds of ephemeral data live | 30 |
| connectionTimeout | long | Seconds of connection timeout | 30 |
Mate Repository #
Type: SphereEx:MATE
Mode: Cluster
Attributes:
none
Procedure #
- Configure running mode in server.yaml.
- Configure metadata persistence warehouse type.
Sample #
- Cluster mode.
mode:
type: Cluster
repository:
type: SphereEx:MATE
props:
namespace: governance
server-lists: localhost:21506