Help Center> Data Admin Service> User Guide> GaussDB(for MySQL)> Intelligent O&M> Sessions> Sessions that Can Be Killed If Necessary
Updated on 2023-12-13 GMT+08:00
View PDF

Sessions that Can Be Killed If Necessary

You can end the sessions that can be killed if necessary 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.

Prerequisites

  • The kernel version of GaussDB(for MySQL) 5.6 must be 5.6.43.3 or later, and the kernel version of GaussDB(for MySQL) 5.7 must be 5.7.25.3 or later.
  • This function is not available to ECS-hosted instances and instances in the creating, frozen, or abnormal state.
  • Use this function in urgent conditions. All your kill operations will be logged.
  • This function is not recommended if your instance can be logged in to on the DAS console. You can choose to log in to the instance and perform required operations on the Real-Time Sessions page.
  • Sessions of sensitive users such as rdsadmin, rdsbackup, rdsmetric, and rdsRepl cannot be killed.
  • When the CPU usage or the number of connections reaches the upper limit, requests to kill sessions may time out. In this case, you have to try more than once.

Procedure

  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, and under Databases, click Data Admin Service.
  4. In the navigation pane, choose Intelligent O&M > Instance List.

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

  5. In the upper right corner of the Instance List page, search for instances by engine type, instance name, or instance IP.

    Figure 1 Searching for instances

  6. Locate the instance whose sessions you want to kill if necessary and click Details.
  7. Choose Sessions > Sessions that Can Be Killed If Necessary. Sessions are sorted and displayed in the session list in descending order by duration.
  8. Select the session that you want to kill and choose Kill.

    Figure 2 Killing a session

  9. In the Kill Session dialog box, confirm the session information and click Yes.
  10. Click History Logs to view the sessions killed through the emergency channel.
Parent topic: Sessions