Synapse Integration Runtime high availability

Question

Synapse Integration Runtime high availability

Charles Thivierge 4,181

I have a question with the Self-Hosted Integration Runtime configuration in a high availability scenario.

As per this documentation https://learn.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime?tabs=data-factory#high-availability-and-scalability

You need to configure "Remote access to intranet" on the first node before adding another node. I have done that and it's working well. But do we have to configure the Remote access to intranet option on all other nodes as well ?

I have searched for the answer but i was not able to find it.

Any thought ?

Thanks!

Anonymous

2024-05-31T03:18:25.4966667+00:00

@cthivierge Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Your answer

Anonymous

2024-05-31T03:18:25.4966667+00:00

@cthivierge Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Anonymous

@cthivierge Thanks for the question and using MS Q&A platform.

In a high availability scenario for the Self-Hosted Integration Runtime, you only need to configure “Remote access to intranet” on the first node. This is done before adding any other nodes to ensure that the first node can communicate with the other nodes that will be added later.

Once the first node is configured with “Remote access to intranet”, you can then add other nodes to the Self-Hosted Integration Runtime These additional nodes do not require the “Remote access to intranet” to be configured individually.

This setup allows for higher availability of the self-hosted integration runtime, ensuring it’s not a single point of failure in your data solution. It also improves performance and throughput during data movement between on-premises and cloud data stores.

Please refer this thread https://learn.microsoft.com/en-us/answers/questions/818758/high-availability-or-multiple-node-setup-for-self

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Charles Thivierge 4,181 Reputation points

2024-05-28T15:51:15.25+00:00

Thanks @Anonymous but let say we have a 3 nodes and i only enable "Remote access to intranet" on the first node. What happen if the first node is not running (maintenance or any other problem) ? does this would cause a problem ? The other 2 nodes without the "Remote access to intranet" configured will still be able to work as expected ?
Anonymous

2024-05-30T03:13:13.4366667+00:00

@Anonymous

In a high availability setup, if the first node (where “Remote access to intranet” is enabled) goes down for maintenance or encounters an issue, the other nodes should continue to operate as expected. The “Remote access to intranet” setting is primarily required for the initial setup and communication between the nodes. Once the nodes are added and operational, they work independently of each other.

However, it’s important to note that the specific impact might depend on the nature of the tasks being performed and the configuration of your network. If a particular task was being handled by the first node at the time it went down, that task might be interrupted. But the self-hosted integration runtime is designed to provide high availability and ensure that there’s no single point of failure.

If you anticipate that the first node might go down frequently or for extended periods, you might want to consider enabling “Remote access to intranet” on the other nodes as well for redundancy. But under normal circumstances, it’s not necessary to do so

Share via

Synapse Integration Runtime high availability

1 answer

Your answer