Hi, According to http-grpc-status-mapping.md <https://github.com/grpc/grpc/blob/v1.66.2/doc/http-grpc-status-mapping.md>, HTTP 429 Too Many Requests is translated into gRPC UNAVAILABLE rather than RESOURCE_EXHAUSTED. However, at some point in the past, statuscodes.md <https://github.com/grpc/grpc/blob/v1.23.1/doc/statuscodes.md> said RESOURCE_EXHAUSTED. Is there any reason the gRPC team changed the recommended mapping for HTTP 429 status? Why is UNAVAILABLE is better than RESOURCE_EXHAUSTED for HTTP 429?
I'm asking this question not only to solve my own curiosity, but also to give a better answer to the bug report <https://github.com/line/armeria/issues/5928> for Armeria's gRPC status code mapping that merely follows what grpc-java does. Thanks, T -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/24702a70-915d-41d5-a9a1-e477bfaf8a05n%40googlegroups.com.
