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

chore: added estuary peering peers #337

Merged
merged 1 commit into from
Jul 19, 2022
Merged

chore: added estuary peering peers #337

merged 1 commit into from
Jul 19, 2022

Conversation

alvin-reyes
Copy link
Contributor

@alvin-reyes alvin-reyes commented Jul 19, 2022

Change

Add estuary peers on the peering list

Verification (/admin/peering/peers)

image

@alvin-reyes alvin-reyes marked this pull request as ready for review July 19, 2022 21:25
Copy link
Contributor

@gmelodie gmelodie left a comment

Choose a reason for hiding this comment

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

@alvin-reyes the PR looks solid. Just one question though: what are these peers being added for? So that every estuary node can peer with our hosted main node + shuttles? If so, what benefit does this bring?

@alvin-reyes
Copy link
Contributor Author

Estuary has a /gw (gateway) to can be used to retrieve content from other peers. If we have a CID pinned on a shuttle, the the gateway node (in this case the main estuary node) can locate the CID more efficiently.

@alvin-reyes alvin-reyes merged commit ef93e7a into master Jul 19, 2022
@alvin-reyes alvin-reyes deleted the est-peering branch July 20, 2022 01:34
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