-
Notifications
You must be signed in to change notification settings - Fork 38
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
Proposal: change the responce code in eventshub receiver for dropped events #211
Comments
@vaikas What do you think of this? |
Not totally sure if this would fit your use case, but for RabbitMQ Broker, I ended up using this: With some more context here: |
Thanks! It is very helpful! |
Great to hear :) Ping me if you need some more help :) |
@vaikas Hi, what do you think we add a new env I think in my scenario(knative/eventing#5457), it might not be good to modify the default strategy of cloudevent.Client |
@xinydev makes sense to me, and it will be a lot useful for testing the behavior of some specific status codes with the upcoming changes here https://github.com/knative/specs/pull/24/files#diff-e71710278fc6ee3296a229b7448808ab0869b6ce9b3232a695b6f57fbc7ea6fdR95 |
/assign |
I am writing an e2e test for apiServerSource's retry feature, but the
cloudevents.Client
only retries when the HTTP response code is one of these.I want to use eventshub to simulate a events lost scenario but the eventshub returns http.StatusConflict when dropping events. and the
http.StatusConflict
is not one of the codes whichcloudevents.Client
retries.So I have a question. Is there any special reason to choose
http.StatusConflict
?Can we change it to
429(Too Many Requests)
or503(Service Unavailable)
or504(Gateway Timeout)
for some tests scenario like retring?Or is there any advices for this e2e test?
The text was updated successfully, but these errors were encountered: