yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
78f14b668b315fcd2228aa39cfc9c2d4211d6c7f
doc-exports/docs/taurusdb/umn/en-us_topic_0000002521502463.html
wangdengke2 78f14b668b taurusdb_umn 
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2026-03-11 14:56:23 +00:00

4.1 KiB
Raw Blame History

Managing Real-Time Sessions

Scenarios

You can view current session statistics of your instance and kill abnormal sessions.

Constraints

Killing a session may cause the application to disconnect from the instance. Your application should be able to reconnect to the instance.

Setting a Slow Session Threshold

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, click the instance name.
  5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
  6. Click the Sessions tab to view current session statistics by user, access host, and database.

  7. In the session list, select the abnormal session you want to kill and click Kill Session to recover the database.

    A maximum of 20 sessions can be killed at once.

    To kill sessions automatically, see Using Auto Kill Sessions.

Parent topic: Problem Diagnosis