-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
clusterversion: set binaryMinSupportedVersion
on master to v21_1
#67277
Labels
A-cc-enablement
Pertains to current CC production issues or short-term projects
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-server-and-security
DB Server & Security
Comments
ajwerner
added
the
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
label
Jul 6, 2021
ajwerner
added a commit
to ajwerner/cockroach
that referenced
this issue
Jul 6, 2021
This probably should have been done when `Start21_2` was added. Fixes cockroachdb#67277. Release note: None
knz
added
the
A-cc-enablement
Pertains to current CC production issues or short-term projects
label
Jul 29, 2021
ajwerner
added a commit
to ajwerner/cockroach
that referenced
this issue
Jul 29, 2021
This probably should have been done when `Start21_2` was added. Fixes cockroachdb#67277. Release note: None
ajwerner
added a commit
to ajwerner/cockroach
that referenced
this issue
Jul 29, 2021
This probably should have been done when `Start21_2` was added. Fixes cockroachdb#67277. Release note: None
ajwerner
added a commit
to ajwerner/cockroach
that referenced
this issue
Jul 29, 2021
This probably should have been done when `Start21_2` was added. Fixes cockroachdb#67277. Release note: None
ajwerner
added a commit
to ajwerner/cockroach
that referenced
this issue
Aug 2, 2021
This probably should have been done when `Start21_2` was added. Fixes cockroachdb#67277. Release note: None
craig bot
pushed a commit
that referenced
this issue
Aug 3, 2021
66600: sql: Store instance ID and network addresses of SQL pods r=rimadeodhar a=rimadeodhar This change adds a new system table, sql_instances, for storing SQL instance information in a multi-tenant environment. This table will be used to store and propagate unique instance ids and network address information on individual SQL pods. This change also implements a storage layer for accessing the sql_instances system table using the KV API. We need to use KV API as this table will be accessed and updated prior to the construction of a SQL server for the tenant. It also implements the provider interface for using this new sqlinstance subsystem to assign unique instance ids per pod and propagate their network information. This is a part of #62818, resolves #64475 Release Note (general change): Add sqlinstance subsystem for creating unique instance ids per SQL pod and for propagating network address for SQL pods within a single tenant. 67281: clusterversion: set `binaryMinSupportedVersion` to `v21_1` r=ajwerner a=ajwerner This probably should have been done when `Start21_2` was added. Fixes #67277. Release note: None 68280: SQL: Reset database zone configuration builtin r=arulajmani a=ajstorm The new(ish) multi-region syntax introduced in 21.1 sets a zone configuration at the database level. This zone configuration can diverge from its original state either because the user has manually overridden it, or because the system hasn't kept it up to date as the database has evolved (though there are no known issues where this occurs). In either case, the user may wish to revert the zone configurations for a given databases back to its original state. The new builtin takes a database ID, and resets its underlying zone configuration to its original state (as specified by the underlying RegionConfig). For non-multi-region databases, the builtin no-ops. Resolves #66855. Release note (sql change): Creates a builtin to reset the zone configuration of a multi-region database. This builtin can be helpful in cases where the user has overridden the zone configuration for a given database and wishes to revert back to the original system-specified state. 68400: ci: enlarge boot disks for `roachtest` clusters from 10GiB->32GiB r=jlinder a=rickystewart These tests are sometimes failing due to running out of storage space on the `roachprod` clusters used by `roachtest` (see #68166). Try to resolve it by bumping up the size of the boot disks. Release note: None Co-authored-by: rimadeodhar <rima@cockroachlabs.com> Co-authored-by: Andrew Werner <awerner32@gmail.com> Co-authored-by: Adam Storm <storm@cockroachlabs.com> Co-authored-by: Ricky Stewart <ricky@cockroachlabs.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-cc-enablement
Pertains to current CC production issues or short-term projects
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-server-and-security
DB Server & Security
Is your feature request related to a problem? Please describe.
We should probably have done this when we introduced
Start21_2
. Internal discussion here and here. Does not depend on but does relate to #33578.The text was updated successfully, but these errors were encountered: