After a failed node recovered, connection alarms remained and not cleared

Build tested: 1.1.6-1 source

/root/columnstore/mariadb-columnstore-server
commit 513775738f72ec990d055a5d47e2511e3c0e34dd
Merge: 3c37210 9236098
Author: Andrew Hutchings <andrew@linuxjedi.co.uk>
Date: Wed Jul 18 09:37:17 2018 +0100

Merge pull request #123 from drrtuy/MCOL-970

MCOL-970 Slow query log now contains original query even in vtable mode

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit 150171b714c16bd91ef620ea483f6200ad775038
Merge: 1068679 8a42949
Author: benthompson15 <ben.thompson@mariadb.com>
Date: Thu Aug 9 17:49:01 2018 -0500

Merge pull request #535 from mariadb-corporation/MCOL-1605

MCOL-1605 - changed error to debug, alarms trying to get issued b

stack: 1um4pm, glusterfs

I suspended pm2 and there are 14 critical connection failure alarms. I resumed PM2, getprocessstatus show normally status, and the 14 critical alarms remained. They should be cleared if the stack came back to normal operation.