CORTX ha (High-Availability) is responsible for ensuring that CORTX Solution is available in case of any hardware component or software service failures. It takes care of failover/ failback control flow for affected services and stabilizes them across CORTX cluster.
Optimizing ha_setup code to reduce consul accesses
Coding
[ ] Coding conventions are followed and code is consistent
Testing
[ ] Unit and System Tests are added
[ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
[ ] Testing was performed with RPM
Verified that values of data_node_ids , server_node_ids, control_node_ids, nodes_list remain same as before after this change
Review Checklist
[ ] PR is self reviewed
[ ] JIRA number/GitHub Issue added to PR
[ ] Jira and state/status is updated and JIRA is updated with PR link
[ ] Check if the description is clear and explained
[ ] Is there a change in filename/package/module or signature? [Y/N]:
[ ] If yes for above point, is a notification sent to all other cortx components? [Y/N]
[ ] Side effects on other features (deployment/upgrade)? [Y/N]
[ ] Dependencies on other component(s)? [Y/N]
If yes for above point, post link to the corresponding PR.
Review Checklist
[ ] Is perfline test run and the report with and without the changes updated in the PR? [Y/N]:
Documentation
Checklist for Author
[ ] Changes done to WIKI / Confluence page / Quick Start Guide
Signed-off-by: ArchanaLimaye archana.limaye@seagate.com
Problem Statement
CORTX-29667 HA deployment takes too long
Design
Optimizing ha_setup code to reduce consul accesses
Coding
Testing
Review Checklist
Review Checklist
Documentation
Checklist for Author