Sync mariadb version with prod

[fauust]

Was already deployed and tested on DEV.

The following was needed:

docker exec -it mariadb mysql_upgrade --force

[grooverdan]

MARIADB_AUTO_UPGRADE=1 and you won't need manual post steps.

https://mariadb.com/kb/en/using-healthcheck-sh/ for the healthcheck.

    depends_on:
      mariadb:
        condition: service_healthy

For dependent services (otherwise they start when mariadb starts, not when its ready).

MariaDB tuning, as command, if it gets unruly can move to a config file.

command: --slow_query_log --log_slow_verbosity=query_plan,explain,engine --log_slow_query_time=0.5 --innodb-buffer-pool-size=4G --innodb-log-file-size=4G --innodb_io_capacity=2000

[illuusio]

Where does innodb_io_capacity = 2000 come from? Is it some calculated IOPS? As reading docs it's just something in the docs and if it's that high one needs to set innodb_io_capacity_max higher as it's default is 2000 also.

[illuusio]

Shouldn't:

innodb-buffer-pool-size = 4G
innodb-log-file-size    = 4G

be

innodb_buffer_pool_size = 4G
innodb_log_file_size    = 4G

[fauust]

https://mariadb.com/kb/en/using-healthcheck-sh/ for the healthcheck.

    depends_on:
      mariadb:
        condition: service_healthy

For dependent services (otherwise they start when mariadb starts, not when its ready).

So, do you think that https:/MariaDB/buildbot/blob/dev/docker-compose/start-bbm-web.sh#L21-L25 is overkill?

[grooverdan]

Shouldn't:

innodb-buffer-pool-size = 4G
innodb-log-file-size    = 4G

be

innodb_buffer_pool_size = 4G
innodb_log_file_size    = 4G

both forms are accepted.

[grooverdan]

Where does innodb_io_capacity = 2000 come from? Is it some calculated IOPS? As reading docs it's just something in the docs and if it's that high one needs to set innodb_io_capacity_max higher as it's default is 2000 also.

Mainly that the default of 200 was for some pretty old/poor storage and I assume we have better. Measuring would be better. I can't remember the behaviour of innodb_io_capacity_max off had but it might auto-adjust.

[illuusio]

Shouldn't:

innodb-buffer-pool-size = 4G
innodb-log-file-size    = 4G

be

innodb_buffer_pool_size = 4G
innodb_log_file_size    = 4G

both forms are accepted.

Yes I know they are both accepted but this is bit like CMake use uppercase or lowercase in function names not both. All I was trying to say that it looks bit unfinished to have '_' and '-'.

[illuusio]

Where does innodb_io_capacity = 2000 come from? Is it some calculated IOPS? As reading docs it's just something in the docs and if it's that high one needs to set innodb_io_capacity_max higher as it's default is 2000 also.

Mainly that the default of 200 was for some pretty old/poor storage and I assume we have better. Measuring would be better. I can't remember the behaviour of innodb_io_capacity_max off had but it might auto-adjust.

Seems so as I made bit IOPS testing and 2000 is easily what one get. Ok Max is 2000 or twice innodb_io_capacity, whichever is higher.