You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It adds a useful feature, but it does mean that if we somehow end up with rogue kill packets floating about during the barrier, they could derail an app execution rather than being silently dropped as now. Also need to consider instruction overhead.
I think it might be more important to know why there are rogue kill packets, rather than ignoring them.
Instruction space is a reasonable concern. It might be better for the Mothership to start and stop the application to achieve a recall. Then again, the operator might not want to start the application because they've just realised their supervisor would do something nasty on startup. In that case, the start-stop approach wouldn't solve the problem.
Small discussion arose in POETSII/orchestrator-documentation#18.
The motivation is to make the Mothership able to recall initialised applications without first starting and stopping them.
The text was updated successfully, but these errors were encountered: