tidb panic: indexHashJoinInnerWorker.doJoinUnordered failed while execute with prepare

[aytrack]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

cluster_index.UK_MU15544.000000000.txt

source cluster_index.UK_MU15544.000000000.txt
prepare stmt from 'select/*+ inl_hash_join(t1) */ count(*)  from UK_MU15544 t1 join UK_MU15544 t2 on t1.col1 = t2.col1 where t1. col1 + 10 > ? + 10 or t2. col1 > some (select col1 from UK_MU15544);';
set @a="1E847";
execute stmt using @a;
select/*+ inl_hash_join(t1) */ count(*) from UK_MU15544 t1 join UK_MU15544 t2 on t1.col1 = t2.col1 where t1. col1 + 10 > "1E847" + 10 or t2. col1 > some (select col1 from UK_MU15544);

2. What did you expect to see? (Required)

mysql > prepare stmt from 'select/*+ inl_hash_join(t1) */ count(*) from UK_MU15544 t1 join UK_MU15544 t2 on t1.col1 = t2.col1 where t1. col1 + 10 > ? + 10 or t2. col1 > some (select col1 from UK_MU15544);';
Query OK, 0 rows affected
Time: 0.038s
mysql > set @a="1E847";
Query OK, 0 rows affected
Time: 0.038s
mysql > execute stmt using @a;
+----------+
| count(*) |
+----------+
| 101      |
+----------+

3. What did you see instead (Required)

mysql > prepare stmt from 'select/*+ inl_hash_join(t1) */ count(*) from UK_MU15544 t1 join UK_MU15544 t2 on t1.col1 = t2.col1 where t1. col1 + 10 > ? + 10 or t2. col1 > some (select col1 from UK_MU15544);';
Query OK, 0 rows affected
Time: 0.038s
mysql > set @a="1E847";
Query OK, 0 rows affected
Time: 0.038s
mysql > execute stmt using @a;
(1105, 'indexHashJoinInnerWorker.doJoinUnordered failed')

4. What is your TiDB version? (Required)

release-5.0: e2740f5

[wshwsh12]

/assign @XuHuaiyu

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

[ChenPeng2013]

Release-5.1 still don't fix this issue

Release Version: v5.1.0-66-g797bddd25
Edition: Community
Git Commit Hash: 797bddd25310ed42f0791c8eccb78be8cce2f502
Git Branch: release-5.1
UTC Build Time: 2021-07-29 03:36:57
GoVersion: go1.16.5
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false

[XuHuaiyu]

Cherry-pick to release-5.0 and release-5.1 already.

[github-actions]

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.