Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6197

restarting node running on cluster with wsrep_provider_options='socket.checksum=1' crashes when option removed

    XMLWordPrintable

Details

    Description

      I updated a cluster with wsrep_provider_options='socket.checksum=1' in the my.cnf of all nodes (from 5.5.29 to 5.5.37). I updated one node at a time and all when quite smoothly.

      I then removed the wsrep_provider_options='socket.checksum=1' in node 1 and restarted it.

      It crashed on startup with:

      140502  8:43:56 [Note] WSREP: Received NON-PRIMARY.
      140502  8:43:56 [Note] WSREP: Shifting SYNCED -> OPEN (TO: 9320857)
      140502  8:43:56 [Note] WSREP: Received self-leave message.
      140502  8:43:56 [Note] WSREP: Flow-control interval: [0, 0]
      140502  8:43:56 [Note] WSREP: Received SELF-LEAVE. Closing connection.
      140502  8:43:56 [Note] WSREP: Shifting OPEN -> CLOSED (TO: 9320857)
      140502  8:43:56 [Note] WSREP: RECV thread exiting 0: Success
      140502  8:43:56 [Note] WSREP: recv_thread() joined.
      140502  8:43:56 [Note] WSREP: Closing replication queue.
      140502  8:43:56 [Note] WSREP: Closing slave action queue.
      140502  8:43:56 [Note] WSREP: New cluster view: global state: 727ac931-ae1d-11e2-0800-35fac11491b4:9320857, view# -1: non-Primary, number of nodes: 1, my index: 0, protocol version 2
      140502  8:43:56 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      140502  8:43:56 [Note] WSREP: New cluster view: global state: 727ac931-ae1d-11e2-0800-35fac11491b4:9320857, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version 2
      140502  8:43:56 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      140502  8:43:56 [Note] WSREP: applier thread exiting (code:0)
      140502  8:43:56 [ERROR] 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.
       
      To report this bug, see http://kb.askmonty.org/en/reporting-bugs
       
      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.
       
      Server version: 5.5.37-MariaDB-1~precise-wsrep-log
      key_buffer_size=33554432
      read_buffer_size=2097152
      max_used_connections=4
      max_threads=202
      thread_count=1
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1277538 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f6eff012000
      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 = 0x7f6f003b2a20 thread_stack 0x48000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f6f14ee808b]
      /usr/sbin/mysqld(handle_fatal_signal+0x471)[0x7f6f14b03ef1]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f6f1334ecb0]
      /usr/sbin/mysqld(+0x5a5e9c)[0x7f6f14bbbe9c]
      /usr/sbin/mysqld(_ZN14Relay_log_infoD1Ev+0x1d2)[0x7f6f14a68e82]
      /usr/sbin/mysqld(_ZN14Relay_log_infoD0Ev+0x11)[0x7f6f14a68f21]
      /usr/sbin/mysqld(_ZN3THDD1Ev+0x18c)[0x7f6f14979a1c]
      /usr/sbin/mysqld(_ZN3THDD0Ev+0x11)[0x7f6f1497a031]
      /usr/sbin/mysqld(_Z29one_thread_per_connection_endP3THDb+0x18)[0x7f6f1491eab8]
      /usr/sbin/mysqld(start_wsrep_THD+0x5d6)[0x7f6f1491f536]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f6f13346e9a]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6f12a773fd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): is an invalid pointer
      Connection ID (thread ID): 2
      Status: KILL_CONNECTION
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off
       
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      140502 08:43:56 mysqld_safe Number of processes running now: 0
      140502 08:43:56 mysqld_safe WSREP: not restarting wsrep node automatically
      140502 08:43:56 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

      Attachments

        Activity

          People

            ramesh Ramesh Sivaraman
            danblack Daniel Black
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.