Till Rohrmann
Till Rohrmann
Is this issue resolved via c2a44e2c863131a0ca20845e08321d6f2c70cf5a?
> It simply doesn't work. You can't use the new trim and restart feature unless you're 100% sure you're using the new restate version, that's the constraint. So should this...
> I guess we can, but we can also defer this decision to a later point IMO. If so, then please create a release blocker issue for the next release....
This issue is related to #1651 since it refers to the communication between the ingress and the partition processor.
The problem of crashing nodes during a rolling upgrade could be solved by only activating the new state machine version in the next version (similar to how we do it...
To sum up the current discussion: Right now, we don't have a mechanism to change the behavior of the business logic (PP state machine) which is not based on input...
fyi @AhmedSoliman
Thanks for raising this issue @ryansun96. The reverse service connection (the service deployment registering at the server) is a feature that we have discussed already for quite some time and...
Thanks for clarifying your requirements @ryansun96. If the service name is not DNS resolvable and needs some other resolution API then we are indeed lacking support for it. In theory...
One way to solve this problem is to introduce a `WorkerState` that we store in the `NodesConfiguration`. The variants could be: ``` enum WorkerState { /// Node should be considered...