Not the answer you need?
Register and ask your own question!

Mysql 5.1 to percona 5.5

mwainmwain EntrantCurrent User Role Participant
Hi,

We are looking to upgrade our mysql 5.1.23 to an up to date version. The problem is we need to do it with as little downtime as possible.

We have one idea using replication but not sure is this is feasible.
Is it possible to set our server running 5.1 replicate to a server running percona 5.5. We can then switch the new server to the master while upgrading?

One gotcha is the mysql 5.1 is running on Solaris, while percona 5.5 will run a Linux box. Will this matter?

Any advise is welcome.

Thanks

Comments

  • niljoshiniljoshi MySQL Sage Inactive User Role Leader
    Hi,

    >Is it possible to set our server running 5.1 replicate to a server running percona 5.5. We can then switch the new server to the master while upgrading?

    Logically, you can replicate db from older version (5.1) to newer version(5.5) and Percona Server is based on native mysql binaries so it is possible but there are lots of changes in mysql 5.5 (configuration parameters, default storage engine etc). Many people are facing performance issues after migrating db from 5.1 to 5.5 due to incorrect parameter configuration. So you must test on stage servers before implement in production. You can get some more information here, http://www.percona.com/doc/percona-server/5.5/upgrading_guid e_51_55.html

    >One gotcha is the mysql 5.1 is running on Solaris, while percona 5.5 will run a Linux box. Will this matter?

    As per the mysql documentation, replication should work across the platform/OS but it might create some issue for Blob columns I'm not sure. Very few people are using it so again I would suggest that you should test before implement. I'll try to find some proof/statistics if I can and will let you know.
  • mwainmwain Entrant Current User Role Participant
    Well we have been testing the replication from 5.1 to 5.5 for a while the data get across intact but the slave (5.5) crashes randomly.
    We cant figure out why it does this and was hoping someone may have had a similar issue.

    The mysql error log from the crash below, it has happened before this is the latest one.

    WSREP: skipping FK key appendWSREP: skipping FK key appendWSREP: skipping FK key appendWSREP: skipping FK key append12:21:18 UTC - mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware.We will try our best to scrape up some info that will hopefully helpdiagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.Please help us make Percona Server better by reporting anybugs at urlherekey_buffer_size=33554432read_buffer_size=131072max_used_connections=3max_threads=500thread_count=1connection_count=1It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1127084 K bytes of memoryHope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x7f2984000990Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...stack_bottom = 7f3530172e78 thread_stack 0x40000/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c5fb5]/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6a00f4]/lib64/libpthread.so.0(+0xf500)[0x7f35321f4500]/usr/sbin/mysqld(_ZN11Query_arena10free_itemsEv+0x2d)[0x5661ed]/usr/sbin/mysqld(_ZN3THD19cleanup_after_queryEv+0x97)[0x5692e7]/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x2c8)[0x597dc8]/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xd58)[0x7474b8]/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x5317b5]/usr/sbin/mysqld[0x535af7]/usr/sbin/mysqld(handle_slave_sql+0xa45)[0x537025]/lib64/libpthread.so.0(+0x7851)[0x7f35321ec851]/lib64/libc.so.6(clone+0x6d)[0x7f353147211d]Trying to get some variables.Some pointers may be invalid and cause the dump to abort.Query (7f29840083a0): is an invalid pointerConnection ID (thread ID): 6Status: NOT_KILLEDYou may download the Percona Server operations manual by visitingurlhere. You may find informationin the manual which will help you identify the cause of the crash.121219 12:21:18 mysqld_safe Number of processes running now: 0121219 12:21:18 mysqld_safe mysqld restarted121219 12:21:18 [Note] Flashcache bypass: disabled121219 12:21:18 [Note] Flashcache setup error is : open flash device failed121219 12:21:18 [Note] Plugin 'FEDERATED' is disabled.121219 12:21:18 InnoDB: The InnoDB memory heap is disabled121219 12:21:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins121219 12:21:18 InnoDB: Compressed tables use zlib 1.2.3121219 12:21:18 InnoDB: Using Linux native AIO121219 12:21:18 InnoDB: Initializing buffer pool, size = 44.0G121219 12:21:21 InnoDB: Completed initialization of buffer pool121219 12:21:21 InnoDB: highest supported file format is Barracuda.InnoDB: Log scan progressed past the checkpoint lsn 612232880549121219 12:21:21 InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files...InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer...InnoDB: Doing recovery: scanned up to log sequence number 612233195105121219 12:21:22 InnoDB: Starting an apply batch of log records to the database...InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completedInnoDB: In a MySQL replication slave the last master binlog fileInnoDB: position 0 17532360, file name mysql-bin.000047InnoDB: and relay log fileInnoDB: position 0 17532506, file name ./slave-relay-bin.000077InnoDB: Last MySQL binlog file position 0 565234080, file name /var/lib/mysql/log/mysql-bin.000190121219 12:21:26 InnoDB: Waiting for the background threads to start121219 12:21:27 Percona XtraDB (urlhere) 1.1.8-rel28.1 started; log sequence number 612233195105121219 12:21:27 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306121219 12:21:27 [Note] - '0.0.0.0' resolves to '0.0.0.0';121219 12:21:27 [Note] Server socket created on IP: '0.0.0.0'.121219 12:21:27 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=slave-relay-bin' to avoid this problem.121219 12:21:27 [Note] Event Scheduler: Loaded 0 events121219 12:21:27 [Note] WSREP: Read nil XID from storage engines, skipping position init121219 12:21:27 [Note] WSREP: wsrep_load(): loading provider library 'none'sh: /sbin/ifconfig: Permission denied121219 12:21:27 [ERROR] WSREP: Failed to read output of: '/sbin/ifconfig | grep -m1 -1 -E '^[a-z]?eth[0-9]' | tail -n 1 | awk '{ print $2 }' | awk -F : '{ print $2 }''121219 12:21:27 [Warning] WSREP: Failed to autoguess base node address121219 12:21:27 [Note] /usr/sbin/mysqld: ready for connections.Version: '5.5.27-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Percona XtraDB Cluster (GPL), wsrep_23.6.r356121221 17:32:34 [Note] WSREP: ready state reached</pre>


    We disabled the slave auto start. When we try and restart the slave. it crashes again with the same output as above.
    Does any one know why this is happening?

    Many Thanks
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.