[MCOL-827] Document where to run troubleshooting utilities Created: 2017-07-21  Updated: 2017-09-21  Resolved: 2017-09-21

Status: Closed
Project: MariaDB ColumnStore
Component/s: Documentation
Affects Version/s: 1.0.9
Fix Version/s: Icebox

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Geoff Montee (Inactive)
Resolution: Fixed Votes: 0
Labels: documentation

Sprint: 2017-19

 Description   

The MariaDB ColumnStore documentation lists several troubleshooting utilities here:

https://mariadb.com/kb/en/mariadb/system-troubleshooting-mariadb-columnstore/#mariadb-columnstore-troubleshooting-utilities

But the documentation doesn't say on which node to run these utilities. Are they run on UM1 or PM1? Or do they need to be run on each node individually?



 Comments   
Comment by David Thompson (Inactive) [ 2017-09-20 ]

GeoffMontee I think this was already updated, can you confirm and let us know if this can be closed?

Comment by Geoff Montee (Inactive) [ 2017-09-20 ]

I still do not see the requested information on the "MariaDB ColumnStore troubleshooting utilities" section of that page:

https://mariadb.com/kb/en/library/system-troubleshooting-mariadb-columnstore/#mariadb-columnstore-troubleshooting-utilities

It explains that there are tools like "cleartablelock", "viewtablelock", etc., but it does not say where to run those tools.

Comment by David Thompson (Inactive) [ 2017-09-20 ]

these can run from columnstore server but the default / convention is always to run from pm1. hill - can you update the doc?

Comment by David Hill (Inactive) [ 2017-09-21 ]

Done...I also broken to the utilities in sections to help better explain them and where they should be used.

https://mariadb.com/kb/en/library/system-troubleshooting-mariadb-columnstore/#mariadb-columnstore-utilities

Geoff Montee - please review

Comment by David Hill (Inactive) [ 2017-09-21 ]

update made, please review

Comment by Geoff Montee (Inactive) [ 2017-09-21 ]

The latest updates are great. Thanks!

Generated at Thu Feb 08 02:24:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.