New Grid setup - EGO Controller Configuration

[mkiran]

We are installing SAS 9.4 M8 and would like to have a high availability for Grid nodes and I know this can be acheived with EGO controller configuration. Can you provide any good reference for how-to-configure EGO on a grid setup?.  I found the below URL but this is pretty old and referring to RTM setup which is no longer exist.

https://communities.sas.com/t5/SAS-Communities-Library/High-Availability-with-SAS-Grid-Manager/ta-p/...

[JuanS_OCS · Accepted solution]

Hi there!

I would always point you to the documentation at SAS, but the HA implementation will also depend on your Grid Architecture: are your binaries shared? Are your config folders shared? Is your Grid based on IBM Process Manager, on Hadoop, on SAS Workload Orchestrator (SWO)? 

1- For the first one, which I am not sure if it is the one you have, the main difference for now from earlier with RTM is about who will acting as Load Balanced - if RTM, EGO or something else. In this case, you can still use EGO, but I would rather use something else for Load Balancing.

2- For the second one, I cannot tell you much, as I have not implemented it yet. But the basics should be fairly similar.

3- For the last one, and when you have binaries and configuration shared across compute nodes. Remember, you will need a Load Balancer still: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-HA-services-with-SAS-Workload-O...

[mkiran]

@JuanS_OCS : We still wanted to go for LSF with EGO controller, Yes, our binaries and configs are shared between grid nodes. Can you suggest me a specific doc I can refer for this setup?

[gwootton]

What is it you are trying to make highly available on the grid nodes?

The replacement for RTM is the SAS Grid Manager Module for SAS Environment Manager, and you can configure services (ego) through that.

High Availability in a SAS Grid Manager for Platform Grid
https://go.documentation.sas.com/doc/en/bicdc/9.4/gridref/n195slxn27oenen19duslvwv3scg.htm

[mkiran]

Thank you !. We decided to go with HA using SASEVM.