Ticket 8537 - (in)compatible/validated/recommended data base version
Summary: (in)compatible/validated/recommended data base version
Status: RESOLVED WONTFIX
Alias: None
Product: Slurm
Classification: Unclassified
Component: Documentation (show other tickets)
Version: 20.02.x
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Jason Booth
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-02-19 13:13 MST by S Senator
Modified: 2020-02-19 15:17 MST (History)
0 users

See Also:
Site: LANL
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description S Senator 2020-02-19 13:13:29 MST
(In reply to Felip Moll https://bugs.schedmd.com/show_bug.cgi?id=7677#c12)
> After more investigation I see that in MySQL >= 5.7 the row format is DYNAMIC

Does SchedMD have a recommendation with respect to either specific data base features or data base version numbers which have been proven to be best-fit implementations for slurm?

Ideally if a (small) table were included in the documentation (or expect tests suite results?) which would indicate
1) validated and recommended products and versions of databases, possibly including specific features that differentiate a valid version vs. a recommended version
1) whether mariadb, mysql or other (percona?) db
2) what specific versions of those db are validated and/or recommended
   For example, if mysql and 5.7 were recommended, to specify whether the version was: "community MySQL" vs. vendor-supplied MySQL or bundled with OS distribution, etc.

I expect that this request will be classified as an enhancement, appropriately.

Thank you.
Comment 2 Jason Booth 2020-02-19 15:17:10 MST
Hi Steve - Good to hear from you. We do not have a matrix of versions and compatibility, and I do not think we are interested in adding this since it would have to be validated and updated each release. 

I would refer back to the field notes in this case:
https://slurm.schedmd.com/SLUG18/field_notes2.pdf
https://slurm.schedmd.com/SLUG19/Field_Notes_3.pdf

> Older MySQL versions (5.5 and before) have had problems with later conversion processes.

We also expect mariadb > 10 for most sites should be sufficient.


If you experience a problem with more recent versions of MySQL/MariaDB then you should log a bug.