jperkin: did you had the time to look into the mariadb missing innodb issue? Just wanted to know before the next update round :-)

Is it really missing or did people just hit the same as me I wonder

→ GitHub commit : (committed)

There is a workaround in the my.cnf too. They changed a default value in a minor release which makes the innodb engine try to mmap a very large amount of memory, assuming Linux semantics.

andyf: I got the error "Unknown/unsupported storage engine: innodb". But innodb is the main storage engine.

If you got the same as me - paste.omnios.org/?5d43a09365c6aecb#…x3C1YDJU5xnfchdPjRMRs8r1bwGTnUhS5CR - then it's the new default innodb_buffer_pool_size_max

jira.mariadb.org/browse/MDEV-38671 - I already dropped a note in there.

Thx a lot for sharing! I will take a look into it. And maybe jperkin can include the patch in the mean time?

ah thanks, no sorry I didn't get a chance to look yet (August is very flaky for me, and there are issues with the NetBSD repo conversion at the moment) - I'll pull in andy's patch

andyf: Looked into the log again and yes it is the exact same error output as yours. So I will try to fix it by setting innodb_buffer_pool_size_max to a lower value. Maybe I do not understand it right, but it should work if I set it to 80% of the swap (currently 32G)?

I just set it to 2G, and innodb_buffer_pool_size to 1G - but this was on a smallish server. Maybe just look at what the current size is with `show global variables like...` and set both to that value. It just means you can't dynamically grow it with the server running.

I really wish projects would not make changes like this in minor releases.

andyf: yes so true! But this is more and more the case.