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

Use secondary storage for network graph #408

Open
tnull opened this issue Nov 21, 2024 · 1 comment
Open

Use secondary storage for network graph #408

tnull opened this issue Nov 21, 2024 · 1 comment

Comments

@tnull
Copy link
Collaborator

tnull commented Nov 21, 2024

Now that we're moving towards supporting remote storage in general and VSS in particular, we should consider discerning which data could/should still live only in a local data store. One such example would be NetworkGraph, that is if the network graph remains only an object storing gossip data, i.e., would only ever contain data that we can easily resync from the network.

@G8XSU
Copy link
Contributor

G8XSU commented Nov 21, 2024

Imo, in addition to network_graph, we should also explore more granular control over using different types of kv_stores.

For example not all stores need remote_first storage, some might be fine with local_fist, some could be better suited for sql backend. I might want to store my network_graph and scorer in object store like s3 etc.

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

No branches or pull requests

2 participants