gRPC status 11: OUT_OF_RANGE
OUT_OF_RANGE is gRPC status code 11. The request went past the valid range, such as reading beyond the end of a file or a page past the last.
Updated
Usual causes
- A page token, offset or cursor past the end of the data.
- A date or index outside the range the data currently covers.
What to check
- The offset or cursor sent against the size of the data.
- Whether the loop reading pages stops on
OUT_OF_RANGE; for iteration it is the expected end signal.
Not to be confused with
A value that is invalid whatever the data holds, such as a negative page size, is INVALID_ARGUMENT.
What it looks like
A typical error, as a Go client prints it: rpc error: code = OutOfRange desc = offset 1200 is past the end of the log (1024 entries)
Retry, and the HTTP equivalent
| OUT_OF_RANGE | |
|---|---|
| Code | 11 |
| Name | OUT_OF_RANGE |
| In istek's status bar | out_of_range |
| Retry | No, unless the data may have grown since. |
| HTTP status | 400 |
istek names the status of every call it makes, out_of_range included, and explains transport failures in plain words. See istek.