On CouchBase 5.0.1 Community Edition for RHEL7, 'Got notified from Channel as inactive'


#1

On upgrading to CouchBase 5.0.1 Community Edition for RHEL7 & the setup is three node cluster , I see below log messages:

2018-04-10 07:08:34,381| INFO | [] - [/xx:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-1 | c.c.c.c.e.Endpoint
2018-04-10 07:08:34,389| INFO | [] - [/yy:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-2 | c.c.c.c.e.Endpoint
2018-04-10 07:08:34,415| INFO | [] - [zz:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-3 | c.c.c.c.e.Endpoint
2018-04-10 07:08:54,383| INFO | [] - [/xx:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-1 | c.c.c.c.e.Endpoint
2018-04-10 07:08:54,412| INFO | [] - [/yy:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-2 | c.c.c.c.e.Endpoint
2018-04-10 07:08:54,416| INFO | [] - [zz:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-3 | c.c.c.c.e.Endpoint
2018-04-10 07:09:14,384| INFO | [] - [/xx:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-1 | c.c.c.c.e.Endpoint
2018-04-10 07:09:14,414| INFO | [] - [/yy:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-2 | c.c.c.c.e.Endpoint
2018-04-10 07:09:14,417| INFO | [] - [zz:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-3 | c.c.c.c.e.Endpoint
2018-04-10 07:09:34,386| INFO | [] - [/xx:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-1 | c.c.c.c.e.Endpoint
2018-04-10 07:09:34,417| INFO | [] - [/yy:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-2 | c.c.c.c.e.Endpoint
2018-04-10 07:09:34,418| INFO | [] - [zz:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-3 | c.c.c.c.e.Endpoint
2018-04-10 07:09:54,388| INFO | [] - [/xx:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-1 | c.c.c.c.e.Endpoint
2018-04-10 07:09:54,418| INFO | [] - [/yy:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-2 | c.c.c.c.e.Endpoint
2018-04-10 07:09:54,420| INFO | [] - [zz:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-3 | c.c.c.c.e.Endpoint
2018-04-10 07:10:14,389| INFO | [] - [/xx:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-1 | c.c.c.c.e.Endpoint
2018-04-10 07:10:14,420| INFO | [] - [/yy:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-2 | c.c.c.c.e.Endpoint
2018-04-10 07:10:14,421| INFO | [] - [zz:8094][SearchEndpoint]: Got notified from Channel as inactive, attempting reconnect. | cb-io-1-3 | c.c.c.c.e.Endpoint

Can you help to understand this information further.


#2

That’s referring to a Channel associated with a TCP connection. It’s generally normal for disconnections to happen during an upgrade. Notice that they’re INFO level. If the updated cluster topology says to connect to the node, it will reconnect.


#3

Thank you… that helps !!