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

Release 2023 04 30 #4126

Merged
merged 20 commits into from
May 1, 2023
Merged

Release 2023 04 30 #4126

merged 20 commits into from
May 1, 2023

Conversation

arssher
Copy link
Contributor

@arssher arssher commented Apr 30, 2023

Release 2023-04-30

NB: this PR must be merged only by 'Create a merge commit'!

Checklist when preparing for release

  • Read or refresh the release flow guide
  • Ask in the cloud Slack channel that you are going to rollout the release. Any blockers?
  • Does this release contain any db migrations? Destructive ones? What is the rollback plan?

Checklist after release

kelvich and others added 20 commits April 28, 2023 17:15
In order to not to create NodePorts for each compute we can setup
services that accept connections on wildcard domains and then use
information from domain name to route connection to some internal
service. There are ready solutions for HTTPS and TLS connections
but postgresql protocol uses opportunistic TLS and we haven't found
any ready solutions.

This patch introduces `pg_sni_router` which routes connections to
`aaa--bbb--123.external.domain` to `aaa.bbb.123.internal.domain`.

In the long run we can avoid console -> compute psql communications,
but now this router seems to be the easier way forward.
Makes it easier to test locally.
As soon as we have received the SSLRequest packet, and have figured
out the hostname to connect to from the SNI, we can start passing
through data. We don't need to parse the StartupPacket that the client
will send next.
This reverts commit 732acc5.

Reverted PR: #3869

As noted in PR #4094, we do in fact try to insert duplicates to the
layer map, if L0->L1 compaction is interrupted. We do not have a proper
fix for that right now, and we are in a hurry to make a release to
production, so revert the changes related to this to the state that we
have in production currently. We know that we have a bug here, but
better to live with the bug that we've had in production for a long
time, than rush a fix to production without testing it in staging first.

Cc: #4094, #4088
Add HTTP endpoint to initialize safekeeper timeline from peer
safekeepers. This is useful for initializing new safekeeper to replace
failed safekeeper. Not fully "correct" in all cases, but should work in
most.

This code is not suitable for production workloads but can be tested on
staging to get started. New endpoint is separated from usual cases and
should not affect anything if no one explicitly uses a new endpoint. We
can rollback this commit in case of issues.
## Describe your changes
Adding 4 new pageserves to us-west

TF apply output:
module.pageserver-us-west-2.aws_instance.this["7"]: Creation complete
after 21s [id=i-02eec9b40617db5bc]
module.pageserver-us-west-2.aws_instance.this["5"]: Creation complete
after 21s [id=i-00ca6417c7bf96820]
module.pageserver-us-west-2.aws_instance.this["4"]: Creation complete
after 21s [id=i-013263dd1c239adcc]
module.pageserver-us-west-2.aws_instance.this["6"]: Creation complete
after 22s [id=i-01cdf7d2bc1433b6a]
Add patch directive to Cargo.toml to use patched version of
sharded-slab:
neondatabase/sharded-slab@98d1675

Patch changes the MAX_THREADS limit from 4096 to 32768. This is a
temporary workaround for using tracing from many threads in safekeepers
code, until async safekeepers patch is merged to the main.

Note that patch can affect other rust services, not only the safekeeper
binary.
@arssher arssher requested review from a team as code owners April 30, 2023 04:35
@arssher arssher requested review from petuhovskiy, piercypixel and MMeent and removed request for a team April 30, 2023 04:35
@arssher arssher requested review from shanyp and removed request for a team April 30, 2023 04:35
@github-actions
Copy link

Test results for 21eb944:


debug build: 222 tests run: 212 passed, 0 failed, 10 (full report)


release build: 222 tests run: 212 passed, 0 failed, 10 (full report)


@kelvich kelvich merged commit 21eb944 into release May 1, 2023
@kelvich kelvich deleted the release-2023-04-30 branch May 1, 2023 15:52
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.

9 participants