Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0.4
    • Fix Version/s: 2.1.0
    • Component/s: maxadmin, maxinfo
    • Labels:
      None
    • Sprint:
      2017-28, 2017-29

      Description

      What the replication manager do is in monitoring go routine pool the servers lists and the monitoring list

      During switchover we do

      • set master flag and remove slave flag to the elected master
      • set slave flag and remove master flag to the old master

      After a signifiant number or retried we are able to crash the maxscale.

      Nota that i do open and close the connection in failover and monitoring code

      2017-02-27 10:34:05 notice : Server changed state: server1[192.168.0.41:5055]: server_down. [Running] -> [Down]
      2017-02-27 10:34:11 notice : Server changed state: server1[192.168.0.41:5055]: slave_up. [Down] -> [Slave, Running]
      2017-02-27 10:34:31 notice : Server changed state: server1[192.168.0.41:5055]: lost_slave. [Slave, Running] -> [Running]
      2017-02-27 10:34:32 notice : Server changed state: server1[192.168.0.41:5055]: new_slave. [Running] -> [Slave, Running]
      2017-02-27 10:36:12 notice : Server changed state: server1[192.168.0.41:5055]: lost_slave. [Slave, Running] -> [Running]
      2017-02-27 10:36:17 notice : Server changed state: server1[192.168.0.41:5055]: new_slave. [Running] -> [Slave, Running]
      2017-02-27 15:44:24 notice : Server changed state: server1[192.168.0.41:5055]: new_master. [Master, Slave, Running] -> [Master, Running]
      2017-02-27 15:44:24 notice : Server changed state: server2[192.168.0.41:5056]: new_slave. [Master, Running] -> [Slave, Running]
      2017-02-27 15:44:24 notice : A Master Server is now available: 192.168.0.41:5055
      2017-02-27 15:55:11 error : Fatal: MaxScale 2.0.4 received fatal signal 11. Attempting backtrace.
      2017-02-27 15:55:11 error : Commit ID: 00f16e1fa56765678131faea59b2a819e59d49cc System name: Linux Release string: Ubuntu 16.10
      2017-02-27 15:55:11 error : /usr/bin/maxscale() [0x403ca7]
      2017-02-27 15:55:11 error : /lib/x86_64-linux-gnu/libpthread.so.0(+0x11670) [0x7f6686ec6670]
      2017-02-27 15:55:11 error : /usr/lib/x86_64-linux-gnu/maxscale/libcli.so(execute_cmd+0x2c) [0x7f667fea45d5]
      2017-02-27 15:55:11 error : /usr/lib/x86_64-linux-gnu/maxscale/libcli.so(+0x417b) [0x7f667fea417b]
      2017-02-27 15:55:11 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscaled.so(+0x1828) [0x7f667e36b828]
      2017-02-27 15:55:11 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(+0x4f338) [0x7f668738b338]
      2017-02-27 15:55:11 error : /usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(poll_waitevents+0x6c1) [0x7f668738aad9]
      2017-02-27 15:55:11 error : /usr/bin/maxscale(main+0x193b) [0x406eb0]
      2017-02-27 15:55:11 error : /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f66866ca3f1]
      2017-02-27 15:55:11 error : /usr/bin/maxscale(_start+0x29) [0x403629]

        Attachments

          Activity

            People

            • Assignee:
              esa.korhonen Esa Korhonen
              Reporter:
              stephane@skysql.com VAROQUI Stephane
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: