Trying to perform in-place upgrade of MySQL 5.5 replica to 5.6.14.
Previous versions…
[root@ip-10-167-34-15 logs]# rpm -qa | grep Percona-Server
Percona-Server-client-55-5.5.16-rel22.0.189.rhel5
Percona-Server-shared-compat-5.5.27-rel28.1.296.rhel5
Percona-Server-shared-55-5.5.16-rel22.0.189.rhel5
Percona-Server-server-55-5.5.16-rel22.0.189.rhel5
Percona-Server-devel-55-5.5.16-rel22.0.189.rhel5
Following the directions from http://www.percona.com/doc/percona-s…ide_55_56.html.
Using the RPM-based distributions.
my.cnf:
[mysql]
no-auto-rehash
[client]
port = 3306
socket = /mysqldb/data/mysql.sock
[mysqld_safe]
socket = /mysqldb/data/mysql.sock
nice = 0
[mysqld]
server-id = 102
port = 3306
datadir = /mysqldb/data
pid-file = /mysqldb/data/mysql.pid
socket = /mysqldb/data/mysql.sock
tmpdir = /data/tmp
skip_name_resolve = 1
interactive_timeout = 100
back_log = 100
transaction_isolation = read-committed
key_buffer_size = 512M
bulk_insert_buffer_size = 128M
max_sort_length = 64
ft_min_word_len = 2
sort_buffer_size = 2M
join_buffer_size = 8M
max_connections = 500
max_connect_errors = 40000
thread_cache_size = 200
### table_cache = 4000 --- doesn't like this
max_allowed_packet = 32M
open_files_limit = 32000
tmp_table_size = 512M
max_heap_table_size = 512M
query_cache_size = 0
query_cache_type = 0
query_cache_limit = 4M
innodb_log_group_home_dir = /mysqldb/data
innodb_data_home_dir = /mysqldb/data
innodb_data_file_path = ibdata1:10M:autoextend
innodb_autoextend_increment = 8
innodb_buffer_pool_size = 20G
innodb_buffer_pool_instances = 4
### innodb_additional_mem_pool_size = 32M --- deprecated option
innodb_flush_method = O_DIRECT
innodb_thread_concurrency = 16
innodb_thread_sleep_delay = 0
innodb_open_files = 2000
innodb_file_per_table = 1
innodb_flush_log_at_trx_commit = 0
innodb_log_buffer_size = 16M
innodb_log_file_size = 512M
innodb_log_files_in_group = 3
innodb_locks_unsafe_for_binlog = 0
innodb_adaptive_hash_index = 1
### innodb_read_ahead = linear --- replaced by MySQL Read-Ahead Algorithm implementation, innodb_random_read_ahead
innodb_max_dirty_pages_pct = 80
innodb_io_capacity = 200
innodb_read_io_threads = 2
innodb_write_io_threads = 2
innodb_fast_shutdown = 1
### innodb_stats_update_need_lock = 0 --- variable has not been ported to Percona Server 5.6
### innodb_checksum = 1 --- ambiguous option
### innodb_fast_checksum = 1 --- replaced by innodb_checksum_algorithm
### innodb_buffer_pool_restore_at_startup = 600 --- replaced by innodb_buffer_pool_load_at_startup
#log-bin = /mysqldb/binlogs/mysql-bin.log
relay-log = /mysqldb/binlogs/mysql-relay.log
log-slave-updates = 0
max_binlog_size = 1G
binlog_format = MIXED
expire_logs_days = 7
binlog_cache_size = 1M
max_binlog_cache_size = 256M
log_bin_trust_function_creators = 1
slow-query-log-file = /mysqldb/logs/mysql-slow.log
slow-query-log = ON
### log_slow_slave_statements = ON --- the upstream variable has the same functionality
# remove this when promoting this to master
read_only = 1
log-error = /mysqldb/logs/error.log
log_warnings = 2
long_query_time = 10
slow_query_log = 1
#replicate-wild-ignore-table=pixel_stats.%
#replicate-wild-ignore-table=bi.shipment_carrier_fact
#replicate-wild-ignore-table=bi.shipment_fedex_event_history_fact
#replicate-wild-ignore-table=bi.shipment_fedex_fact
#replicate-wild-ignore-table=bi.shipment_ups_fact
When running command after installing new binaries,
/usr/sbin/mysqld --skip-grant-tables --user=mysql &
Getting these errors from the log.
2013-11-13 07:38:33 25029 [ERROR] InnoDB: checksum mismatch in data file /mysqldb/data/ibdata1 2013-11-13 07:38:33 25029 [ERROR] 2013-11-13 07:38:33 25029 [ERROR] InnoDB: checksum mismatch in data file /mysqldb/data/ibdata1
2013-11-13 07:38:33 25029 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2013-11-13 07:38:33 25029 [ERROR] Plugin 'InnoDB' init function returned error.
2013-11-13 07:38:33 25029 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2013-11-13 07:38:33 25029 [ERROR] Unknown/unsupported storage engine: InnoDB
2013-11-13 07:38:33 25029 [ERROR] Aborting