Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Slack vitess 9 2021.03.16r0 #200

Merged
merged 1,218 commits into from
Apr 7, 2021

Conversation

setassociative
Copy link

@setassociative setassociative commented Mar 17, 2021

Upstream Release Notes

These are the notes for the official release. Later on, the PR's that we explicitly call out are the ones that are not in the notes that we consider interesting / risky for our deployment.

https://github.com/vitessio/vitess/releases/tag/v9.0.0

Slack changes

Non Slack changes (interesting)

PR's we should be really really careful:

Features that we haven been wanting

VReplication changes

Online schema DDL

  • These are explicitly on the release, but still worth mentioning. We can start playing with all the online schema changes functionalities that Shlomi has been working on.

Query parser / routing changes

Constructing the branch

# find point of divergence between 8 & 9
git merge-base upstream/release-8.0 upstream/release-9.0

# reset to common point to generate a good diff and set a stake in that sha
git checkout 098845592f16d235cb440bdafe070b4dcc0eb07b
git checkout -b slack-vitess-9-2021.03.16r0

# start the branch to generate this PR / the diff
git checkout -b slack-vitess-9-2021.03.16r0.wip

# set that branch to be what we want to deploy
git reset --hard upstream/release-9.0

# cherry-pick some changes

Cherry Picked Changes

$ git llog upstream/release-9.0...slack-vitess-9-2021.03.16r0.wip
2021-03-15 - 7f8a0bbb5 - setassociative - Fix bug in vtgate when running with keyspace filtering (#199)
2021-03-09 - 8da0a142f - setassociative - Backport vitessio#7523 into 8.0 (#198)
2021-03-08 - 60efc9139 - setassociative - Backport some panic protection during ERS (#196)
2020-03-05 - 00381f49f - mdemmer - add a hack to enable routing to RDONLY tablets for REPLICA queries
2019-02-25 - 3d3f66091 - setassociative - Patch sqltypes.MakeRowTrusted to lean on field count (#126)

doeg and others added 30 commits December 22, 2020 11:54
artifact tables are named after the migration UUID (this helps in tracking their origin)

Signed-off-by: Shlomi Noach <[email protected]>
Signed-off-by: Sara Bee <[email protected]>
Signed-off-by: Sara Bee <[email protected]>
Signed-off-by: Sara Bee <[email protected]>
Signed-off-by: Sara Bee <[email protected]>
…-pool

Online DDL executor databae pool size increase
Do vschema_customer_sharded.json before create_customer_sharded.sql.
Signed-off-by: Shlomi Noach <[email protected]>
sougou and others added 24 commits January 23, 2021 15:18
Backport and fix tags for examples/operator
Return error immediately if the target keyspace is unknown. Do
the same for the source keyspace. Currently, the code will
attempt to continue with a bad keyspace name.

Signed-off-by: Jordan Moldow <[email protected]>
Backport 7361: vtctl: Add missing err checks for VReplication v2
Signed-off-by: Alkin Tezuysal <[email protected]>
… branch instead of always using latest

Signed-off-by: deepthi <[email protected]>
Fix Dockerfiles for vtexplain and vtctlclient
Signed-off-by: Harshit Gangal <[email protected]>
Fix table parsing on VSchema generation
…rted keyspace does not account for default selected keyspace on that session.

Signed-off-by: Harshit Gangal <[email protected]>
Signed-off-by: Harshit Gangal <[email protected]>
[9.0] Show anywhere plan fix to consider default keyspace
[9.0] Reset Session for Reserved Connection when the connection id is not found
Patch to handle this case while we move towards a permanent fix upstream.
cf. vitessio#4661 vitessio#4669
Backport some panic protection during ERS

This takes the core of the change from vitessio#7486 and backports it into 8.0.

Signed-off-by: Richard Bailey <[email protected]>
OP vitessio#7523

This basically protects from trying to catch up on replication on hosts
that are likely not replicating.

Signed-off-by: Richard Bailey <[email protected]>
This checks if a vtgate is currently filtering keyspaces before requesting the TopoServer. This is necessary because a TopoServer can't be accessed in those cases as the filtered Topo in those cases could make it unsafe to make writes since all reads would be returning a subset of the actual topo data.

The only use of the requested topoServer that I found was in the DDL handling path and was introduced in vitessio#6547.

This is deployed on dev but should get testing (endtoend or unit, unclear on best path atm) before going upstream.
Signed-off-by: Harshit Gangal <[email protected]>
@rafael rafael changed the title [draft] Slack vitess 9 2021.03.16r0.wip Slack vitess 9 2021.03.16r0.wip Apr 5, 2021
@rafael rafael changed the title Slack vitess 9 2021.03.16r0.wip Slack vitess 9 2021.03.16r0 Apr 7, 2021
@rafael rafael marked this pull request as ready for review April 7, 2021 17:25
Copy link

@rafael rafael left a comment

Choose a reason for hiding this comment

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

LGTM

@rafael rafael merged commit 12c6e5d into slack-vitess-9-2021.03.16r0 Apr 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.