-
Notifications
You must be signed in to change notification settings - Fork 49
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
Separate heartbeat_periods and reporting_period #1356
Conversation
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.
We'll also need to update the engine_runner fixture and the status report tests.
compute_endpoint/globus_compute_endpoint/engines/globus_compute.py
Outdated
Show resolved
Hide resolved
7217414
to
eb6f4fb
Compare
…, and ThreadPoolEngine
d7ad2c6
to
64ae4ed
Compare
* Test fixes * Removing heartbeat params from engine init * Minor perf improvements
64ae4ed
to
d2ca73f
Compare
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.
Nice!
[sc-28343] |
This pull request has been linked to Shortcut Story #28343: Separate engine heartbeats and endpoint status reporting periods. |
Description
The
GlobusComputeEngine
has a notion ofhearbeat_period
andheartbeat_threshold
used internally to track worker liveness. This is separate from the status reporting logic implemented in theGlobusComputeEngineBase
that sendsEPStatusReports
.This PR sets the
reporting period
to a constant. Users should not be able to tweak this, and we should not be supporting cases where there's any functionality built on faster updates.Fixes # (issue)
Type of change
Choose which options apply, and delete the ones which do not apply.