You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest changes of Restate, we are bootstrapping a cluster with a replication property of 1. That's why the verification test no longer tests the distributed setup. Once we have restatedev/restate#2409 implemented, we should update the verification test to provision the cluster with a replication property of 2.
The text was updated successfully, but these errors were encountered:
To run with a replication factor of 2, we need to manually provision the cluster
with it. This commit adds the required proto files and calls the grpc endpoint to
manually provision a cluster.
This fixesrestatedev#3.
To run with a replication factor of 2, we need to manually provision the cluster
with it. This commit adds the required proto files and calls the grpc endpoint to
manually provision a cluster.
This fixesrestatedev#3.
tillrohrmann
added a commit
to tillrohrmann/e2e-verification-runner
that referenced
this issue
Jan 14, 2025
To run with a replication factor of 2, we need to manually provision the cluster
with it. This commit adds the required proto files and calls the grpc endpoint to
manually provision a cluster.
This fixesrestatedev#3.
With the latest changes of Restate, we are bootstrapping a cluster with a replication property of 1. That's why the verification test no longer tests the distributed setup. Once we have restatedev/restate#2409 implemented, we should update the verification test to provision the cluster with a replication property of 2.
The text was updated successfully, but these errors were encountered: