Details
-
Task
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
23.02
-
None
-
None
Description
review the tool in https://github.com/mariadb-edwardstoever/columnstore_review
David's suggestion below
At the least, the following information should be contained in the reports:
- Columnstore version
- Build hash (hopefully)
- Number of servers and how many are configured for accepting queries
- Number of cores per server, RAM per server and anything else hardware we can think of.
- Topology such as type of storage (s3, single data disk, shared nothing), aws, google, on-prem, skysql, etc.
- Which server is currently prime.
- Printout of Columnstore.xml
- Print of all the files in my.cnf (or wherever .cnf files are kept)
- If it can be found, the contents of mariadb .err file
- All contents of /var/logs/mariadb/columnstore (or wherever logs are kept).
- If we can figure it out, the contents of the bulk load logs.
- Anything else we can think of that might help us figure stuff out.
All this and more used to be produced by ColumnstoreSupport executable (which called a bunch of shell scripts that ran some other things) That code can still be found in the develop-5 branch oamapps/columnstoreSupport for reference.