CzyerChen commented on PR #12109: URL: https://github.com/apache/skywalking/pull/12109#issuecomment-2060289662
> > ` - VIRTUAL_MQ -> ACTIVEMQ` may have to check `cluster` mode, rather than single node. if client connected by `failover:(tcp://amq1:61616,tcp://amq2:61617)`, it may hard to continue service hierarchy. > > How could this be in k8s? I think K8s should be DNS oriented right? Even with a cluster, client should use service address like `activemq-svr.namespace.cluster`. > > VM deployment is complex, we are hard to make service hierarchy working in that deployment out-of-box. Normally we use failover transport to connect server node on client side, like `failover:(tcp://broker1.namespace.cluster:61616,tcp://broker2.namespace.cluster:61616,tcp://broker3.namespace.cluster:61616)?transportOptions` in K8S. In Master-Slave or Broker cluster mode, If just configure one node of Broker on client side, the failover will not work automatically. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
