Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
7.4.0.Beta
-
None
-
False
-
False
-
Undefined
Description
I have noticed this strange situation during our test. We formed cluster of 3 nodes/pods; `hsc-1-vdchr`, `hsc-1-8rv72`, `hsc-1-nhvkn`.
But for some reason node `hsc-1-nhvkn` was named `95d313f5-e405-cbbb-5539-57068e93c59e` in log of `hsc-1-8rv72`.
[0m[0m16:57:30,602 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 77) ISPN000094: Received new cluster view for channel ee: [hsc-1-vdchr|2] (3) [hsc-1-vdchr, hsc-1-8rv72, 95d313f5-e405-cbbb-5539-57068e93c59e] [0m[0m16:57:30,603 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 80) ISPN000094: Received new cluster view for channel ee: [hsc-1-vdchr|2] (3) [hsc-1-vdchr, hsc-1-8rv72, 95d313f5-e405-cbbb-5539-57068e93c59e] [0m[0m16:57:30,603 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 79) ISPN000094: Received new cluster view for channel ee: [hsc-1-vdchr|2] (3) [hsc-1-vdchr, hsc-1-8rv72, 95d313f5-e405-cbbb-5539-57068e93c59e] [0m[0m16:57:30,603 INFO [org.infinispan.CLUSTER] (ServerService Thread Pool -- 78) ISPN000094: Received new cluster view for channel ee: [hsc-1-vdchr|2] (3) [hsc-1-vdchr, hsc-1-8rv72, 95d313f5-e405-cbbb-5539-57068e93c59e]
Then in same log this suspicious message was printed
[0m[33m16:57:31,190 WARN [org.jgroups.protocols.TCP] (non-blocking-thread--p5-t1) JGRP000032: hsc-1-8rv72: no physical address for 95d313f5-e405-cbbb-5539-57068e93c59e, dropping message
I suspect OpenShift internal DNS failed in this case. But I would like to know what do you think about it pferraro rhn-engineering-rhusar How severe `JGRP000032` is?
Seems to me cluster was formed. I don't know if cluster was working properly. Our test condition failed at beginning of test expecting cluster is formed from nodes named by pod names.
[1] com.redhat.xpaas.eap.ha.HAServletCounterDnsPingAsymEncryptTest