gRPC
8 RESOURCE_EXHAUSTED
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
When You See This Code
A rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.
How to Fix
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
Specification
View RFC / Specification →Cross-Protocol Equivalents
Comparisons
Guides
Choosing the Right HTTP Status Codes for REST APIs
API Design
gRPC Status Codes: A Practical Guide
API Design
Debugging Timeout Errors: 408 and 504
Debugging & Troubleshooting
How to Implement and Handle Rate Limiting (429)
API Design
API Versioning Strategies: URL, Header, and Query Param
API Design
Designing Consistent API Error Responses
API Design
API Keys vs OAuth vs JWT: Choosing the Right Auth Method
Security & Authentication