Managing Sessions

Scenarios

You can manage sessions in the following scenarios:

• 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

• This function is not recommended unless you really need it. All your kill operations will be logged.

• DB instances of Community Edition 3.4, 4.0, 4.2, and 4.4 are supported.
• DB instances in the creating, frozen or abnormal state are not supported.
• Killing inactive sessions is not allowed.
• Real-time sessions are generated based on currentOp of a database at the current time point. If the execution time of a session is too short (less than or equal to milliseconds), you are not advised to view real-time sessions. If you need to collect statistics on all operations, see Audit Log Policy Management.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click in the upper left corner of the page and choose Databases > Document Database Service.
4. On the Instances page, click the cluster instance name.
5. In the navigation tree, choose DBA Assistant.
6. Choose Real-Time Diagnosis.
7. Click Real-Time Sessions.
8. On the displayed Emergency Channel page, view session statistics of the current instance node by summary, source, or namespace.
9. By default, sessions are sorted and displayed in the session list in descending order by duration. You can also search for sessions by specifying Sessions lasting longer than or Namespace.
10. Select the sessions that you want to kill and click Kill Session.
11. In the Kill Session dialog box, confirm the session information and click Yes.
12. Click History Logs to view the sessions killed through the emergency channel.