[MCOL-3623] Changing hostname on UM1 sets the cluster in DEGRADED mode Created: 2019-11-22  Updated: 2021-02-19  Resolved: 2021-02-19

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: 1.2.5
Fix Version/s: N/A

Type: New Feature Priority: Minor
Reporter: Rick Pizzi Assignee: Todd Stoffel (Inactive)
Resolution: Won't Do Votes: 0
Labels: None


 Description   

We found out that setting the hostname on a running UM1 node causes the cluster to become DEGRADED and the mysqld process to go in MAN_OFFLINE.
Despite the status reported, however, the cluster works just fine.

How to reproduce:

mcsadmin> getsysteminfo
getsysteminfo   Fri Nov 22 14:30:39 2019
System columnstore-1
System and Module statuses
Component     Status                       Last Status Change
------------  --------------------------   ------------------------
System        ACTIVE                       Fri Nov 22 14:29:46 2019
Module pm1    ACTIVE                       Fri Nov 22 14:29:43 2019
MariaDB ColumnStore Process statuses
Process             Module    Status            Last Status Change        Process ID
------------------  ------    ---------------   ------------------------  ----------
ProcessMonitor      pm1       ACTIVE            Fri Nov 22 14:28:21 2019       21862
ProcessManager      pm1       ACTIVE            Fri Nov 22 14:28:27 2019       21956
DBRMControllerNode  pm1       ACTIVE            Fri Nov 22 14:29:22 2019       23529
ServerMonitor       pm1       ACTIVE            Fri Nov 22 14:29:24 2019       23590
DBRMWorkerNode      pm1       ACTIVE            Fri Nov 22 14:29:24 2019       23611
PrimProc            pm1       ACTIVE            Fri Nov 22 14:29:28 2019       23682
ExeMgr              pm1       ACTIVE            Fri Nov 22 14:29:32 2019       23723
WriteEngineServer   pm1       ACTIVE            Fri Nov 22 14:29:36 2019       23814
DDLProc             pm1       ACTIVE            Fri Nov 22 14:29:40 2019       23884
DMLProc             pm1       ACTIVE            Fri Nov 22 14:29:44 2019       23952
mysqld              pm1       ACTIVE            Fri Nov 22 14:29:22 2019       23419
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0
mcsadmin> exit
exit   Fri Nov 22 14:30:55 2019
Exiting the MariaDB ColumnStore Admin Console
[root@columnstore ~]# hostnamectl set-hostname testbox
[root@columnstore ~]# hostname
testbox
[root@columnstore ~]# mcsadmin
MariaDB ColumnStore Admin Console
   enter 'help' for list of commands
   enter 'exit' to exit the MariaDB ColumnStore Command Console
   use up/down arrows to recall commands
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0
Critical Active Alarms:
mcsadmin> getsysteminfo
getsysteminfo   Fri Nov 22 14:31:31 2019
System columnstore-1
System and Module statuses
Component     Status                       Last Status Change
------------  --------------------------   ------------------------
System        ACTIVE                       Fri Nov 22 14:29:46 2019
Module pm1    DEGRADED                     Fri Nov 22 14:31:18 2019
MariaDB ColumnStore Process statuses
Process             Module    Status            Last Status Change        Process ID
------------------  ------    ---------------   ------------------------  ----------
ProcessMonitor      pm1       ACTIVE            Fri Nov 22 14:28:21 2019       21862
ProcessManager      pm1       ACTIVE            Fri Nov 22 14:28:27 2019       21956
DBRMControllerNode  pm1       ACTIVE            Fri Nov 22 14:29:22 2019       23529
ServerMonitor       pm1       ACTIVE            Fri Nov 22 14:29:24 2019       23590
DBRMWorkerNode      pm1       ACTIVE            Fri Nov 22 14:29:24 2019       23611
PrimProc            pm1       ACTIVE            Fri Nov 22 14:29:28 2019       23682
ExeMgr              pm1       ACTIVE            Fri Nov 22 14:29:32 2019       23723
WriteEngineServer   pm1       ACTIVE            Fri Nov 22 14:29:36 2019       23814
DDLProc             pm1       ACTIVE            Fri Nov 22 14:29:40 2019       23884
DMLProc             pm1       ACTIVE            Fri Nov 22 14:29:44 2019       23952
mysqld              pm1       MAN_OFFLINE       Fri Nov 22 14:31:18 2019
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0
mcsadmin>  



 Comments   
Comment by Todd Stoffel (Inactive) [ 2019-11-22 ]

This is expected behavior since the OAM monitoring does not recognize dynamic hostname changes. A restart of the cluster would be required in this case. I'm going to change this to a new feature request since it's not really a bug.

Comment by Todd Stoffel (Inactive) [ 2021-02-19 ]

Obsoleted by convergence.

Generated at Thu Feb 08 02:44:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.