-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Healthchecks provided for all context storages #279
Changes from all commits
1371e53
3fa0950
6c79bad
a599890
bde8480
facea50
c60d4b3
6f2b9b9
83b54b7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,6 @@ | ||
version: "3.9" | ||
services: | ||
|
||
mysql: | ||
env_file: [.env_file] | ||
image: mysql:latest | ||
|
@@ -10,6 +11,13 @@ services: | |
- 3307:3306 | ||
volumes: | ||
- mysql-data:/var/lib/mysql | ||
healthcheck: | ||
test: mysql -u $${MYSQL_USERNAME} -p$${MYSQL_PASSWORD} -e "select 1;" | ||
interval: 5s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
|
||
psql: | ||
env_file: [.env_file] | ||
image: postgres:latest | ||
|
@@ -20,6 +28,13 @@ services: | |
- 5432:5432 | ||
volumes: | ||
- postgres-data:/var/lib/postgresql/data | ||
healthcheck: | ||
test: psql pg_isready -U $${POSTGRES_USERNAME} -d $${POSTGRES_DB} | ||
interval: 5s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
|
||
redis: | ||
env_file: [.env_file] | ||
image: redis:latest | ||
|
@@ -31,6 +46,13 @@ services: | |
- 6379:6379 | ||
volumes: | ||
- redis-data:/data | ||
healthcheck: | ||
test: redis-cli --raw incr ping | ||
interval: 5s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
|
||
mongo: | ||
env_file: [.env_file] | ||
image: mongo:latest | ||
|
@@ -41,6 +63,13 @@ services: | |
- 27017:27017 | ||
volumes: | ||
- mongo-data:/data/db | ||
healthcheck: | ||
test: mongosh --norc --quiet --eval 'db.runCommand("ping").ok' localhost:27017/test | ||
interval: 5s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
|
||
ydb: | ||
env_file: [.env_file] | ||
image: cr.yandex/yc/yandex-docker-local-ydb:latest | ||
|
@@ -55,6 +84,13 @@ services: | |
volumes: | ||
- ydb-data:/ydb_data | ||
- ydb-certs:/ydb_certs | ||
healthcheck: | ||
test: sh ./health_check | ||
interval: 5s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
|
||
dashboard: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need health checks for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can, but I am not very familiar with what properties should we test in that cases. If you have a suggestion - I'll research how to add some. |
||
env_file: [.env_file] | ||
build: | ||
|
@@ -70,6 +106,7 @@ services: | |
- stats | ||
ports: | ||
- "8088:8088" | ||
|
||
dashboard-metadata: | ||
env_file: [.env_file] | ||
image: postgres:latest | ||
|
@@ -83,11 +120,13 @@ services: | |
command: -p 5433 | ||
healthcheck: | ||
test: pg_isready -p 5433 --username=$${POSTGRES_USERNAME} | ||
interval: 4s | ||
timeout: 3s | ||
retries: 3 | ||
interval: 5s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
volumes: | ||
- dashboard-data:/var/lib/postgresql/data | ||
|
||
clickhouse: | ||
env_file: [.env_file] | ||
image: clickhouse/clickhouse-server:latest | ||
|
@@ -101,10 +140,12 @@ services: | |
volumes: | ||
- ch-data:/var/lib/clickhouse/ | ||
healthcheck: | ||
test: wget --no-verbose --tries=1 --spider http://localhost:8123/ping || exit 1 | ||
test: wget --no-verbose --tries=1 --spider http://localhost:8123/ping | ||
interval: 5s | ||
timeout: 4s | ||
timeout: 10s | ||
retries: 5 | ||
start_period: 30s | ||
|
||
otelcol: | ||
image: otel/opentelemetry-collector-contrib:latest | ||
profiles: | ||
|
@@ -121,6 +162,7 @@ services: | |
ports: | ||
- "4317:4317" # OTLP over gRPC receiver | ||
- "4318:4318" # OTLP over HTTP receiver | ||
|
||
volumes: | ||
ch-data: | ||
dashboard-data: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you explain how these numbers were chosen?
If we used the default ones we wouldn't have to specify anything and have
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These numbers were chosen after local testing; some DB images already have healthchecks included, other do not.
I wanted all of them to be in equal conditions.