Skip to main content

Microsoft Orleans - Multi silo deployment behind a load balancer

In one of my projects we are using Orleans, the virtual actor framework from Microsoft. Your Orleans backend(the cluster) can span out over multiple servers(silos).

In a cluster there are 2 types of communication  happening:

  • silo-to-silo communication(through the silo port)
  • client-to-silo communication(through the gateway port)

As a result on every server 2 ports should be opened to enable this traffic.

Load balancing

The Orleans runtime does all the load balancing for you. More important it is one of the pillars of the Orleans runtime. The runtime tries to make everything balanced, since balancing allows to maximize resource usage and avoid hotspots, which leads to better performance, as well as helps with elasticity.

More information: https://dotnet.github.io/orleans/Documentation/implementation/load_balancing.html

This means that it doesn’t make sense to put a load balancer between the clients and the cluster as this would defy one of the core purposes of the Orleans runtime.

But what if a load balancer exists?

This was exactly the situation I had with one of my customers. They were not fully aware that it doesn’t make sense to add a load balancer and installed our Orleans application on 2 servers behind a load balancer.

What they noticed was the following? As long as only one silo was running everything worked as expected. However the moment a second silo was spinned up, the other one shut down.

The problem was that due to the load balancer both silo got the same IP address. This was easily detectable in the Orleans Membershiptable:

To solve it, we explicitly specified the IP address of each server in the silo configuration:

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more