| title | description | ms.service | ms.subservice | ms.topic | author | ms.author | ms.custom | ms.date |
|---|---|---|---|---|---|---|---|---|
Self-hosted integration runtime auto-update and expire notification |
Learn about self-hosted integration runtime auto-update and expire notification |
data-factory |
integration-runtime |
conceptual |
lrtoyou1223 |
lle |
seo-lt-2019 |
06/16/2021 |
[!INCLUDEappliesto-adf-asa-md]
This article will describe how to let self-hosted integration runtime auto-update to the latest version and how ADF manages the versions of self-hosted integration runtime.
You can check the version either in your self-hosted integration runtime client or in Azure data factory portal:
:::image type="content" source="./media/self-hosted-integration-runtime-auto-update/self-hosted-integration-runtime-version-client.png" alt-text="Screenshot that shows the version in self-hosted integration runtime client.":::
:::image type="content" source="./media/self-hosted-integration-runtime-auto-update/self-hosted-integration-runtime-version-portal.png" alt-text="Screenshot that shows the version in Azure data factory portal.":::
Generally, when you install a self-hosted integration runtime in your local machine or an Azure VM, you have two options to manage the version of self-hosted integration runtime: auto-update or maintain manually. Typically, ADF releases two new versions of self-hosted integration runtime every month which includes new feature release, bug fix or enhancement. So we recommend users to update to newer version in order to get the latest feature and enhancement.
The most convenient way is to enable auto-update when you create or edit self-hosted integration runtime. The self-hosted integration runtime will be automatically update to newer version. You can also schedule the update at the most suitable time slot as you wish.
:::image type="content" source="media/create-self-hosted-integration-runtime/shir-auto-update.png" alt-text="Enable auto-update":::
You can check the last update datetime in your self-hosted integration runtime client.
:::image type="content" source="media/create-self-hosted-integration-runtime/shir-auto-update-2.png" alt-text="Screenshot of checking the update time":::
You can use this PowerShell command to get the auto-update version.
Note
If you have multiple self-hosted integration runtime nodes, there is no downtime during auto-update. The auto-update happens in one node first while others are working on tasks. When the first node finishes the update, it will take over the remain tasks when other nodes are updating. If you only have one self-hosted integration runtime, then it has some downtime during the auto-update.
To ensure the stability of self-hosted integration runtime, although we release two versions, we will only push one version every month. So sometimes you will find that the auto-update version is the previous version of the actual latest version. If you want to get the latest version, you can go to download center. Additionally, auto-update to a version is managed one. You cannot change it. If you want to upgrade to latest version, you have to do it manually.
The self-hosted integration runtime Auto update page in ADF portal shows the newer version if current version is old. When your self-hosted integration runtime is online, this version is auto-update version and will automatically update your self-hosted integration runtime in the scheduled time. But if your self-hosted integration runtime is offline, the page only shows the latest version.
If you have multiple nodes, and for some reasons that some of them are not auto-updated successfully. Then these nodes roll back to the version which was the same across all nodes before auto-update.
If you want to manually control which version of self-hosted integration runtime, you can disable the setting of auto-update and install it manually. Each version of self-hosted integration runtime will be expired in one year. The expiring message is shown in ADF portal and self-hosted integration runtime client 90 days before expiration.