Dgraph Alpha Eating Up All RAM

[lminaudier (Loïc Minaudier)]

@MichelDiz

Nope, each transaction should go in a robin(or a better balancing algo) manner to each Alpha. Sharding you are already doing. Each new Alpha without replicas is a shard/group.

You say that you have 3 replicas with 3 Alphas. Humm. So you have no shard. In my conception, having 3 replicas is quite consuming. Cuz any data coming, will be immediately replicated to the other instances. In that case, I would put the replicas in separate machines, cuz you gonna stress out the machine. That’s my opinion. I would keep only shards in the same machine.

Our setup is 3 alphas running on a dedicated i3.2xlarge EC2 instance. All alphas are part of the same group as we don’t use sharding. To my understanding, it means that the entire data we hold is replicated on the 3 alpha nodes right ?

@MichelDiz

But still, a single Alpha can happen to be overloaded with tasks if you not balance the transactions between them.

Our k8s service is in theory balancing request across all 3 alpha nodes.