Skip to content
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

Backend service errors result in status other than INTERNAL from frontend services #1936

Open
SanjayVas opened this issue Nov 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@SanjayVas
Copy link
Member

If a frontend service calls a backend service as part of a method implementation, any error from that backend service should result in an INTERNAL gRPC status. This is standard practice for gRPC frameworks such as those used within Google.

Consider DEADLINE_EXCEEDED as an example. Any DEADLINE_EXCEEDED from a backend service should always be considered unexpected. Due to Deadline Propagation, the only time a frontend will receive a DEADLINE_EXCEEDED from a backend is if the backend deadline is too short.

@SanjayVas SanjayVas added the bug Something isn't working label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant