[Remote Store] RFC - Adding segment download metrics to remotestore stats API #8395
Labels
enhancement
Enhancement or improvement to existing feature or request
RFC
Issues requesting major changes
Storage:Durability
Issues and PRs related to the durability framework
Storage
Issues and PRs relating to data and metadata storage
Overview
As of today the _remotestore/stats API only shows the segment upload stats. We are planning on integrating segment download stats to this API also. That would provide the end user with vital stats related to segment downloads and troubleshoot slow index recovery times.
The _remotestore/stats API only takes into account the primary shard copies for an index. This is because, the primary shard copy is taking part in all the segment uploads to the remote store. The replica shard copies on the other hand would only download segments from the remote store as and when it is required.
Metrics to be added:
We are suggesting the following metrics to be added for tracking segment downloads from the remote store:
last_download_timestamp
: Last timestamp in milliseconds when the download from remote store succeededtotal_files_downloaded
: Would be available in started, succeeded and failed statistics. This would track the total number of files that have been downloaded from the remote store.total_files_downloaded_in_bytes
: Would be available in started, succeeded and failed statistics. This would track the total size of files downloaded from the remote storedownload_size_in_bytes
: Would be available in moving_avg and last_successful stat. Would track the last successfully downloaded segment size and average size of the downloaded payload from the remote storedownload_speed_in_bytes_per_sec
: Would be available in moving_avg stat. Would track the average speed of downloads from the remote storedownload_latency_in_millis
: Would be available in moving_avg stat. Would be used to track time taken for downloads from the remote store to completeWe are also proposing a change in the API output for remotestore stats for this. The new API output would be like the sample mentioned below:
Path:
Response:
and along the same lines:
Path:
Response:
This API format change would also accommodate the newer Translog Upload stats metrics that are being proposed on: #8311
The text was updated successfully, but these errors were encountered: