-
Notifications
You must be signed in to change notification settings - Fork 937
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream Analytics on Edge restart engine to pick up new reference data #142
Comments
Thanks for reporting the case. The behavior is expected, for ASA edge module, we currently only support static ref data, to update existing ref data, you will need to do an iotedge deployment with the latest ref data path, it will not trigger container restart but instead cause engine reboot to pick up the latest data. |
Thanks for the answer. This is how I was doing it (updating data). But will the engine restart cause the loss of the data? If yes then I would say the documentation is quite unclear about it as it states that it picks up new ref data without stopping the job. |
Thanks for pointing it out, we will update the doc to avoid confusion. During engine reboot, the input which has been calculated in memory but hasn't been produced as output will be deleted. |
Hi, Can anyone explain me how to add reference data file in a stream analytics edge job? The docs lacks information/examples about that. Do I have to create a volume for docker and bind it between ASA container and the edge machine? Thank you. |
I am working on Stream Analytics deployed on Edge machine. It's using reference data that is deployed in the volume and binded to Stream analytics container. It's working fine. But I encountered an issue when i try to update the reference data.
As per documentation:
So I updated the file and then i updated the edge manifest through Azure portal. In fact i didn't change anything i just created new deployment. After that i checked if Stream Analytics got that information. And it seems that it did but it also caused the engine to restart. It is unacceptable as it will occur in data loss for almost 2 minutes. As per documentation it seems that it shouldn't restart.
Here is what I see in logs after deployment: (i deleted link with company names)
The text was updated successfully, but these errors were encountered: