4 ms·
I've been following CockroachDB for quite a while. Great job on 1.0. I've had a question for quite some time though (and I think there is an RFC for it on GitH
by apognu 9y ago
I've been following CockroachDB for quite a while. Great job on 1.0.
I've had a question for quite some time though (and I think there is an RFC for it on GitHub): do we still need to have a "seed node" that is run without the --join parameter, or can we run all the nodes with the same command line, with the cluster waiting for quorum to reconcile on its own?
- bdarnell 9y agoCurrently, you need to run one node without --join for the initial bootstrapping (as soon as this bootstrapping is complete, you can and should restart it with --join to get everything into a homogenous configuration). I was hoping to make some changes here so you could start every node with --join from the beginning, but it was trickier than anticipated so it didn't make the cut for 1.0. Watch for improvements here in a future release.
- apognu 9y agoThank you for your answer. That's okay, for now, I run a simple StatefulSet where each pod checks whether the Service is reachable on port 26257 to determine if it should join or init the cluster. It's not as nice as if it was handled by Cockroach itself, but it does the job.
- bdarnell 9y agoThis bootstrapping problem is tricky. We publish kubernetes templates at https://github.com/cockroachdb/cockroach/tree/master/cloud/kubernetes https://github.com/cockroachdb/cockroach/tree/master/cloud/k... that contain our current best solution for the join/init problem.