Why doesn't _cat/recovery honor the bytes=XX in the URI?

DavidTurner · March 21, 2019, 8:42am

It looks like this is an oversight in the code that serves the GET _cat/recovery API:

elastic/elasticsearch/blob/99f88f15c5febbca2d13b5b5fda27b844153bf1a/server/src/main/java/org/elasticsearch/rest/action/cat/RestRecoveryAction.java#L167-L170


t.addCell(state.getIndex().totalRecoverBytes());
t.addCell(state.getIndex().recoveredBytes());
t.addCell(String.format(Locale.ROOT, "%1.1f%%", state.getIndex().recoveredBytesPercent()));
t.addCell(state.getIndex().totalBytes());

These values are returned as numbers, not as ByteSizeValues, so the ?bytes= parameter doesn't apply. Could you open an issue on Github, @slmingol?

Topic		Replies	Views
Calculate the correct recovery.max_bytes_per_sec Elasticsearch	1	359	April 21, 2021
Values less than -1 bytes are not supported when cat/indices Elasticsearch	1	63	April 27, 2025
Every shard showing up in /_cat/recovery Elasticsearch	3	570	July 6, 2017
Need clarity on recovery throttling parameters impacting snapshot restores Elasticsearch snapshot-and-restore	2	604	August 5, 2021
I need to get store.size in GB from _cat/indices for all indices Kibana	10	1308	March 6, 2024

Why doesn't _cat/recovery honor the bytes=XX in the URI?

Related topics