1 of 1 people found this helpful
You can configure the Catalog service to run on an backup node for failsafe scenario.
For Hadoop services this is not possible, But in a multinode cluster , HDFS and Yarn are run on any of the multiple nodes if any of the server s go down.
Ambari would need the servers to be up and running though
Thanks for your answer.
Can you tell me the steps to configure the Catalog_Service to run on a backup gateway node when the master gateway node goes down?
In the Multi-Node setup when we configure the service, It gives you an option to select the backup node in the multi-node setup.
In case if you are using an multi-node setup for failsafe scenarios please make sure to make the changes related to firewall(if any) and EBF's are applied on both the nodes.
Hi Srinivas ,
I had a related question to it . How can we handle the domain failover in EDC ? Is that we just set another node as a gateway node ?
And to select these backup node settings is the High availability license required separately in EDC ?
If you use a backup node for the service configuration in the Admin Console.
EDC would switch to the backup node if for any reason the primary node goes down.
AFAIK, there is no separate licensing required.
Thank you Srinivas for your helpful answer . I understood the service failover part but what if domain which hosts the services itself goes down? Is there any way to make it fault tolerant ?
Yes, The Domain can be configured for HA setup.
Although I would recommend you to raise this query related to HA on domain level under the community Data Integration --> Platform.
This would be the right community for queries related to domain level requirements so that the right people can check and answer the same.
Are there any plans to have the CMS(Content Management Service) run on a grid or use a backup node?
Currently, it looks like there is not a soluition if the CMS goes down even with domain on multi-node and CS,DIS, MRS with backup nodes.
CMS behave differently and does not follow the same active/passive deployment method.
Recommendation is to run one CMS on backup nodes to allow availibility of the content on backup node.
the additional CMS services will be started as passive and will license to changes occuring on the master CMS service.
please see additional information on HA for CMS here: Content Management Service and High Availability