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

[Platform]Availibility zones change depending on region selection order during Universe creation #8003

Open
adil246 opened this issue Apr 12, 2021 · 5 comments
Assignees
Labels
area/platform Yugabyte Platform
Milestone

Comments

@adil246
Copy link
Contributor

adil246 commented Apr 12, 2021

Description
Az's disappear from the list when a new region is added. This issue appears for the on-prem config provider. If the order is changed when adding regions(for example East first and then Central), the AZ's populate the way they should. Depending on the order you enter the regions, the availability zone list/behavior changes.

To Reproduce

  1. Create Universe using an on-prem config provider.
  2. Add the first Region with Nodes 3 and RF 3.
  3. Then add the second Region and you will notice one of the AZ's disappear.
  4. When you click Add Zone, the missing zone appears back.

Reference ticket
1081

@adil246
Copy link
Contributor Author

adil246 commented Apr 12, 2021

cc @skahler-yuga Let me know if anything else has to be added.

@adil246 adil246 added the area/platform Yugabyte Platform label Apr 14, 2021
@streddy-yb streddy-yb added this to the 2.7.x milestone Apr 19, 2021
@streddy-yb
Copy link
Contributor

hi @mjoshi0923 - please check if this issue reproduces for other providers as well (AWS, GCP, etc).

@mjoshi0923
Copy link
Contributor

mjoshi0923 commented Apr 19, 2021 via email

@mjoshi0923
Copy link
Contributor

@adil246 Do we have this issue? This was resolved long back, it's duplicate issue I guess.

@mjoshi0923 mjoshi0923 assigned adil246 and unassigned mjoshi0923 Feb 15, 2022
@adil246
Copy link
Contributor Author

adil246 commented Feb 15, 2022

@mjoshi0923 Yes, I do not see the issue now in 2.6.3 and AZ’s placement info is not switching to other zones when additional regions are added. I tested with a couple of regions adding them consecutively in google cloud and placement info stayed the same. I could go back and select Az’s based on preference after adding all regions. This can be closed. Thanks for the follow-up.

Final Placement info: Cloud=gcp Region=us-central1 : (AZ=us-central1-f, count=1, replication factor=1)Region=us-west1 : (AZ=us-west1-c, count=1, replication factor=1)Region=us-east1 : (AZ=us-east1-d, count=1, replication factor=1).
2022-02-15 15:06:44.643 [info] PlacementInfoUtil.java:1092 [application-akka.actor.default-dispatcher-81] Az placement map {b22ad78a-4c65-4c52-b43b-62db1fedd4f9=1, b09ed13a-4076-4faa-b0ce-682855aaaab0=1, 56bb5b1e-41ca-4c89-a08a-8446888d66cc=1}
2022-02-15 15:06:44.643 [info] PlacementInfoUtil.java:1124 [application-akka.actor.default-dispatcher-81] Az Map {b22ad78a-4c65-4c52-b43b-62db1fedd4f9=1, b09ed13a-4076-4faa-b0ce-682855aaaab0=1, 56bb5b1e-41ca-4c89-a08a-8446888d66cc=1}

@adil246 adil246 changed the title [Bug] Availibility zones change depending on region selection order during Universe creation [Platform]Availibility zones change depending on region selection order during Universe creation Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform Yugabyte Platform
Projects
None yet
Development

No branches or pull requests

3 participants