No immediate reaction on changes/deletion if sleeping for retries

[kopf-archiver]

An issue by nolar at 2019-08-02 00:19:14+00:00
Original URL: zalando-incubator/kopf#161
 

Expected Behavior

When a handler function raises an exception, it is scheduled to be retried later (by default, in 60 seconds). Other handlers will be invoked — until the state is reached, when all the remaining handlers are scheduled for later.

When a handler with an exception or a retry is scheduled for later execution, and its operator is sleeping until the time comes, and a new watch-event arrives — the sleep must be interrupted, and a new state must be processes immediately, not after few tens of seconds.

Actual Behavior

Kopf uses unconditional asyncio.sleep() with the shortest duration until the next handler to be awakened.

If new events arrive for that object — e.g. it was changed or deleted — the sleep continues unconditionally, and the new events are processes much later.

Steps to Reproduce the Problem

import kopf

@kopf.on.create('zalando.org', 'v1', 'kopfexamples')
def create(**_):
    raise Exception("oops")

1. Run the operator in the background.
2. Create an object.
3. Within the next 60 seconds (default timeout), delete the object.
4. Observe: the deletion is frozen until the operator reaches its 60s timing.

Specifications

kopf==0.20