-
Notifications
You must be signed in to change notification settings - Fork 407
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
Epic: compute support for sharding phase 1 #5508
Comments
5 tasks
knizhnik
pushed a commit
that referenced
this issue
Dec 20, 2023
5 tasks
jcsp
pushed a commit
that referenced
this issue
Dec 22, 2023
knizhnik
pushed a commit
that referenced
this issue
Dec 27, 2023
jcsp
pushed a commit
that referenced
this issue
Jan 2, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 2, 2024
@hlinnaka , waiting for your final review |
jcsp
pushed a commit
that referenced
this issue
Jan 3, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 7, 2024
knizhnik
pushed a commit
that referenced
this issue
Jan 10, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 11, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 16, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 17, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 17, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 17, 2024
jcsp
pushed a commit
that referenced
this issue
Jan 18, 2024
to merge it this week |
knizhnik
added a commit
that referenced
this issue
Jan 25, 2024
refer #5508 replaces #5837 ## Problem This PR implements sharding support at compute side. Relations are splinted in stripes and `get_page` requests are redirected to the particular shard where stripe is located. All other requests (i.e. get relation or database size) are always send to shard 0. ## Summary of changes Support of sharding at compute side include three things: 1. Make it possible to specify and change in runtime connection to more retain one page server 2. Send `get_page` request to the particular shard (determined by hash of page key) 3. Support multiple servers in prefetch ring requests ## Checklist before requesting a review - [ ] I have performed a self-review of my code. - [ ] If it is a core feature, I have added thorough tests. - [ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard? - [ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section. ## Checklist before merging - [ ] Do not forget to reformat commit message to not include the above checklist --------- Co-authored-by: Konstantin Knizhnik <knizhnik@neon.tech> Co-authored-by: John Spray <john@neon.tech> Co-authored-by: Heikki Linnakangas <heikki@neon.tech>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #5507 for the related pageserver work.
RFC in progress here: #5432
Tasks
The text was updated successfully, but these errors were encountered: