tiflash: add the alert-rules.md#2191
Merged
Merged
Conversation
toutdesuite
added
needs-cherry-pick-3.1
priority/P2
Contributor
|
Please resolve conflict. @toutdesuite |
yikeke
reviewed
Apr 10, 2020
|
|
||
| # TiFlash Alert Rules | ||
|
|
||
| This documents introduces the alert rules of the TiFlash cluster. |
Contributor
There was a problem hiding this comment.
Suggested change
| This documents introduces the alert rules of the TiFlash cluster. | |
| This document introduces the alert rules of the TiFlash cluster. |
Please do not make this mistake again.
|
|
||
| `increase(tiflash_schema_apply_count{type="failed"}[15m]) > 0` | ||
|
|
||
| - Rule description: |
Contributor
There was a problem hiding this comment.
Keep the format consistent with other alert rule docs, e.g. https://pingcap.com/docs/dev/reference/alert-rules/
Please apply the correct format to the whole document! @toutdesuite
|
|
||
| - Rule description: | ||
|
|
||
| You can get an alert when the schema apply error occurs. |
Contributor
There was a problem hiding this comment.
Suggested change
| You can get an alert when the schema apply error occurs. | |
| When the schema apply error occurs, an alert is triggered. |
Keep the same description format as the other doc: https://pingcap.com/docs/dev/reference/alert-rules/
Please update the other places in this document. @toutdesuite
|
|
||
| - How to handle: | ||
|
|
||
| The error might be caused by the logical problem. Get in touch with the TiFlash R&D. |
Contributor
There was a problem hiding this comment.
Suggested change
| The error might be caused by the logical problem. Get in touch with the TiFlash R&D. | |
| The error might be caused by some wrong logic. Contact [TiFlash R&D](mailto:support@pingcap.com) for support. |
Please update the other similar places to Contact [TiFlash R&D](mailto:support@pingcap.com) for support.. @toutdesuite
|
|
||
| > **Note:** | ||
| > | ||
| > `read index` is the kvproto request sent to the TiKV leader. TiKV region retries, busy Store, or network problems might lead to long request time of read index. |
Contributor
There was a problem hiding this comment.
Suggested change
| > `read index` is the kvproto request sent to the TiKV leader. TiKV region retries, busy Store, or network problems might lead to long request time of read index. | |
| > `read index` is the kvproto request sent to the TiKV leader. TiKV region retries, busy store, or network problems might lead to long request time of `read index`. |
yikeke
reviewed
Apr 10, 2020
|
|
||
| - How to handle: | ||
|
|
||
| The frequent retries might be caused by frequent TiKV cluster split events or frequent TiKV cluster migrations. You can check the TiKV cluster status to identify the retry reason. |
Contributor
There was a problem hiding this comment.
Suggested change
| The frequent retries might be caused by frequent TiKV cluster split events or frequent TiKV cluster migrations. You can check the TiKV cluster status to identify the retry reason. | |
| The frequent retries might be caused by frequent splitting or migration of the TiKV cluster. You can check the TiKV cluster status to identify the retry reason. |
yikeke
reviewed
Apr 10, 2020
|
|
||
| - How to handle: | ||
|
|
||
| It might be caused by communications problems between TiKV and Proxy. Get in touch with the TiFlash R&D. |
Contributor
There was a problem hiding this comment.
Suggested change
| It might be caused by communications problems between TiKV and Proxy. Get in touch with the TiFlash R&D. | |
| It might be caused by a communications error between TiKV and the proxy. Get in touch with the TiFlash R&D. |
Contributor
Author
|
@yikeke PTAL again. Thanks! |
yikeke
reviewed
Apr 10, 2020
Contributor
|
/merge |
sre-bot
added
the
status/can-merge
Contributor
|
/run-all-tests |
sre-bot
added a commit
to sre-bot/docs
that referenced
this pull request
Apr 10, 2020
* add the alert-rules.md * address comments * Apply suggestions from code review Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com>
5 tasks
Contributor
|
cherry pick to release-3.1 in PR #2243 |
sre-bot
added a commit
to sre-bot/docs
that referenced
this pull request
Apr 10, 2020
* add the alert-rules.md * address comments * Apply suggestions from code review Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com>
5 tasks
Contributor
|
cherry pick to release-4.0 in PR #2244 |
yikeke
added a commit
that referenced
this pull request
Apr 10, 2020
* add the alert-rules.md * address comments * Apply suggestions from code review Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com> Co-authored-by: toutdesuite <guizhiluo2014@163.com> Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com>
sre-bot
added a commit
that referenced
this pull request
Apr 10, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
add the alert-rules.md
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?