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

Change tidb_memory_usage_alarm_ratio scope to instance (#5988) #5992

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update system-variables.md
  • Loading branch information
TomShawn authored Jul 16, 2021
commit edf5cb1baddf75ef506a606328b2d88c0c0fcd7b
1 change: 0 additions & 1 deletion system-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -555,7 +555,6 @@ Constraint checking is always performed in place for pessimistic transactions (d
- TiDB triggers an alarm when the percentage of the memory it takes exceeds a certain threshold. For the detailed usage description of this feature, see [`memory-usage-alarm-ratio`](/tidb-configuration-file.md#memory-usage-alarm-ratio-new-in-v409).
- You can set the initial value of this variable by configuring [`memory-usage-alarm-ratio`](/tidb-configuration-file.md#memory-usage-alarm-ratio-new-in-v409).

>>>>>>> 93009172f (Change tidb_memory_usage_alarm_ratio scope to instance (#5988))
### tidb_metric_query_range_duration <span class="version-mark">New in v4.0</span>

- Scope: SESSION
Expand Down