rollback transaction
The rollback transaction command attempts to roll back the uncommitted transaction(s) for the metaspace member on which the command is invoked, provided the member is still connected to the cluster.
The all option causes all uncommitted transactions for all metaspace members to be rolled back. Specifying the name of a metaspace member causes the uncommitted transaction for the specified metaspace member to be rolled back. Specifying transaction_id will cause the transaction with the indicated id to be rolled back.
Parameters
The following table describes the parameters for this command.
| Parameter | Description |
|---|---|
| all | Specify all to roll back all transactions for all metaspace members. |
| member_name | Specify a member name to roll back the committed transactions for a specified space member. |
| transaction_id | Specify a transaction ID to roll back a transaction with a specific transaction ID. |
Caution: When you commit or rollback a transaction from as-admin, the member which began the transaction continues to remain in the transaction, if member is still connected to the cluster. So that member must either commit or rollback the transaction before it can start another transaction. However, the commit or rollback by the member will have no effect on the space since
as-admin has already performed a commit or rollback on the original tuples in the transaction. To avoid this issue, use
execute on member to cause the commit or rollback to be performed by the member owning the transaction. This command succeeds only if the member is still connected to the cluster.
Related concepts
Related tasks
Related reference
Copyright © Cloud Software Group, Inc. All rights reserved.