GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

Percona - InnoDB - Galera on CentOS 6.3 SegFault

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

  • Percona - InnoDB - Galera on CentOS 6.3 SegFault

    We have setup Percona XtraDB with Galera (5.5.29) and InnoDb on 3 CentOS 6.3 virtual servers. We have also setup HaProxy on a 4th CentOS 6.3 Virtual server. We are running a script for testing the configuration the Creates a table, inserts a record, selects the records, updates the record, selects the records and deletes the record and a final select on the record. We run this in a loop for 1000 iterations and we run multiple instances (x5) to ensure that all the nodes of the cluster are getting hit via HaProxy. After roughly 5,000 runs of the query one node consistently fails with a signal 11 error. Here is the stack trace:

    [begin stack trace]

    19:22:56 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 at ... [ link to bug . percona . com]

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

    Thread pointer: 0xffffffffa64008a0
    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 = ffffffff9705a36c thread_stack 0x30000
    /usr/sbin/mysqld(my_print_stacktrace+0x33)[0x8416663]
    /usr/sbin/mysqld(handle_fatal_signal+0x48c)[0x82e026c]
    [0x179400]
    /usr/sbin/mysqld(_Z14wsrep_apply_cbPvPKvjx+0xad)[0x81ba27d]
    /usr/lib/libgalera_smm.so(+0x19a2af)[0x3142af]
    /usr/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM9apply_t r xEPvPNS_9TrxHandleE+0x265)[0x3194b5]
    /usr/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM11proces s _trxEPvPNS_9TrxHandleE+0x4b)[0x31a16b]
    /usr/lib/libgalera_smm.so(_ZN6galera15GcsActionSource8dispa t chEPvRK10gcs_action+0x3bf)[0x2f312f]
    /usr/lib/libgalera_smm.so(_ZN6galera15GcsActionSource7proce s sEPv+0xe0)[0x2f3c00]
    /usr/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM10async_ r ecvEPv+0x8a)[0x312d4a]
    /usr/lib/libgalera_smm.so(galera_recv+0x35)[0x3331f5]
    /usr/sbin/mysqld(_Z25wsrep_replication_processP3THD+0x50)[0x 81b95d0]
    /usr/sbin/mysqld(start_wsrep_THD+0x3c7)[0x8138d87]
    /lib/libpthread.so.0[0xd5aa09]
    /lib/libc.so.6(clone+0x5e)[0xc9800e]

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

    You may download the Percona Server operations manual by visiting
    [link to percona server]. You may find information
    in the manual which will help you identify the cause of the crash.

    [end stack trace]

    Any help is appreciated.
Working...
X