-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
HA: inspect the health of kvdb if using separate mount paths on kvdb and raft-engine. #17884
Labels
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.5
This bug affects the 8.5.x(LTS) versions.
type/enhancement
The issue or PR belongs to an enhancement.
user_report
The issue is reported by real TiKV user from their environment.
Comments
LykxSassinator
added
the
type/enhancement
The issue or PR belongs to an enhancement.
label
Nov 25, 2024
LykxSassinator
added
the
user_report
The issue is reported by real TiKV user from their environment.
label
Nov 25, 2024
Merged
9 tasks
9 tasks
LykxSassinator
added
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.5
This bug affects the 8.5.x(LTS) versions.
and removed
may-affects-7.5
may-affects-8.1
may-affects-8.5
labels
Nov 27, 2024
ti-chi-bot bot
pushed a commit
that referenced
this issue
Nov 29, 2024
…rformance factors (#17801) close #17884 This pr introduces an extra and individual inspector to detect whether there exists I/O hung issues on kvdb disk, if the kvdb is deployed with a separate mount path. Signed-off-by: lucasliang <[email protected]> Co-authored-by: Bisheng Huang <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Dec 2, 2024
close tikv#17884 Signed-off-by: ti-chi-bot <[email protected]>
9 tasks
ti-chi-bot bot
pushed a commit
that referenced
this issue
Dec 2, 2024
…rformance factors (#17801) (#17912) close #17884 This pr introduces an extra and individual inspector to detect whether there exists I/O hung issues on kvdb disk, if the kvdb is deployed with a separate mount path. Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: lucasliang <[email protected]> Co-authored-by: lucasliang <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Dec 2, 2024
close tikv#17884 Signed-off-by: ti-chi-bot <[email protected]>
9 tasks
ti-chi-bot bot
pushed a commit
that referenced
this issue
Dec 2, 2024
…individual disk performance factors.(#17801) (#17901) close #17884 This pr introduces an extra and individual inspector to detect whether there exists I/O hung issues on kvdb disk, if the kvdb is deployed with a separate mount path. Signed-off-by: lucasliang <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/tikv
that referenced
this issue
Dec 11, 2024
close tikv#17884 Signed-off-by: ti-chi-bot <[email protected]>
9 tasks
ti-chi-bot bot
pushed a commit
that referenced
this issue
Dec 11, 2024
…rformance factors (#17801) (#17980) close #17884 This pr introduces an extra and individual inspector to detect whether there exists I/O hung issues on kvdb disk, if the kvdb is deployed with a separate mount path. Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: lucasliang <[email protected]> Co-authored-by: lucasliang <[email protected]>
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-7.5
This bug affects the 7.5.x(LTS) versions.
affects-8.1
This bug affects the 8.1.x(LTS) versions.
affects-8.5
This bug affects the 8.5.x(LTS) versions.
type/enhancement
The issue or PR belongs to an enhancement.
user_report
The issue is reported by real TiKV user from their environment.
Development Task
Recently, users have reported that TiKV is missing the inspector for the health of kvdb when deployed with a separate mount path. This issue prevents TiKV from detecting I/O hung issues on kvdb, which can impact the end-to-end accessibility of TiKV clusters. And this case is also a HA related issue, ref: #15909.
Therefore, it is essential to enhance TiKV's inspecting ability to address this issue and improve the SLA in this scenario.
The text was updated successfully, but these errors were encountered: