Help Center/ Data Admin Service/ User Guide/ MySQL/ Intelligent O&M (Old Version)/ Sessions/ Sessions that Can Be Killed If Necessary
Updated on 2024-08-29 GMT+08:00
View PDF
Share

Sessions that Can Be Killed If Necessary

You can use this function 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.

Precautions

  • This function is not available to ECS-hosted instances and instances in the creating, frozen, or abnormal state.
  • The kernel version of RDS for MySQL 5.6 must be 5.6.43.3 or later, and the kernel version of RDS for MySQL 5.7 must be 5.7.25.3 or later.
  • Use this function in urgent conditions. All your kill operations will be logged.
  • This function is not recommended if you can log in to your instance on the DAS console. After logging in to the instance, you can 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 DAS 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 box containing your target instance and click Details.
  7. In the upper right corner of the page, click Go to Old Edition.
  8. Choose Sessions > Sessions that Can Be Killed If Necessary and select the sessions you want to kill.

    Sessions are sorted in descending order by duration.

  9. Select the session you want to kill and click Kill.
  10. In the displayed dialog box, confirm the session information and click Yes.
  11. Click the History Logs tab and view the sessions killed.
Parent topic: Sessions