Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4005

Crash on server failure with causal_reads=local

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.2.2
    • Fix Version/s: 6.2.3
    • Component/s: readwritesplit
    • Labels:
      None

      Description

      When testing a custom pre-build of the upcoming MaxScale 6.2.2 (with proposed fix for MXS-4000 and some extra logging code added), a crash in the readwritesplit happened (just once so far):

      2022-02-16 15:45:35   alert  : (48) (Appdata1RW-Service); MaxScale 6.2.2 received fatal signal 11. Commit ID: 2374370f645d721e99237d4d9bc61bb691757ad6 System name: Linux Release string: undefined
      2022-02-16 15:45:35   alert  : (48) (Appdata1RW-Service); Statement currently being classified: none/unknown
      2022-02-16 15:45:35   alert  : (48) (Appdata1RW-Service); DCB: 0x7efe7803b370 Session: 48 Service: Appdata1RW-Service
      2022-02-16 15:45:35   notice : (48) (Appdata1RW-Service); For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] section.
        /usr/lib64/maxscale/libreadwritesplit.so(RWSplitSession::finish_causal_read()+0x59) [0x7efe7c20b849]
        /usr/lib64/maxscale/libreadwritesplit.so(RWSplitSession::clientReply(GWBUF*, std::vector<maxscale::Endpoint*, std::allocator<maxscale::Endpoint*> > const&, maxscale::Reply const&)+0x2fc) [0x7efe7c20030c]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(ServiceEndpoint::clientReply(GWBUF*, std::vector<maxscale::Endpoint*, std::allocator<maxscale::Endpoint*> >&, maxscale::Reply const&)+0x99) [0x7efe8574bb19]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(ServerEndpoint::clientReply(GWBUF*, std::vector<maxscale::Endpoint*, std::allocator<maxscale::Endpoint*> >&, maxscale::Reply const&)+0xfa) [0x7efe8573d4ba]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(MariaDBBackendConnection::normal_read()+0x19f) [0x7efe8577d30f]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(DCB::process_events(unsigned int)+0xc4) [0x7efe856c7314]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(DCB::event_handler(DCB*, unsigned int)+0x21) [0x7efe856c7411]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(maxbase::Worker::poll_waitevents()+0x212) [0x7efe857bd9d2]
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(maxbase::Worker::run(maxbase::Semaphore*)+0x4f) [0x7efe857bdb8f]
        /usr/lib64/libstdc++.so.6(+0xdb3b4) [0x7efe845e63b4]
        /lib64/libpthread.so.0(+0xa6ea) [0x7efe833396ea]
        /lib64/libc.so.6(clone+0x3f) [0x7efe826e0a8f]
      alert  : Writing core dump.
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.