Skip to content

Commit

Permalink
feat: add more clarification for tables queried for troubleshooting (#…
Browse files Browse the repository at this point in the history
…1895)

Signed-off-by: Manan Gupta <[email protected]>
  • Loading branch information
GuptaManan100 authored Nov 29, 2024
1 parent b7cb2c6 commit 0108e72
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ There are several methods to determine whether something has gone wrong in distr
## Fixing Issues

Once a transaction has been identified as irreversibly failed, human intervention is required to correct the database state. You will need the DTID(s) from the previous step. Follow these steps:
1. Query the `redo_state` and `redo_statement` tables on all participating shards using the DTID to get more information about the transaction.
1. Query the `redo_state` and `redo_statement` tables on all participating shards using the DTID to get more information about the transaction. To query these tables, you will have to connect directly to the MySQL instances running alongside vttablets. These tables cannot be queried via vtgate.
2. Each shard will display the status of the transaction on that shard. For shards where the transaction has failed, the information will include the writes that were part of the transaction.
3. Using this information, rerun the relevant writes directly on each of the failing shards.
4. After making the necessary changes, conclude the transaction by running the [`Conclude` CLI command](../../../reference/programs/vtctldclient/vtctldclient_distributedtransaction/vtctldclient_distributedtransaction_conclude).
Expand Down

0 comments on commit 0108e72

Please sign in to comment.