Help Center > > User Guide> Console> Emergency Channel

Emergency Channel

Updated at: May 14, 2020 GMT+08:00

Scenarios

  • Emergency Channel
    1. If the maximum number of sessions for an instance has been reached and the instance cannot be logged in to, you can view and kill unnecessary sessions through the emergency channel.
    2. Only RDS MySQL databases support emergency channel currently. Self-built databases on ECSs and instances whose status is creating, frozen, and abnormal do not support this function.
    3. Use this function in urgent conditions. All your kill operations will be recorded in logs.
    4. If your instance can be logged in to on the DAS console, log in to the instance and perform desired operations through Real-Time Sessions & Performance.
    5. Sessions of sensitive users, like rdsadmin, rdsbackup, and rdsmetric, cannot be killed.
  • History Logs

    History emergency operation list

Prerequisites

You have logged in to the DAS console.

Procedure

  1. In the navigation pane on the left, choose Cloud DBA > Emergency Channel.
  2. On the displayed page, select an instance and click OK.
  3. In the session list, sessions are sorted by session duration in descending order by default. Select the sessions you want to kill.
  4. Click Kill. In the displayed dialog box, click Yes.

  5. Click the History Logs tab and view information about the historical kill operations.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel