GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

5.5.25a server crash when replication starts

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • 5.5.25a server crash when replication starts

    In the last 1.5 weeks, we've started running into a very strange issue where we have 5 different slaves that will suddenly completely crash in the middle of replication. Once that happens, we can never successfully get replication going again without completely re-initializing the slave. This happens at minimum every 24 hours.

    I've already verified that these slaves are not overloaded in the slightest. There's plenty of free memory and CPU is no where close to being fully utilized.

    Once the crash happens, MySQL will never be able to start again until it is started with "skip-slave-start". Once the command for "start slave" is issued, the server immediately crashes. I have looked in the relay logs on the slave and in the binary logs on the master and I cannot see anything wrong at all with the queries being sent to the slave. Here are the crash details from the logs. The messages appear immediately after the slave connects to the master to start replication.

    08:14:48 UTC - mysqld got signal 11 ;
    This could be because you hit a bug. It is also possible that this binary
    or 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 help
    diagnose 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 any
    bugs

    key_buffer_size=8388608
    read_buffer_size=131072
    max_used_connections=5
    max_threads=200
    thread_count=4
    connection_count=4
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 445843 K bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x24622950
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    stack_bottom = 4bef40e8 thread_stack 0x40000
    /opt/apps/ms/mysql/sbin/mysqld(my_print_stacktrace+0x2e)[0x7 b346e]
    /opt/apps/ms/mysql/sbin/mysqld(handle_fatal_signal+0x3e2)[0x 688dd2]
    /lib64/libpthread.so.0[0x39cc00eb10]
    /lib64/libc.so.6(strcmp+0x2)[0x39cb879232]
    /opt/apps/ms/mysql/sbin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_ LIST+0x4d)[0x5f153d]
    /opt/apps/ms/mysql/sbin/mysqld(_Z10open_tableP3THDP10TABLE_L ISTP11st_mem_rootP18Open_table_context+0x130)[0x53fe60]
    /opt/apps/ms/mysql/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE _LISTPjjP19Prelocking_strategy+0x2c1)[0x542841]
    /opt/apps/ms/mysql/sbin/mysqld(_Z20open_and_lock_tablesP3THD P10TABLE_LISTbjP19Prelocking_strategy+0x51)[0x543371]
    /opt/apps/ms/mysql/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE _LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicates b+0xd8)[0x 567638]
    /opt/apps/ms/mysql/sbin/mysqld(_Z21mysql_execute_commandP3TH D+0x226d)[0x57831d]
    /opt/apps/ms/mysql/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Par ser_state+0x3db)[0x57c6fb]
    /opt/apps/ms/mysql/sbin/mysqld(_ZN15Query_log_event14do_appl y_eventEPK14Relay_log_infoPKcj+0xe45)[0x738bf5]
    /opt/apps/ms/mysql/sbin/mysqld(_Z26apply_event_and_update_po sP9Log_eventP3THDP14Relay_log_info+0x14d)[0x516ccd]
    /opt/apps/ms/mysql/sbin/mysqld[0x51fad5]
    /opt/apps/ms/mysql/sbin/mysqld(handle_slave_sql+0xc6a)[0x520 e0a]
    /lib64/libpthread.so.0[0x39cc00673d]
    /lib64/libc.so.6(clone+0x6d)[0x39cb8d3d1d]

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (2462fdb0): ▒▒▒
    Connection ID (thread ID): 77
    Status: NOT_KILLED

  • #2
    Hi,

    This crash is caused by the following bug:

    bugs.launchpad.net/percona-server/+bug/1053342

    That bug is solved in the latest Percona Server 5.5.28-29.1

    There is a workaround, disable the replication filters on the slave. For example:

    replicate-wild-ignore-table
    replicate-ignore-table
    replicate-do-table

    and so on. Comment those variables on my.cnf and start the server again.

    Anyway, an upgrade is recommended.

    Regards.

    Comment


    • #3
      Thanks a ton for giving me that info! I had done considerable amounts of searching, but had not found that bug. I'll be doing an upgrade today

      Comment

      Working...
      X