You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a follow-up to #17216, we want to make sure that there is always a persisted version cluster setting for folks running 1.1. In particular, this means that a new cluster initialized using v1.1 should have a persisted version setting.
@dt pointed out in #17216 that there is a precedent:
For the diagnostic reporting setting, semantically we wanted a default of true, but since settings need to be allowed to return defaults until they are read and didn't want to risk ignoring an explicit false and betraying user trust, we went with a default of false with a startup migration writing an explicit true (optInToDiagnosticsStatReporting in migrations.go). This feels pretty similar.
The text was updated successfully, but these errors were encountered:
This uses the previously added bootstrap version which is populated when a
cluster running >1.0 is bootstrapped to populate the settings table. At the
same time, prevent `SET CLUSTER SETTING version = 'x'` from working until
that migration has run.
This solves one remaining headache for [version migrations][1] by giving it
authoritative information on the currently running cluster version during
upgrades.
Fixescockroachdb#17389.
[1]: cockroachdb#16977
As a follow-up to #17216, we want to make sure that there is always a persisted version cluster setting for folks running 1.1. In particular, this means that a new cluster initialized using v1.1 should have a persisted version setting.
@dt pointed out in #17216 that there is a precedent:
#17216 (comment)
The text was updated successfully, but these errors were encountered: