Skip to content
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

How to deploy a horizontally scalable cluster? #353

Open
seepine opened this issue Jan 14, 2025 · 1 comment
Open

How to deploy a horizontally scalable cluster? #353

seepine opened this issue Jan 14, 2025 · 1 comment

Comments

@seepine
Copy link

seepine commented Jan 14, 2025

After reading the introduction, we found that citus perfectly met our requirements, but the deployment documentation was unfriendly.
How to deploy a horizontally scalable cluster?

Eg in Node 1 of 192.168.1.1

service:
  master1:
    image:citusdata/citus:12.1
    ports:
      - 5432:5432
    volumes:
      - ./data1:/data
    environment:
      - CITUS_CLUSTER: 192.168.1.2,182.168.1.3

Eg in Node 1 of 192.168.1.2

service:
  master2:
    image:citusdata/citus:12.1
    ports:
      - 5432:5432
    volumes:
      - ./data2:/data
    environment:
      - CITUS_CLUSTER: 192.168.1.1,182.168.1.3

Eg in Node 1 of 192.168.1.3

service:
  master3:
    image:citusdata/citus:12.1
    ports:
      - 5432:5432
    volumes:
      - ./data3:/data
    environment:
      - CITUS_CLUSTER: 192.168.1.1,182.168.1.2

And users can connect to any node.

  • 192.168.1.1:5432
  • 192.168.1.2:5432
  • 192.168.1.3:5432

Referenced from the MinIO cluster https://github.com/minio/minio/blob/master/docs/orchestration/docker-compose/docker-compose.yaml

@seepine
Copy link
Author

seepine commented Jan 14, 2025

I'm not sure if my understanding is wrong, but if citus can support such horizontal scalability and it can still work when a certain node fails, then it will be very powerful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant