Logs and metrics pertaining resolved_ts gap can be wrong if TSO fetch fails

## Bug Report



https://github.com/tikv/tikv/blob/261458672ab66e6acef5017535783628e62bb76c/components/resolved_ts/src/advance.rs#L109-L113

`last_pd_tso` may be updated to 0.

The field is only used for diagnosis.
The consequence can be misleading gaps in logs and metrics, but not correctness risks.

### What version of TiKV are you using?


master and versions in [v7.3, v8.5]

### What operating system and CPU are you using?


### Steps to reproduce


### What did you expect?

### What did happened?

	// Ignore get tso errors since we will retry every `advdance_ts_interval`.
	let mut min_ts = pd_client.get_tso().await.unwrap_or_default();
	if let Ok(mut last_pd_tso) = last_pd_tso.try_lock() {
	*last_pd_tso = Some((min_ts, Instant::now()));
	}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Logs and metrics pertaining resolved_ts gap can be wrong if TSO fetch fails #17989

Bug Report

What version of TiKV are you using?

What operating system and CPU are you using?

Steps to reproduce

What did you expect?

What did happened?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Logs and metrics pertaining resolved_ts gap can be wrong if TSO fetch fails #17989

Description

Bug Report

What version of TiKV are you using?

What operating system and CPU are you using?

Steps to reproduce

What did you expect?

What did happened?

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions