-
Notifications
You must be signed in to change notification settings - Fork 11
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
[P3] Control-Plane app needing 5 minutes to remove FrameSplitter POD after camera is removed from control plane app. #98
Comments
I still think that it takes too long to delete the pods processing the camera... I deleted the camera 5 minutes ago and it's still getting ALERTS... so I think it needs too much time to delete the related pods? - Please, confirm... |
Answer with the AKRI issue description and we'll contact the AKRI team asking for workaround. |
Let's keep it as P1 until we get an answer from the AKRI team, ok? |
AKRI team said it's a hardcoded value. |
[UPDATED] Read the latest message. IT's working but it need 5 minutes to delete the FramrSplitter POD. We should do it in a few secs, right?
Repro:
I removed the camera that was working, it's empty now:
However, MEC-Accelerator was still getting new ALERTS, like if it didn't delete the provisioning for that camera (FRame-splitter, etc. should be deleted for that camera, right?).
It was still processing. I there are no cameras provisioned in control-plane there should not be ALERTS coming through?...
However, I think this is NOT a bug... I think there were many ALERTS queued in MQTT since it was creating many, all the time...
After a few minutes, the ALERTS stopped being created... So, I think the behavior is correct.
Please, confirm this is the case. :)
The text was updated successfully, but these errors were encountered: