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

Server status unknown after reloading config

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 1.2.1
    • 1.4.0
    • maxadmin
    • None
    • EC2, Ubuntu 14.04

    Description

      Assume MaxScale installation with 2 MySQL replication nodes. Third one is added to the configuration file. MaxScale is reloaded. As a result I'm seeing:

      MaxScale> list servers
      Servers.
      --------------------------------------------------------------------
      Server | Address | Port | Connections | Status
      --------------------------------------------------------------------
      svr_172304179 | 172.30.4.179 | 3306 | 0 | Running
      svr_172304112 | 172.30.4.112 | 3306 | 0 | Slave, Running
      svr_172304194 | 172.30.4.194 | 3306 | 0 | Master, Running
      --------------------------------------------------------------------

      I see no way to make .179 detectable as a slave to the master by MaxScale. Both init scripts and reload config trigger reload but server's status doesn't change:

      root@ip-172-30-4-52:~# echo "reload config" |maxadmin -pmariadb ; date
      MaxScale> Reloading configuration from file.
      MaxScale> Wed Jan 27 13:25:39 UTC 2016

      2016-01-27 13:25:39 Update server protocol for server 172.30.4.179 to protocol MySQLBackend.
      2016-01-27 13:25:39 Update server protocol for server 172.30.4.194 to protocol MySQLBackend.
      2016-01-27 13:25:39 Update server protocol for server 172.30.4.112 to protocol MySQLBackend.
      2016-01-27 13:25:39 Update router for service RR to readconnroute.
      2016-01-27 13:25:39 Update router for service RW to readwritesplit.

      root@ip-172-30-4-52:~# echo "list servers" |maxadmin -pmariadb ; date
      MaxScale> Servers.
      --------------------------------------------------------------------
      Server | Address | Port | Connections | Status
      --------------------------------------------------------------------
      svr_172304179 | 172.30.4.179 | 3306 | 0 | Running
      svr_172304112 | 172.30.4.112 | 3306 | 0 | Slave, Running
      svr_172304194 | 172.30.4.194 | 3306 | 0 | Master, Running
      --------------------------------------------------------------------
      MaxScale> Wed Jan 27 13:26:46 UTC 2016

      MaxScale restart is required to properly detect the state of the node.

      root@ip-172-30-4-52:~# service maxscale restart ; echo "list servers" |maxadmin -pmariadb ; date

      • Stopping MaxScale [ OK ]
      • Starting MaxScale * maxscale is running
        [ OK ]
        MaxScale> Servers.
        --------------------------------------------------------------------
        Server | Address | Port | Connections | Status
        --------------------------------------------------------------------
        svr_172304112 | 172.30.4.112 | 3306 | 0 | Slave, Running
        svr_172304194 | 172.30.4.194 | 3306 | 0 | Master, Running
        svr_172304179 | 172.30.4.179 | 3306 | 0 | Slave, Running
        --------------------------------------------------------------------
        MaxScale> Wed Jan 27 13:27:27 UTC 2016

      If this behavior is expected, please treat this report as a feature request. There should be a way to dynamically add new nodes while keeping MaxScale running.

      Attachments

        Activity

          People

            johan.wikman Johan Wikman
            kksiazek Krzysztof Książek
            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.