How to configure High Availability (HA) on AWS in ScaleArc v3.8 or later
Release | Classification | Level | DB Platform | Categories |
3.8 - 3.11.0.1 | Information | ![]() |
ALL | High Availibility |
Configure HA on AWS in ScaleArc v3.8 or later
QUESTION |
How to configure High Availability (HA) on AWS in Scalearc v3.8 - v3.11.0.1?
ANSWER |
High Availability (HA) allows a pair of ScaleArc servers to function as a redundant cluster. This KB describes the steps to configure High Availability cluster pair in ScaleArc on AWS.
Pre-Requisites to configure HA on AWS:
Create two scalearc v3.8 or later instance in AWS which are:
- Both instances must be able to reach each other
- The ScaleArc configuration must be identical in terms of:
- Instance Type (i.e. m4.2xlarge)
- ScaleArc release version.
- ScaleArc License (Cores, Cluster size, Cache Size)
- Separate license file is required for the Secondary node. Contact sales@scalearc.com or support@scalearc.com
- Replace localhost.domain with actual Hostname of the machine on both instances in ha.cf configuration file. ha.cf is present at location /etc/ha.d/ha.cf
- Ensure that /etc/ha.d/haresources contains "<hostname of Primary> killmonitoridb monitor_idb"
- Start HEARTBEAT service
$ service heartbeat restart
Configure HA on AWS:
- Enable SSH
By default we are unable to see the HA Settings in the Settings tab. To see the HA setting tab we need to access the Scalearc server using SSH.
Please refer this link to enable SSH access using UI.
- Modify instance type
Once we login to scalearc server using SSH, use the following command on both the scalearc servers :
- Modify HEARTBEAT parameters
Go to Settings in Scalearc UI and check if the HA settings are visible.
- Go to Settings >> HA settings:
- Click on Configure and change the Keep Alive and DeadTime parameters.
Please refer this link for recommended configuration on virtual environment.
-> KeepAlive(ms): 1000ms
-> DeadTime(Sec): 5 sec
-> WarnTime(ms): 2500ms(*automatically set*)
Configure HA
- On the Primary Scalearc Node Go to Settings >> HA settings
- Enter Remote Interface (Interface of the Secondary Node) and Remote IP (Internal IP of the Secondary Node).
- Click on “Add as Secondary” and enter the UI credentials of the Secondary Scalearc Instance.
- A confirmation message is seen once HA configuration is completed.
- We can check the HA Configuration under Settings >> HA settings.
If you are experiencing issues with ScaleArc or with any of it's features, please contact ScaleArc Support. We are available 24x7 by phone at 855 800 7225 or +1 408 412 7315. For general support inquiries, you can also e-mail us at support@scalearc.com.
Copyright ©2017 ScaleArc, Inc. All rights reserved. Contact Support | Contact ScaleArc | Feedback 2901 Tasman Drive Santa Clara, CA 95054 | Email: support@scalearc.com |
Permalink: https://support.scalearc.com/kb/articles/2388 |
Comments (1)
In Step 2, please define by which user we are executing this command echo 2 > /system/iscloud.txt. In AWS instance, idb user is not able to change its value because of permission denied.
[idb@ip-10-0-7-15 ~]$ ls -ltr /system/iscloud.txt
-rw-r--r-- 1 root apache 2 Mar 15 18:57 /system/iscloud.txt