[slurm-users] Extreme long db upgrade 16.05.6 -> 17.11.3
lech.nieroda at uni-koeln.de
Tue Apr 2 12:56:00 UTC 2019
That’s probably it.
Sub-queries are known for potential performance issues, so one wonders why the devs didn’t extract it accordingly and made the code more robust or at least compatible with RHEL/CentOS 6 rather than including that remark in the release notes.
> Am 02.04.2019 um 07:20 schrieb Chris Samuel <chris at csamuel.org>:
> On Monday, 1 April 2019 7:55:09 AM PDT Lech Nieroda wrote:
>> Further analysis of the query has shown that the mysql optimizer has choosen
>> the wrong execution plan. This may depend on the mysql version, ours was
> I suspect this is the issue documented in the release notes for 17.11:
> NOTE FOR THOSE UPGRADING SLURMDBD: The database conversion process from
> SlurmDBD 16.05 or 17.02 may not work properly with MySQL 5.1 (as was the
> default version for RHEL 6). Upgrading to a newer version of MariaDB or
> MySQL is strongly encouraged to prevent this problem.
> Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
More information about the slurm-users