-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Feature Flag productCatalogFailure
raising errors on Recommendation Service
#1710
Comments
The more I think about this the more I believe this is working as expected. This is a great example on how one error can impact multiple services and multiple endpoints. Not sure if we should work this around for demo purposes. @reese-lee I'd love to hear your opinion on this. |
@reese-lee we have discussed that in the SIG meeting and it seems that this is expected. |
@julianocosta89 I see, I'm trying to understand why recommendationservice isn't impacted by the issue. So, recommendationservice doesn't generate an error, because it's generating the list of products (including the problem product ID) that is then supplied to productcatalogservice when requested by frontend, and since the error doesn't occur until productcatalogservice attempts to give it to frontend, there's no issue for recommendationservice? Edited to clarify: the span generated by recommendationservice when it executes |
@reese-lee I must have lost this comment, sorry about that. Does that make sense? |
Closing this, as this error is being raised as expected. |
Bug Report
Which version of the demo you are using?
52d315a
Symptom
What is the expected behavior?
When enabling the feature flag
productCatalogFailure
it is expected to have an error generated forGetProduct
requests with product ID:OLJCESPC7Z
.What is the actual behavior?
Currently the error is also being trigged in requests for recommendation service whenever the product
OLJCESPC7Z
is returned in the recommendation list.Reproduce
productCatalogFailure
http://localhost:8080/loadgen/
and check the tabFailures
.The text was updated successfully, but these errors were encountered: