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
However, the resuming handlers are not called if the object has been deleted during the operator downtime or restart, and the deletion handlers are now being invoked.
This is done intentionally to prevent the cases when the resuming handlers start threads/tasks or allocate the resources, and the deletion handlers stop/free them: it can happen so that the resuming handlers would be executed after the deletion handlers, thus starting threads/tasks and never stopping them
When I put the resume on the delete event, the delete event is called after create and it deleted the object during operator restart. By looking at the above explanation, I am not clear about the resume on the delete event. Can you explain this behavior?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am looking at the docs here https://kopf.readthedocs.io/en/stable/handlers/#resuming-handlers and not clear about
When I put the
resume
on the delete event, the delete event is called after create and it deleted the object during operator restart. By looking at the above explanation, I am not clear about theresume
on the delete event. Can you explain this behavior?Beta Was this translation helpful? Give feedback.
All reactions