Help Center/ Data Admin Service/ User Guide/ DDS/ Intelligent O&M/ Sessions
Updated on 2026-07-28 GMT+08:00
View PDF
Share

Sessions

You can manage sessions in the following scenarios:

  • If the number of sessions of an instance has reached the upper limit and the instance cannot be logged in to any longer, you can view and kill unnecessary sessions using the emergency channel function.
  • You can view history logs to learn details of the kill operations that you performed using the emergency channel function.

Killing a session may cause instance or service exceptions.

Usage Notes

  • If it can be logged in to through DAS, log in to your instance on the DAS console and enter the commands to kill the sessions in question from there.
  • Use this function in urgent conditions. All your kill operations will be logged.
  • DB instances of Community Edition 3.4, 4.0, 4.2, and 4.4 are supported.
  • Instances in the creating, frozen or abnormal state are not supported.
  • Killing inactive sessions is not allowed.

Procedure

  1. Log in to the DAS console.
  2. Click in the upper left corner and select a region and project.
  3. In the navigation pane, choose Intelligent O&M > Instance List.

    Alternatively, on the Overview page, click Go to Intelligent O&M.

  4. Choose Sessions.
  5. On the displayed Emergency Channel page, view session statistics of the current instance node by overview, host, or namespace.
  6. In the session list, select the target session and click Kill Session.

    Figure 1 Killing a session

  7. In the Kill Session dialog box, confirm the session information and click Yes.
  8. Click History Logs to view the sessions killed through the emergency channel.

    Figure 2 Viewing history logs

  9. Click Export to download some or all history logs.

    Figure 3 Exporting history logs

Parent topic: Intelligent O&M