Skip to content

Commit

Permalink
Release commit for 13.0.0
Browse files Browse the repository at this point in the history
Signed-off-by: Florent Poinsard <[email protected]>
  • Loading branch information
frouioui committed Feb 22, 2022
1 parent bd4a46f commit bc4a960
Show file tree
Hide file tree
Showing 14 changed files with 246 additions and 238 deletions.
401 changes: 204 additions & 197 deletions doc/releasenotes/13_0_0_release_notes.md

Large diffs are not rendered by default.

11 changes: 6 additions & 5 deletions doc/releasenotes/13_0_0_summary.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ alter vitess_migration '9748c3b7_7fdb_11eb_ac2c_f875a4d24e90' complete
This command indicates that a migration executed with `-postpone-completion` is good to complete. Behavior:

- For running `ALTER`s (`online` and `gh-ost`) which are ready to cut-over: cut-over imminently (though not immediately
- cut-over depends on polling interval, replication lag, etc)
- cut-over depends on polling interval, replication lag, etc)
- For running `ALTER`s (`online` and `gh-ost`) which are only partly through the migration: they will cut-over
automatically when they complete their work, as if `-postpone-completion` wasn't indicated
- For queued `CREATE` and `DROP` migrations: "unblock" them from being scheduled. They'll be scheduled at the scheduler'
Expand Down Expand Up @@ -142,7 +142,7 @@ in https://github.com/vitessio/vitess/pull/9136.

### PlannedReparentShard for cluster initialization
For setting up the cluster and electing a primary for the first time, `PlannedReparentShard` should be used
instead of `InitShardPrimary`.
instead of `InitShardPrimary`.

`InitShardPrimary` is a forceful command and copies over the executed gtid set from the new primary to all the other replicas. So, if the user
isn't careful, it can lead to some replicas not being setup correctly and lead to errors in replication and recovery later.
Expand All @@ -156,7 +156,7 @@ A new flag has been added to vtctl, vtctld and vtworker binaries which allows th

If semi-sync is not being used then `-durability_policy` should be set to `none`. This is also the default option.

If semi-sync is being used then `-durability_policy` should be set to `semi_sync` and `-enable_semi_sync` should be set in vttablets.
If semi-sync is being used then `-durability_policy` should be set to `semi_sync` and `-enable_semi_sync` should be set in vttablets.

## Incompatible Changes
### Error message change when vttablet row limit exceeded:
Expand All @@ -183,6 +183,7 @@ If semi-sync is being used then `-durability_policy` should be set to `semi_sync
```shell
W0112 09:38:59.169264 35943 tabletserver.go:1503] Row count exceeded 10000 (errno 10001) (sqlstate HY000) ...
```
* If you were using -queryserver-config-terse-errors to redact some log messages containing bind vars in 13.0-SNAPSHOT, you should now instead enable -sanitize_log_messages which sanitizes all log messages containing sensitive info

### Column types for textual queries now match MySQL's behavior

Expand All @@ -203,6 +204,6 @@ this flag should be updated to remove the flag as it will be deleted in the next

### web/vtctld2 is deprecated and can optionally be turned off

The vtctld2 web interface is no longer maintained and is planned for removal in Vitess 16. Motivation for this change and a roadmap to removing [the web/vtctld2 codebase](https://github.com/vitessio/vitess/tree/main/web/vtctld2) is given in https://github.com/vitessio/vitess/issues/9686.
The vtctld2 web interface is no longer maintained and is planned for removal in Vitess 16. Motivation for this change and a roadmap to removing [the web/vtctld2 codebase](https://github.com/vitessio/vitess/tree/main/web/vtctld2) is given in https://github.com/vitessio/vitess/issues/9686.

Vitess operators can optionally disable the vtctld2 web interface ahead of time by calling the `vtctld` process with the flag `enable_vtctld_ui=false`. For more details on this flag, see https://github.com/vitessio/vitess/pull/9614.
Vitess operators can optionally disable the vtctld2 web interface ahead of time by calling the `vtctld` process with the flag `enable_vtctld_ui=false`. For more details on this flag, see https://github.com/vitessio/vitess/pull/9614.
10 changes: 5 additions & 5 deletions examples/operator/101_initial_cluster.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@ metadata:
name: example
spec:
images:
vtctld: vitess/lite:v13.0.0-rc1
vtgate: vitess/lite:v13.0.0-rc1
vttablet: vitess/lite:v13.0.0-rc1
vtbackup: vitess/lite:v13.0.0-rc1
vtctld: vitess/lite:v13.0.0
vtgate: vitess/lite:v13.0.0
vttablet: vitess/lite:v13.0.0
vtbackup: vitess/lite:v13.0.0
mysqld:
mysql56Compatible: vitess/lite:v13.0.0-rc1
mysql56Compatible: vitess/lite:v13.0.0
mysqldExporter: prom/mysqld-exporter:v0.11.0
cells:
- name: zone1
Expand Down
10 changes: 5 additions & 5 deletions examples/operator/201_customer_tablets.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,12 @@ metadata:
name: example
spec:
images:
vtctld: vitess/lite:v13.0.0-rc1
vtgate: vitess/lite:v13.0.0-rc1
vttablet: vitess/lite:v13.0.0-rc1
vtbackup: vitess/lite:v13.0.0-rc1
vtctld: vitess/lite:v13.0.0
vtgate: vitess/lite:v13.0.0
vttablet: vitess/lite:v13.0.0
vtbackup: vitess/lite:v13.0.0
mysqld:
mysql56Compatible: vitess/lite:v13.0.0-rc1
mysql56Compatible: vitess/lite:v13.0.0
mysqldExporter: prom/mysqld-exporter:v0.11.0
cells:
- name: zone1
Expand Down
10 changes: 5 additions & 5 deletions examples/operator/302_new_shards.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,12 @@ metadata:
name: example
spec:
images:
vtctld: vitess/lite:v13.0.0-rc1
vtgate: vitess/lite:v13.0.0-rc1
vttablet: vitess/lite:v13.0.0-rc1
vtbackup: vitess/lite:v13.0.0-rc1
vtctld: vitess/lite:v13.0.0
vtgate: vitess/lite:v13.0.0
vttablet: vitess/lite:v13.0.0
vtbackup: vitess/lite:v13.0.0
mysqld:
mysql56Compatible: vitess/lite:v13.0.0-rc1
mysql56Compatible: vitess/lite:v13.0.0
mysqldExporter: prom/mysqld-exporter:v0.11.0
cells:
- name: zone1
Expand Down
10 changes: 5 additions & 5 deletions examples/operator/306_down_shard_0.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,12 @@ metadata:
name: example
spec:
images:
vtctld: vitess/lite:v13.0.0-rc1
vtgate: vitess/lite:v13.0.0-rc1
vttablet: vitess/lite:v13.0.0-rc1
vtbackup: vitess/lite:v13.0.0-rc1
vtctld: vitess/lite:v13.0.0
vtgate: vitess/lite:v13.0.0
vttablet: vitess/lite:v13.0.0
vtbackup: vitess/lite:v13.0.0
mysqld:
mysql56Compatible: vitess/lite:v13.0.0-rc1
mysql56Compatible: vitess/lite:v13.0.0
mysqldExporter: prom/mysqld-exporter:v0.11.0
cells:
- name: zone1
Expand Down
2 changes: 1 addition & 1 deletion examples/operator/operator.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5432,7 +5432,7 @@ spec:
fieldPath: metadata.name
- name: OPERATOR_NAME
value: vitess-operator
image: planetscale/vitess-operator:latest
image: planetscale/vitess-operator:v2.6.0
name: vitess-operator
resources:
limits:
Expand Down
12 changes: 6 additions & 6 deletions examples/operator/vtorc_example.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,13 @@ metadata:
name: example
spec:
images:
vtctld: vitess/lite:13.0.0-rc1
vtorc: vitess/lite:13.0.0-rc1
vtgate: vitess/lite:13.0.0-rc1
vttablet: vitess/lite:13.0.0-rc1
vtbackup: vitess/lite:13.0.0-rc1
vtctld: vitess/lite:v13.0.0
vtorc: vitess/lite:v13.0.0
vtgate: vitess/lite:v13.0.0
vttablet: vitess/lite:v13.0.0
vtbackup: vitess/lite:v13.0.0
mysqld:
mysql56Compatible: vitess/lite:13.0.0-rc1
mysql56Compatible: vitess/lite:v13.0.0
mysqldExporter: prom/mysqld-exporter:v0.11.0
cells:
- name: zone1
Expand Down
8 changes: 4 additions & 4 deletions go/vt/servenv/version.go
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ See the License for the specific language governing permissions and
limitations under the License.
*/

// THIS FILE IS AUTO-GENERATED DURING NEW RELEASES
// DO NOT EDIT

package servenv

const versionName = "13.0.0-SNAPSHOT"
// THIS FILE IS AUTO-GENERATED DURING NEW RELEASES BY ./tools/do_releases.sh
// DO NOT EDIT

const versionName = "13.0.0"
2 changes: 1 addition & 1 deletion java/client/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
<parent>
<groupId>io.vitess</groupId>
<artifactId>vitess-parent</artifactId>
<version>13.0.0-SNAPSHOT</version>
<version>13.0.0</version>
</parent>
<artifactId>vitess-client</artifactId>

Expand Down
2 changes: 1 addition & 1 deletion java/example/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
<parent>
<groupId>io.vitess</groupId>
<artifactId>vitess-parent</artifactId>
<version>13.0.0-SNAPSHOT</version>
<version>13.0.0</version>
</parent>
<artifactId>vitess-example</artifactId>

Expand Down
2 changes: 1 addition & 1 deletion java/grpc-client/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
<parent>
<groupId>io.vitess</groupId>
<artifactId>vitess-parent</artifactId>
<version>13.0.0-SNAPSHOT</version>
<version>13.0.0</version>
</parent>
<artifactId>vitess-grpc-client</artifactId>

Expand Down
2 changes: 1 addition & 1 deletion java/jdbc/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
<parent>
<groupId>io.vitess</groupId>
<artifactId>vitess-parent</artifactId>
<version>13.0.0-SNAPSHOT</version>
<version>13.0.0</version>
</parent>
<artifactId>vitess-jdbc</artifactId>

Expand Down
2 changes: 1 addition & 1 deletion java/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@

<groupId>io.vitess</groupId>
<artifactId>vitess-parent</artifactId>
<version>13.0.0-SNAPSHOT</version>
<version>13.0.0</version>
<packaging>pom</packaging>

<name>Vitess Java Client libraries [Parent]</name>
Expand Down

0 comments on commit bc4a960

Please sign in to comment.