gRPC status 15: DATA_LOSS
DATA_LOSS is gRPC status code 15. Data was lost or corrupted beyond recovery, such as stored data that fails its checksum. The client cannot fix it.
Updated
Usual causes
- Stored data failed a checksum or could not be read back.
- A file or object was truncated.
What to check
- The server's storage and its logs; the client cannot fix this.
- Whether a backup or replica holds a good copy.
What it looks like
A typical error, as a Go client prints it: rpc error: code = DataLoss desc = chunk 18 failed checksum
Retry, and the HTTP equivalent
| DATA_LOSS | |
|---|---|
| Code | 15 |
| Name | DATA_LOSS |
| In istek's status bar | data_loss |
| Retry | No. |
| HTTP status | 500 |
istek names the status of every call it makes, data_loss included, and explains transport failures in plain words. See istek.