eventing
eventing copied to clipboard
[QE] Wathola sender is affected by Coordinated Omission Problem
Describe the bug The wathola sender - a testing utility that is used to assert continual propagation of events is affected with The Coordinated Omission Problem. Target service response time is now influencing the rate that the sender is sending the events, as sending is synchronous and single threaded.
Expected behavior
Using wathola sender with set interval should result in sending exactly 1000 / interval events. Remote service response time or outage shouldn't influence sending rate.
To Reproduce
- Write a file https://gist.github.com/cardil/c7c2e0dc7da9b925bbe96a0f3c023731#file-remote-sleep-go
- Run it with
go run ./ - On second terminal run
podman run --rm --network host quay.io/openshift-knative/wathola-senderand observe the rate of sending events. It will be close to 0.5 event per second. It should be 5 events per second (default 200ms interval)
Knative release version
>= v0.15.0
Additional Context This issue was reported during review of #4555
/area test-and-release
I could do this, but maybe someone different is interested in this refactoring?
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
/remove-lifecycle stale
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
/remove-lifecycle stale /reopen
This is still a TODO
@cardil: Reopened this issue.
In response to this:
/remove-lifecycle stale /reopen
This is still a TODO
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
/remove-lifecycle stale /triage accepted
I'm closing this issues as I'm not sure if it's relevant still and has not been update for very long, please reopen if needed