[MXS-1593] Servers appearing as Stale out of list servers for a fresh setup Created: 2018-01-03  Updated: 2018-01-04  Resolved: 2018-01-04

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.2.1
Fix Version/s: 2.2.1

Type: Bug Priority: Major
Reporter: Wagner Bianchi (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 7.2



 Description   

Folks,

I raised a new environment with pretty basic configs, comprising of one master and one slave, and a dedicated VM for Maxscale. With dyamic commands I created the monitor, listener and created and added the servers. As it's mandatory for 2.2, I started Maxscale with --user=root.

What I think is strange about this setup is that the servers out of list servers have the Stale status all the time, no matter what I do, it's there:

[root@maxscale maxscale.cnf.d]# maxadmin list servers
Servers.
-------------------+-----------------+-------+-------------+--------------------
Server             | Address         | Port  | Connections | Status
-------------------+-----------------+-------+-------------+--------------------
prod_mariadb01     | 192.168.50.11   |  3306 |           0 | Master, Stale Status, Running
prod_mariadb02     | 192.168.50.12   |  3306 |           0 | Slave, Stale Status, Running
-------------------+-----------------+-------+-------------+--------------------

Is it this way? Thanks!



 Comments   
Comment by markus makela [ 2018-01-04 ]

The output of the Stale status is not informative to the end user so displaying it only serves to confuse the end user. Fixed by simply removing the stale status printing.

Generated at Thu Feb 08 04:07:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.