Killing Sessions

Scenarios

You can kill sessions when necessary on the Sessions that Can Be Killed If Necessary tab page. This page covers:

• Emergency Channel: If the maximum number of connections for an instance has been reached and the instance cannot be logged in to, you can view and kill unnecessary sessions through this channel.
• History Logs: You can view history logs to learn details of the kill operations that you performed using the emergency channel.

Precautions

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

Constraints

• Do not kill sessions unless you really need to. All your kill operations will be logged.
• Sessions of sensitive users such rdsAdmin, rdsBackup, rdsMetric, and rdsRepl, and sessions whose username is null cannot be killed.
• You may fail to refresh the session list if your instance has a heavy load. Minimize the resources occupied by the emergency channel. Wait a few seconds and try again.
• If the CPU usage reaches 100%, requests to kill sessions may fail. You may 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.
3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
4. On the Instances page, click the target instance name.
5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
6. Choose Sessions > Sessions that Can Be Killed If Necessary.
   • To kill a session, click the Emergency Channel tab, select the session, and click Kill Session.
     Figure 1 Emergency Channel
     
   • To check the kill history, click the History Logs tab.