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

Archival Support: Remove configurable support for catching up from "archivers" #5920

Merged
merged 5 commits into from Jan 25, 2024

Conversation

gmalouf
Copy link
Contributor

@gmalouf gmalouf commented Jan 25, 2024

Summary

This PR removes configurable support for catching up from or (in the case of block serving) falling back to "archivers"; a concept that was never utilized on mainnet nor is currently on testnet. This fits with the larger effort to support first class non-archival relays and dedicated archival nodes for catchup/catchpoint purposes.

A concurrency issue was addressed around read/write access to blockService.fallbackEndpoints.lastUsed along the way.

Test Plan

No longer relevant test scenarios are removed, a few cases were added in catchup service to reflect needing EnableGossipService set to be a relay, existing tests should otherwise pass.

@gmalouf gmalouf self-assigned this Jan 25, 2024
…arying settings for the EnableGossipService flag.
Copy link

codecov bot commented Jan 25, 2024

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (2e41eef) 56.02% compared to head (006b344) 55.94%.

Files Patch % Lines
network/wsNetwork.go 20.00% 3 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5920      +/-   ##
==========================================
- Coverage   56.02%   55.94%   -0.09%     
==========================================
  Files         478      478              
  Lines       67613    67561      -52     
==========================================
- Hits        37878    37794      -84     
- Misses      27176    27203      +27     
- Partials     2559     2564       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

…nd falling back/redirecting to them within the block service. Refactored blockservice redirect tests to primarily leverage 'getNextCustomFallbackEndpoint' for retrieving a peer list (empty by default.
@gmalouf gmalouf marked this pull request as ready for review January 25, 2024 14:01
@gmalouf gmalouf changed the title WIP: Remove configurable support for catching up from "archivers" Archival Support: Remove configurable support for catching up from "archivers" Jan 25, 2024
config/localTemplate.go Show resolved Hide resolved
rpcs/blockService.go Show resolved Hide resolved
catchup/service.go Show resolved Hide resolved
config/localTemplate.go Outdated Show resolved Hide resolved
config/localTemplate.go Outdated Show resolved Hide resolved
Co-authored-by: John Jannotti <jannotti@gmail.com>
Copy link
Contributor

@jannotti jannotti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no objections. The caveat is that I don't really understand the config json stuff.

Copy link
Contributor

@algorandskiy algorandskiy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, need to ensure (manual or auto test) that peer selector does not stuck when where is no archive DNS.

network/wsNetwork.go Show resolved Hide resolved
@gmalouf gmalouf merged commit 8631960 into algorand:master Jan 25, 2024
18 checks passed
@gmalouf gmalouf deleted the archiver-archival-merge branch January 25, 2024 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants