-
Notifications
You must be signed in to change notification settings - Fork 287
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
TiCDC panicked when handling update events with enable-old-value=false
#6198
Comments
/assign @zhaoxinyu |
/assign @hi-rustin |
/unassign @zhaoxinyu |
You can reproduction with these steps:
CREATE TABLE person2 (
name VARCHAR(255) NOT NULL PRIMARY KEY,
address_info JSON,
city VARCHAR(64) AS (JSON_UNQUOTE(JSON_EXTRACT(address_info, '$.city'))),
KEY (city)
);
INSERT INTO person2 (name, address_info) VALUES ('Morgan', JSON_OBJECT('city', 'Canada'));
#!/bin/bash
for ((i = 1; i <= 1000000000000; i++)); do
mysql --comments --host 127.0.0.1 --port 4000 -u root --password="" <update.sql
done use test;
UPDATE person2 set name='Morgan' where name='test';
UPDATE person2 set name='test' where name='Morgan';
#!/bin/bash
for ((i = 1; i <= 1000000000000; i++)); do
mysql --comments --host 127.0.0.1 --port 4000 -u root --password="" <add.sql
done
|
The reason is: Line 287 in 97f6592
When we execute the |
/close |
@nongfushanquan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-label affects-6.2 |
/found customer |
What did you do?
enable-old-value = false
in changefeed configuration file.What did you expect to see?
TiCDC can properly handle this case and panic does not happen.
What did you see instead?
TiCDC panicked
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):5.4.1
Upstream TiKV version (execute
tikv-server --version
):5.4.1
TiCDC version (execute
cdc version
):5.4.1
The text was updated successfully, but these errors were encountered: