Till Rohrmann
Till Rohrmann
We decided to replace the existing ingress pp communication via RPCs: * Change the communication between ingresses and partition processors to be RPC-based * Ingresses ask leading partition processors for...
One way to make the retry behavior event-driven and not timeout-based is to require that responses to requests need to be sent via the same physical connection on which the...
Fixed via https://github.com/restatedev/restate/commit/3a293a4e402a22402ca3895c6bb9c41002d9c040
Thanks for reporting this issue @ryanleecode. The original idea was to keep the Restate container image as lean as possible because we didn't know what tools people would like to...
The problem is that the Raft cluster might change its leadership and thereby calls might fail with an retryable error. All client interactions should be retried.
@muhamadazmy, @slinkydeveloper has this issue been resolved with the `--extra` work?
Thanks for the update @muhamadazmy. I think this issue does not have to resolved for 1.6. So you can leave it be for the time being.
The invoker has a concurrency limit configurable via https://docs.restate.dev/references/server-config#param-concurrent-invocations-limit which controls how many concurrent invocations can be executed by the invoker. There is one invoker per partition. This is primarily...
The logs don't show anything because the test is not failing and therefore we don't see the logs of the Restate server processes. I think we should add a timeout...
@pcholakov has this been covered with the `NodeSetSelector` PR?