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

Crash with transaction_replay=true

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 2.3.6
    • 2.3.8
    • readwritesplit
    • None
    • MXS-SPRINT-84

    Description

      How it happened:

      1. Set a server into maintenance mode with maxctrl set server maintenanance. -> works
      2. Stopped service on the DB Server which was the Master from the Maxscale view, so it goes down in Maxscale. -> crash
      3. Tryed 2. again -> works

      Crash backtrace after running through c++filt

      2019-06-04 08:59:58   alert  :   /usr/bin/maxscale(maxbase::dump_stacktrace(std::function<void (char const*, char const*)>)+0x2b) [0x40cbab]: /home/vagrant/MaxScale/maxutils/maxbase/src/stacktrace.cc:130
      2019-06-04 08:59:58   alert  :   /usr/bin/maxscale(maxbase::dump_stacktrace(void (*)(char const*, char const*))+0x4e) [0x40cf0e]: /usr/include/c++/4.8.2/functional:2029
      2019-06-04 08:59:58   alert  :   /usr/bin/maxscale() [0x4095b9]: ??:0
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libreadwritesplit.so(RWSplitSession::routeQuery(gwbuf*)+0x3b) [0x7f3261e1ffeb]: /home/vagrant/MaxScale/server/modules/routing/readwritesplit/rwsplitsession.cc:143
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libreadwritesplit.so(maxscale::Router<RWSplit, RWSplitSession>::routeQuery(mxs_router*, mxs_router_session*, gwbuf*)+0x1e) [0x7f3261e1bade]: /home/vagrant/MaxScale/include/maxscale/router.hh:181
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xcc49f) [0x7f326929849f]: /home/vagrant/MaxScale/server/core/session.cc:1139
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(maxbase::Worker::tick()+0xe6) [0x7f32692a5946]: /home/vagrant/MaxScale/maxutils/maxbase/include/maxbase/worker.hh:777
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(maxbase::WorkerTimer::handle(maxbase::Worker*, unsigned int)+0x36) [0x7f32692a40e6]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:256
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(maxbase::Worker::poll_waitevents()+0x1b5) [0x7f32692a4ae5]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:844
      2019-06-04 08:59:58   alert  :   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(maxbase::Worker::run(maxbase::Semaphore*)+0x51) [0x7f32692a4ce1]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:545
      2019-06-04 08:59:58   alert  :   /usr/bin/maxscale(main+0x2019) [0x4087f9]: /home/vagrant/MaxScale/server/core/gateway.cc:2259
      2019-06-04 08:59:58   alert  :   /usr/bin/maxscale() [0x409022]: ??:0
      

      Attachments

        Activity

          People

            marko.rajala Marko Rajala (Inactive)
            hholzgra Hartmut Holzgraefe
            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.