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

Trying to create 2 clusters for BigTable Replication #2664

Closed
michyliao opened this issue Dec 13, 2018 · 3 comments
Closed

Trying to create 2 clusters for BigTable Replication #2664

michyliao opened this issue Dec 13, 2018 · 3 comments

Comments

@michyliao
Copy link
Contributor

michyliao commented Dec 13, 2018

Hi,

I am trying to terraform a BigTable instance with replication enabled. I have tried to create 2 clusters in the config of

resource "google_bigtable_instance" "instance" {
  name         = "tf-instance"
  cluster {
    cluster_id   = "tf-instance-cluster-1"
    zone         = "us-central1-b"
    num_nodes    = 3
    storage_type = "HDD"
  }


cluster {
    cluster_id   = "tf-instance-cluster-2"
    zone         = "us-central1-c"
    num_nodes    = 3
    storage_type = "HDD"
  }
}

Let me know how to enable this.. I cannot find any documentation w.r.t this.

Thanks

@michyliao
Copy link
Contributor Author

My mistake, my assumption was that replication was enabled from the thread of #1672 but after reading it more, it sounds like it was a bug fix for multi cluster routing when enabling replication from 1 cluster (through terraform).

Is it possible to add the config of enabling 2 clusters/replication through terraform?

@rileykarson
Copy link
Collaborator

Hey @michyliao! That bug was about enabling multiple clusters- we've added support at HEAD in our 2.0.0 branch, but our 2.0.0 release is blocked on an upstream release of the Terraform 0.12 beta. When we release 2.0.0, creating 2 clusters will be possible. Unfortunately, we don't have a strong estimate on when we'll be able to cut 2.0.0 as we're waiting on that upstream release.

@ghost
Copy link

ghost commented Jan 13, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Jan 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants