Skip to content

eval: ensure exprs are resent on reconnect#1557

Merged
brharrington merged 1 commit intoNetflix:mainfrom
brharrington:eval-reconnect
May 27, 2023
Merged

eval: ensure exprs are resent on reconnect#1557
brharrington merged 1 commit intoNetflix:mainfrom
brharrington:eval-reconnect

Conversation

@brharrington
Copy link
Copy Markdown
Contributor

If the websocket to an lwcapi node fails and needs to reconnect, then the message with the set of expressions needs to be resent. Before this would only happen when there was a change in either the set of remote instances or the set of expressions. With this change, the set of expressions will get repeated every 5s so it will get resent on a reconnect.

Note, the websocket sub-flow already has some deduping if there is no change, so the additional overhead during normal operations is minimal. If there is a failure, then the sub-flow will get restarted and the state for the unique operator will get reset allowing the repeated expression message through.

If the websocket to an lwcapi node fails and needs to reconnect,
then the message with the set of expressions needs to be resent.
Before this would only happen when there was a change in either
the set of remote instances or the set of expressions. With this
change, the set of expressions will get repeated every 5s so it
will get resent on a reconnect.

Note, the websocket sub-flow already has some deduping if there
is no change, so the additional overhead during normal operations
is minimal. If there is a failure, then the sub-flow will get
restarted and the state for the `unique` operator will get reset
allowing the repeated expression message through.
@brharrington brharrington added this to the 1.8.0 milestone May 27, 2023
@brharrington brharrington merged commit 9ebf5f8 into Netflix:main May 27, 2023
@brharrington brharrington deleted the eval-reconnect branch May 27, 2023 16:56
manolama pushed a commit to manolama/atlas that referenced this pull request May 22, 2024
If the websocket to an lwcapi node fails and needs to reconnect,
then the message with the set of expressions needs to be resent.
Before this would only happen when there was a change in either
the set of remote instances or the set of expressions. With this
change, the set of expressions will get repeated every 5s so it
will get resent on a reconnect.

Note, the websocket sub-flow already has some deduping if there
is no change, so the additional overhead during normal operations
is minimal. If there is a failure, then the sub-flow will get
restarted and the state for the `unique` operator will get reset
allowing the repeated expression message through.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant