The workaround is to comment on the section. For example:
We get the following line in our pt-stalk output file and the ps-lock-transactions files are not created:
Environment
None
AFFECTED CS IDs
CS0041887
Activity
Show:
Leonardo Bacchi Fernandes November 27, 2023 at 5:47 PM
It might be a good idea to have one parameter that we can use to skip any data collected. For example: --skip-collection=ps-lock-transactions,global-variables. This is interesting for cases where pt-stalk may cause issues with certain data collections. There are some versions with known bugs that may cause the server to lockup by querying variables_by_thread (https://jira.percona.com/browse/PS-7250), or show full processlist (https://jira.percona.com/browse/PS-8683). In those cases, we usually resort to collecting the data manually through queries, but it would be nice if we could use pt-stalk with a --skip-collection parameter.
Data collection for ps-locks-transactions is the one below:
The workaround is to comment on the section. For example:
We get the following line in our pt-stalk output file and the
ps-lock-transactionsfiles are not created: