{question}
How to Collect mv_processlist and mv_bt Information in SingleStore?
{question}
{answer}
Understanding the current state of the cluster is vital when troubleshooting issues like slowness, stuck queries, or unusual engine behavior. Two valuable sources of diagnostic data are:
-
information_schema.mv_processlist -
information_schema.mv_bt
These views offer insights into active queries and backtraces, respectively.
When should you gather this information?
To be most effective, these outputs should be collected while the issue is occurring. Capturing them in real time helps to identify the root cause more accurately.
Although cluster reports usually include this information, they may be generated after the issue has been addressed. In such cases, collecting mv_processlist and mv_bt manually can be invaluable.
Cluster reports remain highly recommended for thorough analysis and subsequent investigations.
How to collect the data manually?
You can utilize the following commands to gather live process lists and backtrace data (adjust the credentials and endpoint details as necessary):
mysql -u admin -h my_dml_endpoint -P 3306 --default-auth=mysql_native_password --password -e "SET sql_select_limit = 18446744073709551615; SELECT now(), * FROM information_schema.mv_processlist;" > mv_processlist.txt
mysql -u admin -h my_dml_endpoint -P 3306 --default-auth=mysql_native_password --password -e "SET sql_select_limit = 18446744073709551615; SELECT now(), * FROM information_schema.mv_bt;" > mv_bt.txt
Additional Resources
If you need help analyzing the output, feel free to share the files with our Support team via a support ticket.
{answer}