Clarification regarding 0.10.* breaking changes #3310
-
Here is the list of breaking changes, when upgrading from Could you please clarify the following?
|
Beta Was this translation helpful? Give feedback.
Answered by
hengfeiyang
Apr 22, 2024
Replies: 2 comments 4 replies
-
|
Beta Was this translation helpful? Give feedback.
2 replies
-
Hi @hengfeiyang. I've upgraded from openobserve-1:
image: public.ecr.aws/zinclabs/openobserve:v0.10.5
container_name: openobserve-1
depends_on:
- etcd
- minio
- mariadb
environment:
- ZO_LOCAL_MODE=false
- ZO_INSTANCE_NAME=openobserve-1
- [email protected]
- ZO_ROOT_USER_PASSWORD=testtest
- ZO_ETCD_ADDR=etcd:2379
- ZO_S3_SERVER_URL=http://minio:9500
- ZO_S3_REGION_NAME=us-east-1
- ZO_S3_ACCESS_KEY=minio
- ZO_S3_SECRET_KEY=miniopass123
- ZO_S3_BUCKET_NAME=openobserve
- ZO_S3_PROVIDER=minio
- ZO_DATA_DIR=/var/lib/openobserve/
volumes:
- ./openobserve/1/data:/var/lib/openobserve
restart: always
openobserve-2:
image: public.ecr.aws/zinclabs/openobserve:v0.10.5
container_name: openobserve-2
depends_on:
- etcd
- minio
- mariadb
environment:
- ZO_LOCAL_MODE=false
- ZO_INSTANCE_NAME=openobserve-2
- [email protected]
- ZO_ROOT_USER_PASSWORD=testtest
- ZO_ETCD_ADDR=etcd:2379
- ZO_S3_SERVER_URL=http://minio:9500
- ZO_S3_REGION_NAME=us-east-1
- ZO_S3_ACCESS_KEY=minio
- ZO_S3_SECRET_KEY=miniopass123
- ZO_S3_BUCKET_NAME=openobserve
- ZO_S3_PROVIDER=minio
- ZO_DATA_DIR=/var/lib/openobserve/
volumes:
- ./openobserve/2/data:/var/lib/openobserve
restart: always
openobserve-3:
image: public.ecr.aws/zinclabs/openobserve:v0.10.5
container_name: openobserve-3
depends_on:
- etcd
- minio
- mariadb
environment:
- ZO_LOCAL_MODE=false
- ZO_INSTANCE_NAME=openobserve-3
- [email protected]
- ZO_ROOT_USER_PASSWORD=testtest
- ZO_ETCD_ADDR=etcd:2379
- ZO_S3_SERVER_URL=http://minio:9500
- ZO_S3_REGION_NAME=us-east-1
- ZO_S3_ACCESS_KEY=minio
- ZO_S3_SECRET_KEY=miniopass123
- ZO_S3_BUCKET_NAME=openobserve
- ZO_S3_PROVIDER=minio
- ZO_DATA_DIR=/var/lib/openobserve/
volumes:
- ./openobserve/3/data:/var/lib/openobserve
restart: always |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, You must setup MySQL / PostgreSQL for store metadata since v0.10.0. and you still need etcd for cluster, so, you need:
etcd MySQL
oretcd PostgreSQL
now, in 0.9.x you only needetcd
.