Closed zyy17 closed 1 week ago
The recent changes streamline the management of the greptimedb
cluster with etcd using Docker Compose. The Makefile
has renamed and added new targets for starting and stopping the cluster, while the Docker Compose file has seen variable name changes, a new image reference, and additional health checks and configurations.
Files | Change Summary |
---|---|
Makefile | Renamed run-cluster-with-etcd to start-cluster ; added stop-cluster |
docker/docker-compose/cluster-with-etcd... | Renamed ETCD variables; added new image reference for greptimedb ; introduced health checks and ports for services |
In the land of code where clusters dwell,
A change has come, a tale to tell.
Start and stop with newfound grace,
Services checked, no need to chase.
Greptimedb stands strong and free,
Amidst the waves of Docker, see?
All hail the realm of harmony.
πβ¨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.90%. Comparing base (
4f0984c
) to head (f3154e4
). Report is 29 commits behind head on main.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
NOTE: Wait for the latest nightly release.
Refactor the Makefile target naming:
make start-cluster
: Create the greptimedb cluster by using docker compose;make stop-cluster
: Stop the greptimedb cluster that created by the docker compose;Checklist
Summary by CodeRabbit
New Features
greptimedb
cluster using Docker Compose.Improvements
greptimedb
cluster tostart-cluster
.datanode0
,frontend0
, andflownode0
.Configuration Changes
greptimedb
.