cannot start database if host system runs out of memory

[michielbdejong]

also, it seems that my Vultr servers are born swapless.

should definitely do memory checking and shut down containers based on that.

[michielbdejong]

should also set a memory limit on each container, otherwise mysql instances will just expand to fill up the RAM

[Ramblurr]

Yea I've had this same issue. Setting a ram limit per mysql container is a good idea.

I've also been using this minimal memory config for 5.6 (from Configuring MySQL to use minimal memory). This isn't ideal in most cases, however for very lightweight apps with a small amount of traffic it might be ok.

[mysqld]
bind-address=0.0.0.0
# http://www.percona.com/blog/2008/05/31/dns-achilles-heel-mysql-installation/
skip_name_resolve
#server-id
#log-bin
max_allowed_packet = 64M
wait_timeout = 6000
#innodb_buffer_pool_size = 64M
#innodb_log_buffer_size = 512K
innodb_buffer_pool_size=10M
innodb_log_buffer_size=256K
query_cache_size=0
max_connections=10
key_buffer_size=8
thread_cache_size=0
host_cache_size=0
innodb_ft_cache_size=1600000
innodb_ft_total_cache_size=32000000

# per thread or per operation settings
thread_stack=131072
sort_buffer_size=32K
read_buffer_size=8200
read_rnd_buffer_size=8200
max_heap_table_size=16K
tmp_table_size=1K
bulk_insert_buffer_size=0
join_buffer_size=128
net_buffer_length=1K
innodb_sort_buffer_size=64K

#settings that relate to the binary log (if enabled)
binlog_cache_size=4K
binlog_stmt_cache_size=4K

[mysqldump]
max_allowed_packet = 64M

[michielbdejong]

Ah, yes! That's also a good idea