-
Notifications
You must be signed in to change notification settings - Fork 598
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
Added the Troubleshooting section #10888
Added the Troubleshooting section #10888
Conversation
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
@@ -0,0 +1,11 @@ | |||
To diagnose network issues, use the healthcheck in the [Embedded UI](../../../../../reference/embedded-ui/index.md): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be wrong, but I believe that network issues in UI are related to connectivity issues, i.e. when some nodes are not reachable. But other network issues are probably not displayed in our UI. Instead, user should check metrics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a step to use third-party tools to monitor network performance metrics
ydb/docs/en/core/dev/troubleshooting/performance/infrastructure/hardware.md
Show resolved
Hide resolved
|
||
1. Open the **CPU** dashboard in Grafana. | ||
|
||
1. See if the following charts show any spikes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add information how to check CPU utilization: number of cores used vs. number of cores available.
ydb/docs/en/core/dev/troubleshooting/performance/hardware/insufficient-memory.md
Outdated
Show resolved
Hide resolved
ydb/docs/en/core/dev/troubleshooting/performance/hardware/cpu-bottleneck.md
Outdated
Show resolved
Hide resolved
|
||
{% note info %} | ||
|
||
You can also use the [Healthcheck API](../../../../reference/ydb-sdk/health-check-api.md) in your application to get this information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably, we can write something like
It is also recommended to use the Healthcheck API
(we are using it in internal installations, by the way)
Task opensource active checks
sounds good for SRE Team @kobzonega
ydb/docs/en/core/dev/troubleshooting/performance/system/ydb-updates.md
Outdated
Show resolved
Hide resolved
ydb/docs/en/core/dev/troubleshooting/performance/system/ydb-updates.md
Outdated
Show resolved
Hide resolved
ydb/docs/en/core/dev/troubleshooting/performance/system/_includes/tablets-moved.md
Outdated
Show resolved
Hide resolved
ydb/docs/en/core/dev/troubleshooting/performance/schemas/_includes/splits-merges.md
Outdated
Show resolved
Hide resolved
...s/en/core/dev/troubleshooting/performance/schemas/_includes/overloaded-shards-diagnostics.md
Outdated
Show resolved
Hide resolved
ydb/docs/en/core/dev/troubleshooting/performance/queries/overloaded-errors.md
Outdated
Show resolved
Hide resolved
ydb/docs/en/core/dev/troubleshooting/performance/infrastructure/hardware.md
Outdated
Show resolved
Hide resolved
...s/en/core/dev/troubleshooting/performance/schemas/_includes/overloaded-shards-diagnostics.md
Outdated
Show resolved
Hide resolved
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
bbf9f83
to
46d6d90
Compare
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
04e3e02
to
0446a8a
Compare
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
0446a8a
to
73f196d
Compare
✅ Documentation buildRevision built successfully |
73f196d
to
bcc2d3e
Compare
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
⚪ Test history | Ya make output | Test bloat
🟢 |
⚪ Test history | Ya make output | Test bloat
🟢 |
✅ Documentation buildRevision built successfully |
Changelog category
Additional information
Added a new section about Troubleshooting performance issues