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
{{ message }}
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.
Hi! I noticed that after joining a cluster (partisan_peer_service:join) and executing lasp:stream, it takes around a minute before the function passed to lasp:stream gets called. This only happens once, after startup. Succeeding changes to lasp variables are received immediately.
Is this the expected behavior? Is there something that I can configure to shorten the initial propagation time?
Thanks! :)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi! I noticed that after joining a cluster (
partisan_peer_service:join
) and executinglasp:stream
, it takes around a minute before the function passed tolasp:stream
gets called. This only happens once, after startup. Succeeding changes to lasp variables are received immediately.Is this the expected behavior? Is there something that I can configure to shorten the initial propagation time?
Thanks! :)
The text was updated successfully, but these errors were encountered: