Skip to content
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

The max_remote_stream shown in execution info.tiflash_task is not correct #52646

Closed
JaySon-Huang opened this issue Apr 16, 2024 · 4 comments · Fixed by #52647
Closed

The max_remote_stream shown in execution info.tiflash_task is not correct #52646

JaySon-Huang opened this issue Apr 16, 2024 · 4 comments · Fixed by #52647

Comments

@JaySon-Huang
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

2. What did you expect to see? (Required)

Run explain analyze ... on tiflash queries

The remote_regions and min_remote_stream is 0, but the max_remote_stream is "5818ms"

tiflash_task:{time:5.83s, loops:1152, threads:16}, tiflash_scan:{mvcc_input_rows:0, mvcc_input_bytes:0, mvcc_output_rows:0, lm_skip_rows:0, local_regions:194, remote_regions:0, tot_learner_read:14ms, region_balance:{instance_num: 1, max/min: 194/194=1.000000}, delta_rows:0, delta_bytes:0, segments:105, stale_read_regions:0, tot_build_snapshot:0ms, tot_build_bitmap:16ms, tot_build_inputstream:146ms, min_local_stream:4573ms, max_local_stream:5818ms, min_remote_stream:0ms, max_remote_stream:5818ms, dtfile:{data_scanned_rows:71997669, data_skipped_rows:0, mvcc_scanned_rows:0, mvcc_skipped_rows:0, lm_filter_scanned_rows:0, lm_filter_skipped_rows:0, tot_rs_index_check:26ms, tot_read:2873ms}}

3. What did you see instead (Required)

The max_remote_stream should be 0 when remote_regions is 0

4. What is your TiDB version? (Required)

master

@JaySon-Huang JaySon-Huang added the type/bug This issue is a bug. label Apr 16, 2024
@JaySon-Huang
Copy link
Contributor Author

/label affects-8.1

@JaySon-Huang
Copy link
Contributor Author

/label severity/moderate

Copy link

ti-chi-bot bot commented Apr 16, 2024

@JaySon-Huang: The label(s) severity/moderate cannot be applied. These labels are supported: fuzz/sqlancer, challenge-program, compatibility-breaker, first-time-contributor, contribution, good first issue, correctness, duplicate, proposal, security, ok-to-test, needs-ok-to-test, needs-more-info, needs-cherry-pick-release-5.4, needs-cherry-pick-release-6.1, needs-cherry-pick-release-6.5, needs-cherry-pick-release-7.1, needs-cherry-pick-release-7.5, needs-cherry-pick-release-8.1, affects-5.4, affects-6.1, affects-6.5, affects-7.1, affects-7.5, affects-8.1, may-affects-5.4, may-affects-6.1, may-affects-6.5, may-affects-7.1, may-affects-7.5, may-affects-8.1.

In response to this:

/label severity/moderate

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@JaySon-Huang
Copy link
Contributor Author

/severity moderate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants