Managing Real-Time Sessions

Scenarios

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

Constraints

• If the instance is heavily loaded, query results may fail to load due to system traffic limiting.
• Killing a session may cause the application to disconnect from the instance. Your application should be able to reconnect to the instance.
• On the Show killed sessions tab page of the Kill Top 3 dialog box, you can preview the IDs and SQL keywords of matching sessions at the current time. (This preview reflects statistics at the current moment, not the final killing result.) After the request is delivered, you can check the actual results in the session kill history.

Procedure

1. Log in to the RDS console.
2. Click in the upper left corner and select a region.
3. On the Instances page, click the DB instance name.
4. In the navigation pane, choose Sessions under DBA Assistant.
5. On the Sessions page, view current session statistics by login name, access host, and database.
   Figure 1 Sessions
   
   • Killing abnormal sessions

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

   • Killing sessions

     In the session list, click Kill Top 3. In the displayed dialog box, you can preview real-time statistics to view details of sessions matching the kill criteria.

     Kill rules:

     • They are applicable only to SELECT sessions.
     • Sessions are sorted in descending order by start duration and CPU time, and the top 30% from each sort are terminated.
     • The following cases will not be processed: statements containing stored procedures, encrypted statements, or triggers; and non-pure SELECT transactions within large transactions.
       Figure 2 Killing sessions
       

Viewing Killed Sessions

On the Sessions page, click the Killed Top 3 tab and view the execution history of manually killed sessions.

Figure 3 Killing history