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

MGC10.0.12 Crash "_ZNK19rpl_sql_thread_info22cached_charset_compareEPc"



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.0.12-galera
    • 10.0.14-galera
    • Galera
    • - RHEL 6.5
      - MGC 10.0.12


       # my_print_defaults mysqld 

      * 10.0.12-MariaDB-wsrep-log MariaDB Server, wsrep_25.10.r4002 
      * wsrep_provider_version=25.3.5(rXXXX) 

       # ./node1.sh 
      .............ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query 
      ERROR with query 

       # ./node2.sh 

      The server on node1 crashes:

      140828 15:34:49 [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: 10.0.12-MariaDB-wsrep-log 
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467215 K  bytes of memory 
      Hope that's ok; if not, decrease some variables in the equation. 
      Thread pointer: 0x0x7f2d7ce8f008 
      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 = 0x7f2e43e56ce0 thread_stack 0x48000 
      Trying to get some variables. 
      Some pointers may be invalid and cause the dump to abort. 
      Query (0x7f2e1b631251): is an invalid pointer 
      Connection ID (thread ID): 331 
      Status: NOT_KILLED 

      I spoke with Teemu from Codership and he mentioned this is likely a bug specific to MariaDB.

      I tested this on:

      • 5.5.38: no crash
      • PXC 5.6.19: no crash

      12:22 < gryp> I have crash of MGC-10.0.12: https://gist.github.com/grypyrg/22b0512cb59b5e32a538, seems to be similar to
      knielsen's fix of https://mariadb.atlassian.net/browse/MDEV-6156 . Anybody got any ideas?
      12:27 < knielsen> gryp: The code path involved is completely different (Galera replication vs. MariaDB parallel replication).
      But it is possible that Galera has a similar bug (it also does parallel replication), might help the
      developers track it down...
      12:29 < knielsen> Interesting that Galera seems to be calling Query_log_event::do_apply_event() ... I suppose this is to
      handle DDL perhaps, which shouldn't run in parallel
      12:29 < knielsen> well, not that I know much of what Galera code does
      12:29 < gryp> indeed. it's during some DDL's. I'm still working on getting a cleaner test case.
      12:31 < gryp> I'm also running with wsrep_slave_threads=1 and the DDL is executed on the crashing node.
      12:31 < gryp> knielsen: I'll talk some more with Codership, see what they think based on your feedback. TNx
      12:33 < knielsen> gryp: there's more discussions of this bug on maria-developers@ (google should know), in case it helps
      understand the issue. Though it could be something different, hard to say
      12:33 < gryp> Yep, have found that as well. tnx. (https://www.mail-archive.com/maria-developers@lists.launchpad.net/msg06846.html)


        1. node1.sh
          0.4 kB
        2. node2.sh
          0.4 kB



            nirbhay_c Nirbhay Choubey (Inactive)
            gryp Kenny
            0 Vote for this issue
            1 Start watching this issue



              Git Integration

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