-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snapshot status API returns different timing information than snapshot info API #43074
Comments
Pinging @elastic/es-distributed |
This is indeed a little strange. For the snapshot status API we return a serialized |
* We don't have to calculate the start and end times form the shards for the status API, we have the start time available from the CS or the `SnapshotInfo` in the repo and can either take the end time form the `SnapshotInfo` or take the most recent time from the shard stats for in progress snapshots * Closes elastic#43074
* We don't have to calculate the start and end times form the shards for the status API, we have the start time available from the CS or the `SnapshotInfo` in the repo and can either take the end time form the `SnapshotInfo` or take the most recent time from the shard stats for in progress snapshots * Closes #43074
* We don't have to calculate the start and end times form the shards for the status API, we have the start time available from the CS or the `SnapshotInfo` in the repo and can either take the end time form the `SnapshotInfo` or take the most recent time from the shard stats for in progress snapshots * Closes elastic#43074
* We don't have to calculate the start and end times form the shards for the status API, we have the start time available from the CS or the `SnapshotInfo` in the repo and can either take the end time form the `SnapshotInfo` or take the most recent time from the shard stats for in progress snapshots * Closes #43074
Snapshot info API returns the following stats for a given snapshot:
Snapshot status API returns the following overall stats for the same snapshot:
Note that the
start_time_in_millis
values are different. The overall duration is also different, iftime_in_millis
is meant to represent the same duration asduration_in_millis
.I'm not sure if this is a bug or expected behavior. If it is expected, the difference should be documented more clearly.
Full request and responses
The text was updated successfully, but these errors were encountered: