-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node Version Heartbeat #15700
Merged
Merged
Node Version Heartbeat #15700
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f6b2abf
rough implementation of node heartbeat
patrickhuie19 3fb6504
consuming services engine to simplify tick + start/close handling
patrickhuie19 aec8866
fixing duration^2 bug
patrickhuie19 875daf2
fixing health tests
patrickhuie19 a6d3df3
fixing testscripts test; using eng logger; using time.seconds const
patrickhuie19 c45505a
minor refactoring
patrickhuie19 b47e64f
NodeHeartbeat --> Heartbeat
patrickhuie19 cc83e5b
removing close from Heartbeat
patrickhuie19 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it important to check these on start, and necessary to fail if they are not available? Or could we defer, and recall these each tick, in order to allow startup and recovery later if necessary?
If it does make sense to move them inside the tick func, maybe consider making it a separate method too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These specific resources, no. I don't expect them to fail, and their production implementations don't return errors:
I'd like to avoid putting resource init in the tick. I do think you've raised a good point re: recovery. I think the generic heartbeat is the better place to handle that. Since the init func is passed in as a consumer defined method there anyways, the generic heartbeat could handle a failure by storing that the resource init never completed successfully and then the next tick could try the resource init.
Consumers would have to be aware of this and ensure that the resource inits are idempotent, though. Or the generic heartbeat could handle this by having a user defined
onClose
functionality to erase un-wanted side-effects before the next tick invocation.