-
Per MySQL `8.2.0` [release notes](https://dev.mysql.com/doc/relnotes/mysql/8.2/en/news-8-2-0.html):
> Incompatible Change: The WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS() SQL function, deprecated in MySQL …
-
### Overview of the Issue
I have been testing the new `foreignKeyMode=managed` and in that context for the first time created foreign key constraints with Vitess, and then realized that our standar…
-
## Motivation
Let's explore a way to enhance the performance of this implementation 🤔
-
### Overview of the Issue
VReplication workflow metadata is stored in each target shard that participates in the workflow, As a result, all workflow commands that show status or change the state of…
-
### Overview of the Issue
We ran into an issue where promoting the replica to primary via PlannedReparent succeeded. However, the new primary had actually not caught up to the position of the old p…
-
### Overview of the Issue
When deploying a Vitess keyspace with 128 shards and employing a federated toposerver distributed amongst different geographical regions, we have found that calls to vtctl…
-
#### Overview of the Issue
The docs say default is **MULTI**:
> The atomicity policy is controlled by the transaction_mode flag. The default value is multi, and will set it in multi-database mod…
-
Reported by @harshit-gangal , for example in https://github.com/vitessio/vitess/actions/runs/7299836104/job/19894003119?pr=14851, we see a race condition in the table throttler's unit tests, while ite…
-
### Overview of the Issue
vtctlclient failed to run backupShard command when:
**There is a bad replica in the shard [ chance rate: 1/(n-1) where n equals to number of vttablets in a shard]**
Wh…
-
Related to #2349
I receive a
> Error 1062 (HY000): duplicate primary key given: [2]
error when doing these queries in memory mode
```sql
CREATE TABLE table1 (
id int NOT NULL AUTO_INCREME…