I get this warning in mysql
I have been through few topics in google and according to some suggestion I increased the max_allowed_packet from 128 to 512 to 1024 still the same behaviour.
I am using Drupal 7, and yes there are lots of blob data types, but 1024 Mb of max_allowed_packet should be enough in my opinion.
Any other workaround how to overcome this warning ?
My mysql config looks like this:
[client] port = 3306 socket = /tmp/mysql.sock default-character-set = utf8 [mysqld] port = 3306 socket = /tmp/mysql.sock skip-external-locking key_buffer_size = 16K max_allowed_packet = 1024M table_open_cache = 128 sort_buffer_size = 64K read_buffer_size = 256K read_rnd_buffer_size = 256K net_buffer_length = 2K thread_stack = 192K # Query cache disabled thread_cache_size = 8 myisam-recover = BACKUP max_connections = 100 thread_concurrency = 10 tmp_table_size = 128M max_heap_table_size = 128M log_error = /var/log/mysql/mysql-error.log log_slow_queries = /var/log/mysql/mysql-slow.log long_query_time = 2 log_warnings = 2 server-id = 1 binlog-format = row replicate-same-server-id = 0 auto-increment-increment = 2 auto-increment-offset = 1 log_bin = mysql-bin log-slave-updates relay-log=mysqld-relay-bin expire_logs_days = 10 max_binlog_size = 100M innodb_data_home_dir = /var/db/mysql innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /var/db/mysql innodb_buffer_pool_size = 8G character-set-server = utf8 #innodb_additional_mem_pool_size = 2M innodb_log_file_size = 2047M innodb_log_buffer_size = 32M innodb_flush_log_at_trx_commit = 2 innodb_thread_concurrency = 8 innodb_lock_wait_timeout = 50 innodb_flush_method = O_DIRECT [mysqldump] quick quote-names max_allowed_packet = 16M default-character-set = utf8 [mysql] default-character-set = utf8 [myisamchk] key_buffer_size = 32M sort_buffer_size = 32M [mysqlhotcopy] interactive-timeout [mysqld_save] syslog
My application uses only InnoDB, but there are few database like mysql, which came with the standard mysql installations are only the ones which uses MyISAM engine type, I guess that should not be my concern though.
As you can see I have replication too, the warning is the same one in replicated server too, whose config is identical as this.