@Pause — Initiates admin mode on the cluster.
The @Pause system procedure initiates admin mode on the cluster. In admin mode, no further transaction requests are accepted from clients on the client port. All interactions with a database in admin mode must occur through the admin port specified in the deployment file.
There may be existing transactions still in the queue after admin mode is initiated. Until these transactions are completed, the database is not entirely paused. You can use the @Statistics system procedure with the "LIVECLIENTS" keyword to determine how many transactions are outstanding for each client connection.
The goal of admin mode is to pause the system and ensure no further changes to the database can occur when performing sensitive administrative operations, such as taking a snapshot before shutting down.
Several important points to consider concerning @Pause are:
@Pause must be called through the admin port, not the standard client port.
Although new stored procedure invocations received on the client port are rejected in admin mode, existing connections from client applications are not removed.
However, if export is enabled when admin mode is invoked, any connection from an export client to the client port is terminated and further connections refused. The export client will attempt to reconnect until normal operations are resumed and the connection is re-established. Export clients connected to the admin port are not affected.
To return to normal database operation, you must call the system procedure @Resume on the admin port.
Returns one VoltTable with one row.
|STATUS||BIGINT||Always returns the value zero (0) indicating success.|