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
|`CommitUnresolved`| N/A | Counter for failure after Prepare. |[#16939](https://github.com/vitessio/vitess/pull/16939)|
120
120
121
121
122
-
The work done [#17727](https://github.com/vitessio/vitess/pull/17727) introduces new metrics for queries. Via this work we have deprecated several vtgate metrics, please see the [Deprecated Metrics](#deprecated-metrics) section. Here is an example on how to use them:
122
+
The work done in [#17727](https://github.com/vitessio/vitess/pull/17727) introduces new metrics for queries. Via this work we have deprecated several vtgate metrics, please see the [Deprecated Metrics](#deprecated-metrics) section. Here is an example on how to use them:
123
123
```
124
124
Query: select t1.a, t2.b from t1 join t2 on t1.id = t2.id
125
125
Shards: 2
@@ -131,8 +131,6 @@ Metrics Published:
131
131
3. QueryExecutionsByTable – {select, t1}, 1 and {select, t2}, 1
132
132
```
133
133
134
-
---
135
-
136
134
#### <aid="new-vttablet-metrics"/>VTTablet
137
135
138
136
| Name | Dimensions | Description | PR |
@@ -170,8 +168,6 @@ The following fields can be dynamically changed -
170
168
171
169
To upgrade to the newer version of the configuration file, first switch to using the flags in your current deployment before upgrading. Then you can switch to using the configuration file in the newer release.
The Viper configuration keys for the following flags has been changed to match their flag names. Previously they had a discovery prefix instead of it being part of the name.
@@ -199,8 +195,6 @@ This is useful in scenarios where the disk is stalled and the primary vttablet i
199
195
To opt into this feature, `--enable-primary-disk-stalled-recovery` flag has to be specified on VTOrc, and `--disk-write-dir` flag has to be specified on the vttablets.
200
196
`--disk-write-interval` and `--disk-write-timeout` flags can be used to configure the polling interval and timeout respectively.
201
197
202
-
---
203
-
204
198
#### <aid="key-range-vtorc"/>KeyRanges in `--clusters_to_watch`</a>
205
199
VTOrc now supports specifying keyranges in the `--clusters_to_watch` flag. This means that there is no need to restart a VTOrc instance with a different flag value when you reshard a keyspace.
206
200
@@ -234,8 +228,6 @@ VTGate also advertises MySQL version `8.0.40` by default instead of `8.0.30` if
234
228
>
235
229
> This is the last time this will be needed in the `8.0.x` series, as starting with MySQL `8.0.35` it is possible to upgrade and downgrade between `8.0.x` versions without needing to run `innodb_fast_shutdown=0`.
236
230
237
-
---
238
-
239
231
#### <aid="debian-bookworm"/>Docker `vitess/lite` images with Debian Bookworm</a>
240
232
241
233
The base system now uses Debian Bookworm instead of Debian Bullseye for the `vitess/lite` images. This change was brought by [#17552](https://github.com/vitessio/vitess/pull/17552).
@@ -250,17 +242,13 @@ In [#7345](https://github.com/vitessio/vitess/pull/17345) we added support for [
250
242
251
243
If you are using MySQL 8.0 or later and using JSON columns, you can now enable this MySQL feature across your Vitess cluster(s) to lower the disk space needed for binary logs and improve the CPU and memory usage in both `mysqld` (standard intrashard MySQL replication) and `vttablet` ([VReplication](https://vitess.io/docs/reference/vreplication/vreplication/)) without losing any capabilities or features.
In [#17408](https://github.com/vitessio/vitess/pull/17408) and [#17409](https://github.com/vitessio/vitess/pull/17409), we added the ability to use `LAST_INSERT_ID(x)` in Vitess directly at vtgate. This improvement allows certain queries—like `SELECT last_insert_id(123);` or `SELECT last_insert_id(count(*)) ...`—to be handled without relying on MySQL for the final value.
258
248
259
249
**Limitations**:
260
250
- When using `LAST_INSERT_ID(x)` in ordered queries (e.g., `SELECT last_insert_id(col) FROM table ORDER BY foo`), MySQL sets the session’s last-insert-id value according to the *last row returned*. Vitess does not guarantee the same behavior.
261
251
262
-
---
263
-
264
252
#### <aid="max-idle-connections"/>Maximum Idle Connections in the Pool</a>
265
253
266
254
In [#17443](https://github.com/vitessio/vitess/pull/17443) we introduced a new configurable max-idle-count parameter for connection pools. This allows you to specify the maximum number of idle connections retained in each connection pool to optimize performance and resource efficiency.
@@ -272,8 +260,6 @@ You can control idle connection retention for the query server’s query pool, s
272
260
273
261
This feature ensures that, during traffic spikes, idle connections are available for faster responses, while minimizing overhead in low-traffic periods by limiting the number of idle connections retained. It helps strike a balance between performance, efficiency, and cost.
274
262
275
-
---
276
-
277
263
#### <aid="query-logs"/>Filtering Query logs on Error</a>
278
264
279
265
The `querylog-mode` setting can be configured to `error` to log only queries that result in errors. This option is supported in both VTGate and VTTablet.
@@ -287,6 +273,8 @@ Prepared statements now benefit from Deferred Optimization, enabling parameter-a
287
273
Initially, a baseline plan is created at prepare-time, and on first execution, a more efficient parameter-optimized plan is generated.
288
274
Subsequent executions dynamically switch between these plans based on input values, improving query performance while ensuring correctness.
289
275
276
+
---
277
+
290
278
### <aid="rpc-changes"/>RPC Changes</a>
291
279
292
280
These are the RPC changes made in this release -
@@ -358,8 +346,6 @@ While the flag will continue to accept float values (interpreted as seconds) for
358
346
359
347
-`--consolidator-query-waiter-cap` flag to set the maximum number of clients allowed to wait on the consolidator. The default value is set to 0 for unlimited wait. Users can adjust this value based on the performance of VTTablet to avoid excessive memory usage and the risk of being OOMKilled, particularly in Kubernetes deployments.
360
348
361
-
---
362
-
363
349
#### <aid="reloading-vttablet-acl"/>ACL enforcement and reloading</a>
364
350
365
351
When a tablet is started with `--enforce-tableacl-config` it will exit with an error if the contents of the file are not valid. After the changes made in [#17485](https://github.com/vitessio/vitess/pull/17485) the tablet will no longer exit when reloading the contents of the file after receiving a SIGHUP. When the file contents are invalid on reload the tablet will now log an error and the active in-memory ACLs remain in effect.
0 commit comments