changelog/16.0/16.0.2/release_notes.md
v16.0.2During upgrades from <= v15.x.x to v16.0.2, as part of PromoteReplica call, the schema-init realizes that there are schema diffs to apply and ends up writing to the database if semi-sync is enabled, all of these writes get blocked indefinitely.
Eventually, PromoteReplica fails, and this fails the entire PRS call.
A fix for this issue was merged on release-16.0 in PR#13441, read the corresponding bug report to learn more.
This issue is fixed in v16.0.3 and later patch releases.
In v17.x.x super_read_only is turned on by default meaning that downgrading from v17 to v16.0.2 breaks due to init_db.sql needing write access.
This issue is fixed in >= v16.0.3 thanks to PR #13525
go1.20.3Vitess v16.0.2 now runs on go1.20.3.
Below is a summary of this Go patch release. You can learn more here.
go1.20.3 (released 2023-04-04) includes security fixes to the go/parser, html/template, mime/multipart, net/http, and net/textproto packages, as well as bug fixes to the compiler, the linker, the runtime, and the time package. See the Go 1.20.3 milestone on our issue tracker for details.
A new flag grpc-use-static-authentication-callerid is added to gate the behavior introduced in https://github.com/vitessio/vitess/pull/12050.
Earlier, we used to automatically set immediateCallerID to user from static authentication context that overrode the EffectiveCallerId.
Prior to v16.0.2, it was possible to create a shard name with invalid characters, which would then be inaccessible to various cluster management operations.
Shard names may no longer contain the forward slash ("/") character, and TopoServer's CreateShard method returns an error if given such a name.
The entire changelog for this release can be found here.
The release includes 24 commits (excluding merges)
Thanks to all our contributors: @GuptaManan100, @ajm188, @frouioui, @github-actions[bot], @harshit-gangal, @mattlord, @systay, @vitess-bot[bot]