Skip to content
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 29 commits into from
Jun 26, 2024
Merged

refactor!: worker status #254

merged 29 commits into from
Jun 26, 2024

Conversation

brucexc
Copy link
Collaborator

@brucexc brucexc commented Jun 5, 2024

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

  1. add new scheduler service enforcer instead of reliability_score
  2. upgrade golangci-lint to 1.58.1 to match the node.

@brucexc brucexc marked this pull request as draft June 5, 2024 02:26
# Conflicts:
#	internal/service/hub/handler/nta/node_register.go
@brucexc brucexc removed the request for review from HenryQW June 13, 2024 02:48
@brucexc brucexc requested a review from HenryQW June 17, 2024 03:34
@brucexc brucexc self-assigned this Jun 17, 2024
@brucexc brucexc marked this pull request as ready for review June 17, 2024 03:35
@brucexc brucexc merged commit 8d04f22 into main Jun 26, 2024
5 checks passed
@brucexc brucexc deleted the feat/worker_status branch June 26, 2024 00:04
@brucexc
Copy link
Collaborator Author

brucexc commented Jun 26, 2024

close RSS3-Network/Protocol-Go#33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants