# [Known Issue] `grpc-compression-type` does not affect TiKV responses ([tikv#17176](https://github.com/tikv/tikv/issues/17176))

Source note: adapted from GitHub issue [tikv#17176](https://github.com/tikv/tikv/issues/17176).

## Issue

- Link: [tikv#17176](https://github.com/tikv/tikv/issues/17176)
- Summary: in affected versions, TiKV does not apply `grpc-compression-type` to client response paths, so changing the TiKV-side setting alone has no effect for those responses.

## Phenomenon

- `server.grpc-compression-type` is configured on TiKV.
- Operators expect TiKV responses to be compressed.
- In practice, response behavior does not change, so troubleshooting based on this parameter can become misleading.

## Root Cause

In the affected versions, the `grpc-compression-type` setting is not applied consistently to TiKV response paths. As a result, the parameter does not influence the response traffic that users expect it to optimize.

## Diagnostic Steps

1. Confirm that `server.grpc-compression-type` is configured on TiKV.
2. Compare expected and actual response-side behavior in the affected cluster version.
3. If tuning the parameter has no observable effect, suspect this issue rather than a workload-only bottleneck.

## Workaround

- N/A

## Affected Version

- `<= v8.1.0`
- `<= v7.5.2`
- `<= v6.5.10`

## Related Oncall

- v6.5.2 `grpc-compression-type` had no effect in some cases `ONCALL-7215` / `TICKET-4410`