Frequently Asked Questions

• SPI communication exception between EC2 nodes provisioned using AMS
• Ignite clustering not working on Rancher Kubernetes

SPI communication exception between EC2 nodes

• You may observe SPI communication exception between BE Ignite nodes deployed on EC2 boxes provisioned using Amazon Managed Service (AMS).
• Solution: Remove short name aliases (if any) from /etc/hosts file for the loopback IP entry i.e 127.0.0.1

Ignite clustering not working on Rancher Kubernetes

If node is not able to join the cluster try adding below annotations to the deployments:

traffic.sidecar.istio.io/excludeInboundPorts: "47100,47500"

traffic.sidecar.istio.io/excludeOutboundPorts: "47100,47500"