-
Notifications
You must be signed in to change notification settings - Fork 411
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
Slow get segment snapshot causes read timeout when there are multiple tables #7713
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
12 tasks
JaySon-Huang
added
feature/developing
and removed
may-affects-5.2
may-affects-5.3
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
labels
Jun 28, 2023
JaySon-Huang
added
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
and removed
feature/developing
labels
Jun 28, 2023
This was referenced Jun 28, 2023
JaySon-Huang
changed the title
Disagg read timeout under S3 arch
Slow get segment snapshot causes read timeout when there are multiple tables
Jun 30, 2023
Reopen because it leads to the max snapshot lifetime not shown on Grafana affects version: |
12 tasks
This was referenced Sep 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
The time cost by acquiring segment snapshot should be acceptable. For example, within hundred ms
3. What did you see instead (Required)
The time cost by acquiring segment snapshots causes more than 30 seconds
4. What is your TiFlash version? (Required)
7aafea8
The text was updated successfully, but these errors were encountered: