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

[YW] Master brought up in read replica cluster #6085

Closed
iSignal opened this issue Oct 17, 2020 · 0 comments
Closed

[YW] Master brought up in read replica cluster #6085

iSignal opened this issue Oct 17, 2020 · 0 comments
Assignees
Labels
area/platform Yugabyte Platform
Projects
Milestone

Comments

@iSignal
Copy link
Contributor

iSignal commented Oct 17, 2020

Repro steps:

  1. Create a universe with a primary cluster (nodes N1-3) and a read replica cluster (nodes N4-6).
  2. Stop and release a master+tserver node N1 in the primary cluster through the node dropdown.
  3. Stop and release a tserver node N4 in the read replica cluster through the node dropdown.
  4. "Add node" N4 in the read replica cluster through the node dropdown.
  5. Observed: master is started in the read replica cluster.

Screen Shot 2020-10-16 at 4 59 35 PM

@iSignal iSignal added the area/platform Yugabyte Platform label Oct 17, 2020
@streddy-yb streddy-yb added this to To do in Platform Oct 19, 2020
@streddy-yb streddy-yb added this to the v2.5 milestone Oct 19, 2020
@SergeyPotachev SergeyPotachev moved this from To do to In Review in Platform Oct 20, 2020
SergeyPotachev added a commit that referenced this issue Oct 22, 2020
Summary:
- For nodes in Read Replica cluster limited next functions:
  1) Start node action (when the universe is in masters under replicated state, doesn't
     start the master process);
  2) Add node action (when the unierse is in masters under replicated state, creates a node
     with t-server running only);
  3) Start Master action (for nodes in Read Replica cluster it is strictly not available).

Test Plan:
Preparation (common steps for scenarios below):
  Create a universe with a primary cluster (RF=3, nodes N1-3) and a read replica cluster (nodes N4-6).

Scenario 1 (from the issue description):
  1. Stop and release a master+tserver node N1 in the primary cluster through the node dropdown.
  2. Stop and release a tserver node N4 in the read replica cluster through the node dropdown.
  3. "Add node" N4 in the read replica cluster through the node dropdown.
Expected result:
  Master is not started in the read replica cluster (on N4).

Scenario 2:
  1. Stop node N4 through the node dropdown.
  2. Stop node N1 through the node dropdown.
  3. Start node N4 through the node dropdown.
Expected result:
  Master is not started in the read replica cluster (on N4).

Scenario 3.
  1. Stop node N1 through the node dropdown.
  2. Check the dropdown menu of node N4.
Expected result:
  There is no action 'Start Master'.

Reviewers: sanketh

Reviewed By: sanketh

Subscribers: jenkins-bot, yugaware, wesley, daniel

Differential Revision: https://phabricator.dev.yugabyte.com/D9688
@SergeyPotachev SergeyPotachev moved this from In Review to Needs QA/Docs in Platform Oct 23, 2020
@streddy-yb streddy-yb self-assigned this Nov 16, 2020
@streddy-yb streddy-yb modified the milestones: v2.5, 2.5.1.0 Nov 30, 2020
@streddy-yb streddy-yb moved this from Needs QA/Docs to Closed in Platform Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform Yugabyte Platform
Projects
Platform
  
Closed
Development

No branches or pull requests

3 participants