Till Rohrmann
Till Rohrmann
To run the `RaftMetadataStore` distributed, we need to allow them to communicate with remote peers. It would be great if we could reuse the already existing `Networking` component. The current...
We need to solve these known issues to make Restate correct: ```[tasklist] ### Tasks - [ ] #1768 - [ ] #1714 - [ ] #1651 ```
The partition processor scheduler needs to ensure that enough `PartitionProcessors` are running wrt the configured `ReplicationStrategy`. Moreover, it needs to ensure that there is always a single leader for every...
Restate logs wrong invocation id when invoking a service idempotently. In the screenshot I am invoking the same greeter/greet handler idempotently. However, we see that the second invocation gets logged...
In order to make the `RaftMetadataStore` durable, we need to add a `Storage` implementation that supports durable storage. I suggest to explore RocksDB for this purpose.
We might be able to use [raft](https://crates.io/crates/raft) to build a metadata store.
With the fix for #1639, we are now issuing a RocksDB scan operation for every outbox read by the shuffle. This is highly inefficient and should rather use a tailing...
In order to support differently configured node svc addresses, the admin crate must not assume that it is running on `127.0.0.1:5122`. Instead it should read it from the configuration. https://github.com/restatedev/restate/blob/e3bfec752620f37cfb387d6229a924462b059158/crates/node/src/roles/admin.rs#L114.
It would be great to make the channel settings configurable here: https://github.com/restatedev/restate/blob/8ea75044bb4b4504b685c302b1336fbc0d6f8d72/crates/core/src/network/net_util.rs#L45.
Make it configurable when an invocation is classified as too long holding the lock: https://github.com/restatedev/restate/blob/a5653185f4f3aeb0675a0b78a042688661a4dba4/cli/src/commands/services/status/mod.rs#L279