Identify the headnode host, and schedule a script to regularly update the entry.

The HDInsight cluster designates one cluster node as the headnode. If the node fails or stops for maintenance, the cluster designates another node as the headnode. When this happens, the headnodehost entry in

/etc/hosts

files on Informatica domain nodes requires updating. You can schedule a script to perform this update.

In the
/etc/hosts
file on each machine that hosts the Data Integration Service, enter the IP address, DNS name, and DNS short name for each data node on the cluster. Use
headnodehost
to identify the host as the cluster headnode host.
For example:
10.20.30.40 hn0-rndhdi.abcdefghaouniiuvfp3betl3d.ix.internal.cloudapp.net headnodehost
Download the headnode_update_script.zip file from the Informatica documentation portal and uncompress it to get headnode_update_script.sh.
The script gets the the IP address, DNS name, and DNS short name for the head node host from the
x-ms-hdi-active
property on the cluster. The script then replaces the value of
headnodehost
in the hosts file with the
x-ms-hdi-active
value.
Schedule the script to run regularly on each machine that hosts the Data Integration Service. Set up a schedule based on your requirements, such as daily updates.

If the HDInsight cluster is integrated with ADLS storage, you also need to enter the IP addresses and DNS names for the hosts listed in the cluster property fs.azure.datalake.token.provider.service.urls.

For example:

1.2.3.67  gw1-ltsa.1320suh5abcdefghgaz0izgnhe.gx.internal.cloudapp.net
1.2.3.68  gw0-ltsa.1320suh5abcdefghgaz0izgnhe.gx.internal.cloudapp.net