hanishi commented on issue #2579: URL: https://github.com/apache/pekko/issues/2579#issuecomment-3650952115
@pjfanning @He-Pin Thanks for the explanation, that makes sense, and I agree that DurableStateBehavior generally encourages handling side effects via thenRun. That said, I did run into a concrete case where RecoveryCompleted is useful with DurableStateBehavior. After a restart, I need to re-publish the recovered state into DData (replicator) so that other nodes can see the current view. In that scenario, having a clear “recovery boundary” is important to avoid publishing before the state is fully loaded. So while signals may not be the primary mechanism for DurableStateBehavior, there are some scenarios where they’re still quite useful. Given that the hook and signal exist, even a short doc mention or example would help set expectations and avoid confusion around the correct import. Thanks again for looking into this, and I'm happy to defer to others’ insight on whether this was an intentional omission. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
