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

SharedStorage design docs or examples #3177

Closed
tylerwilliams opened this issue Dec 20, 2023 · 3 comments
Closed

SharedStorage design docs or examples #3177

tylerwilliams opened this issue Dec 20, 2023 · 3 comments
Labels
A-storage question Further information is requested T-storage
Projects

Comments

@tylerwilliams
Copy link

Hi, we currently use pebble on large NAS ssd-like drives. Have been watching the development of the SharedStorage feature with interest, but I'm having trouble getting a big picture description of how it's used and the tradeoffs involved outside of just reading the code.

Is there anything you can share here about this new addition, it's purpose, production readiness, performance, etc?

Thanks! (pebble rocks btw)

@blathers-crl blathers-crl bot added this to Incoming in Storage Dec 20, 2023
@nicktrav nicktrav added the question Further information is requested label Jan 9, 2024
@nicktrav nicktrav moved this from Incoming to Community in Storage Jan 9, 2024
@RaduBerinde
Copy link
Member

Hi,

Thanks for the interest. This feature is currently in development and is not ready to use. The goal is to be able to store SSTs on systems like S3, either permanently or temporarily. This can allow faster restores from backup, or faster rebalancing of ranges between cockroach nodes.

@jlewi
Copy link

jlewi commented May 29, 2024

There are a couple older issues regarding plans for an S3 backend (#640, #805). Does SharedStorage mean supporting object storage is now in the works?

I have the following use case. I'd like to be able to run a KV store API server that scales from 0 to 1. If Pebble can use an object store as a backend then this becomes very easy to implement.

@RaduBerinde
Copy link
Member

We have the experimental ability to read and write sstables to S3, but the latencies are too high in practice to use directly and the per-IO pricing might also make it unfeasible. Unfortunately, for now, we don't have anything here that can be used in production.

Storage automation moved this from Community to Done May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-storage question Further information is requested T-storage
Projects
Status: Done
Storage
  
Done
Development

No branches or pull requests

4 participants