You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Repro steps:
The text was updated successfully, but these errors were encountered: