Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-618

innodb query crash only happens on columnstore server

    XMLWordPrintable

    Details

    • Sprint:
      2017-5, 2017-6, 2017-7, 2017-8, 2017-9

      Description

      Please be advised the queries that they are failing on are on table running on innodb engine. The Mariadb server runs fine when Columnstore is not there in the Mariadb server, but when Columnstore is added, it is failing on innodb engine "Outer join" queries.

      170308 23:36:45 [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 https://mariadb.com/kb/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.1.21-MariaDB
      key_buffer_size=1098907648
      read_buffer_size=2097152
      max_used_connections=104
      max_threads=602
      thread_count=104
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3551255 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f0ce1a1faa8
      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 = 0x7f0c71212ed8 thread_stack 0x80000
      /usr/local/mariadb/columnstore/mysql//bin/mysqld(my_print_stacktrace+0x29)[0x7f0cde5a7229]
      /usr/local/mariadb/columnstore/mysql//bin/mysqld(handle_fatal_signal+0x2fd)[0x7f0cde1893ed]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0cdd7ec890]
      /usr/local/mariadb/columnstore/mysql//bin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x22d)[0x7f0cde048a7d]
      /usr/local/mariadb/columnstore/mysql//bin/mysqld(ZN18Prepared_statement12execute_loopEP6StringbPhS2+0xa4)[0x7f0cde048f24]
      /usr/local/mariadb/columnstore/mysql//bin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0xc9)[0x7f0cde049119]
      mysys/stacktrace.c:268(my_print_stacktrace)[0x7f0cde039d3a]
      sql/table.h:1375(TABLE::isInfiniDB())[0x7f0cde03b5f7]
      sql/sql_connect.cc:1349(do_handle_one_connection(THD*))[0x7f0cde0f3b04]
      sql/sql_connect.cc:1263(handle_one_connection)[0x7f0cde0f3b97]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f0cdd7e5064]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0cdc04562d]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f0c40031c18): is an invalid pointer
      Connection ID (thread ID): 6
      Status: NOT_KILLED

      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=on,exists_to_in=on,orderby_uses_equalities=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.

        Attachments

          Activity

            People

            Assignee:
            dleeyh Daniel Lee
            Reporter:
            dthompson David Thompson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

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