Long waiting time to deploy to iot modules to iot edge devices

Question

Long waiting time to deploy to iot modules to iot edge devices

Jeffrey K 171

When testing deployments of modules to IoT edge devices, I noticed wait time of 3-5mins for modules to be deployed to the IoT edge devices. I created default and layered deployment for a IoT device and I see the lag in getting the modules deployed to the end device.

Is there any properties or setup I need to enable to perform better throughput?
Is there the sequence flow that I can refer during this process?
Where can I see the logs during this activity of deployments?

My IoT device is a VM created in Azure with following configuration
"hardwareProfile": {
"vmSize": "Standard_DS3_v2"
},
"storageProfile": {
"imageReference": {
"publisher": "MicrosoftWindowsDesktop",
"offer": "Windows-10",
"sku": "rs5-enterprise-standard-g2",
"version": "latest"
},
"osDisk": {
"osType": "Windows",
"managedDisk": {
"storageAccountType": "Premium_LRS",
"diskSizeGB": 127
},

Accepted answer

2 additional answers

Your answer

Answer 1

VenkatYalla-0009 836

This behavior is dictated by the IoT Hub service not IoT Edge.

IoT Hub evaluates ADM deployment updates roughly every 5 min unless an existing deployment name/priority is updated (as you found), so this is expected behavior. I'm not aware of any way to adjust this.

António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2021-06-30T06:55:15.37+00:00
Hello @Jeffrey K ,
Please share with us if you have any other questions related with your original post. Otherwise could you go ahead and mark the above as answer?

Thank you so much.

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Answer 2

dteteruk 6

@Jeffrey K As far as I know time you need to download module depends on size of module. If module is several GB and connection is not stable it may take a lot of time.
You can simply check #s of traffic passed by network adapter. Run below command in terminal and see if numbers are changing it means download process in progress.

cat /proc/net/dev

Jeffrey K 171 Reputation points

2021-06-23T18:41:24.897+00:00
@dteteruk - I noticed one thing that when I update an existing Azure Edge deployment (which needed to be triggered when target condition was met) by just adding a space in between the targetcondition or priority field, the edgeAgent immediately gets the notification to install the modules from the layered deployment and the module is up and running less than 5-10secs.

I think the issue is there is a lag from the edgeAgent to identify the layered deployments once the target condition is met. I would like to know the following:

Time edgeAgent would wait to check on the deployments.

Is there a way to boost the time wait if any?

How to triage this process as in the logs of the edgeAgent? I do not see any logs from edgeAgent when waiting for the layered deployment to notify for the deployment rather it waits until then.
Jeffrey K 171 Reputation points

2021-06-23T18:41:59.543+00:00
My scenario is like this,

One default deployment created applies all the edge devices connected to the IotHub

One layered deployment created triggered once the targetcondition is satisfied

User applies changes in edge device which satisfies the target condition for the layered deployment to be triggered

Edge agent take 3-4mins to install the modules associated with the Layered deployment

Answer 3

António Sérgio Azevedo 7,671 Microsoft Employee Moderator

Hi @Jeffrey K ,
Before trying to help you further please clarify the following:

What version of IoT Edge are you using? 1.1 or 1.2?
Are you using Windows or Linux Containers?
Why 3-5 minutes is too long for your scenario?

Where can I see the logs during this activity of deployments?

Please start here: Troubleshoot your IoT Edge device

I would try to see more information using the command iotedge logs edgeAgent

António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2021-05-26T07:07:46.753+00:00

Hello @Jeffrey K ,
Please let me know the answers to the above or please share if you have found the answers to your questions already :).

Thanks!
Jeffrey K 171 Reputation points

2021-06-01T18:08:29.047+00:00
Below my updates

IoT edge version 1.1

Windows Container

I want to understand what is the expected time and justify the delay or is it expected?

Is there any sequence flow that I can look into?
António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2021-06-11T17:26:09.48+00:00

Thank you for providing the details @Jeffrey K .
I am researching on official documentation around expected delay times together with Product Team.

Appreciate your time so far.
António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2021-06-21T15:29:12.9+00:00
@Jeffrey K I couldn't find official documentation about expected delay times, but one thing to consider is the size of the module - do you notice a difference when a module is lower in size?

Another suggestion to monitor edge modules is to use the troubleshooting page in Azure Portal, let me know if the data there can help you troubleshoot this?

Troubleshoot IoT Edge devices from the Azure portal

Thank you!
Jeffrey K 171 Reputation points

2021-06-22T15:59:58.957+00:00

@António Sérgio Azevedo - On further analysis, I noticed the Layered deployments takes 2-3mins constantly to deploy while the Default deployment takes 1-2mins for the same set of modules. I will further trouble shoot using the link shared above.

Also, I'm continuously polling the module twin of the $edgeAgent reported properties to callback to our app that the new module has been deployed and I see the delay there as well. Is there a better way to alert the modules in the device to show the progress of the install?
António Sérgio Azevedo 7,671 Reputation points Microsoft Employee Moderator

2021-06-23T09:19:22.337+00:00

Thanks for following the suggested troubleshooting link, keep me posted.

I cannot think of a better way than continuously polling the module twin of the $edgeAgent reported properties. Though you can take a look at Moby or Docker documentation to see if there is any other way to report the progress of a container deployment (are you using moby-engine or Docker?)

Please also leverage feedback.azure.com Azure IoT Edge to suggest or vote for a feature, adding the business case on your description. If you do so, please share it here and I will elevate it to Product Group.

Thank you!

Share via

Long waiting time to deploy to iot modules to iot edge devices

2 additional answers

Your answer