| commit | 08d66c4283b9b9f1cb738a0995f3b9327e4df2c3 | [log] [tgz] |
|---|---|---|
| author | CooooolFrog <zuliangwanghust@gmail.com> | Tue Nov 28 19:52:28 2023 +0800 |
| committer | GitHub <noreply@github.com> | Tue Nov 28 19:52:28 2023 +0800 |
| tree | 92a12bdf9e2e5baa6ffd2c45c5007c4d2c1655d7 | |
| parent | 472b91c031773df6d13a0792a89e9b9aaf16e6c7 [diff] |
refactor: procedure storage (#279) ## Rationale The current design of the procedure storage module is unreasonable. The data will be stored permanently and will not be cleared. This will cause the storage space of `ETCD` to be filled up quickly. We need to redesign the interface of procedure storage. ## Detailed Changes * Add `ttl` config for `CreateOrUpdate`. * Add `Delete` interface, it used to delete history procedure data and current procedure data. ## Test Plan Pass all unit tests and integration tests.
HoraeMeta is the meta service for managing the HoraeDB cluster.
The project is in a very early stage.
make build
Although HoraeMeta is designed to deployed as a cluster with three or more instances, it can also be started standalone:
# HoraeMeta0 mkdir /tmp/meta0 ./bin/ceresmeta-server --config ./config/example-standalone.toml
Here is an example for starting HoraeMeta in cluster mode (three instances) on single machine by using different ports:
# Create directories. mkdir /tmp/meta0 mkdir /tmp/meta1 mkdir /tmp/meta2 # horaemeta0 ./bin/ceresmeta-server --config ./config/exampl-cluster0.toml # horaemeta1 ./bin/ceresmeta-server --config ./config/exampl-cluster1.toml # horaemeta2 ./bin/ceresmeta-server --config ./config/exampl-cluster2.toml
HoraeMeta refers to the excellent project pd in design and some module and codes are forked from pd, thanks to the TiKV team.
The project is under rapid development so that any contribution is welcome. Check our Contributing Guide and make your first contribution!
HoraeMeta is under Apache License 2.0.