Skip to content
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.

Request: Documentation on how to run a BigBen cluster in Kubernetes #34

Open
OUCHUNYU opened this issue Oct 25, 2019 · 2 comments
Open

Comments

@OUCHUNYU
Copy link

First of all, thank all the maintainers for the hard work. I have a single node BigBen running in our dev k8s cluster, so far it has been working reliably for us. We now would like to set up a 3 node BigBen cluster in our production k8s cluster to support real traffic, but there is no documentation about this. So, as the title describes, what should I do to set up a 3 node Bigben cluster in k8s? If you guys already have this worked out, it would be really nice if you guys can share that with me. Or else, if you could point me in the right direction, it would save us a bunch of time.

@OUCHUNYU
Copy link
Author

@sandeepmalik Any thoughts?

@sandeepmalik
Copy link
Contributor

HI @OUCHUNYU , this is indeed strange. I thought I had documented the cluster operation but after looking at the ReadMe I realized I had not documented it properly. I will update the documentation (as soon as I get the write access again, which I am awaiting). But this is how you run it in the cluster mode:

Take a look at the bigben.yaml (https://github.com/walmartlabs/bigben/blob/master/app/src/main/resources/bigben.yaml)

There's an hz section in there. All you need to do is set up the member ips (comma separated) (and change the port if using a different port).

hz:
network:
members: IP1,IP2,IP3

You don't need to list all the IPs (the more the better) but at least provide a couple of IPs (seeds) at least.

You can also provide this setting through the system property as -Dhz.network.members="IP1,IP2,IP3" as well.

After that call the cluster API (GET /events/cluster) to ensure that cluster is property formed and a master is chosen.

Hope this helps.

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

No branches or pull requests

2 participants