-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
refactor!: worker status #254
Merged
Merged
Conversation
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
# Conflicts: # internal/service/hub/handler/nta/node_register.go
brucexc
force-pushed
the
feat/worker_status
branch
from
June 12, 2024 01:26
eaf0df7
to
431db16
Compare
# Conflicts: # go.mod
# Conflicts: # docs/openapi.go
# Conflicts: # go.mod
HenryQW
approved these changes
Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
description
At the start of each epoch, GI queries the /workers_status API on each node to identify the supported worker types and determine if the node qualifies as a full node. Full nodes are prioritized in the request distribution process. However, if a node's /workers_status API response is erroneous or abnormal during this check, it will be disqualified from distributing requests for that entire epoch cycle.
It is recommended that all nodes upgrade to at least version v0.5.17.
breaking changes
enforcer
instead ofreliability_score