Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
Description
origin/10.6 af418bb9ef7e422282dc976640409a6af8fcd58c 2021-04-19T14:04:02+10:00
|
|
Scenario:
|
1. Start the server, create one table and fill it with 100 rows.
|
2. Session 1 runs in a loop some update like
|
UPDATE table100_innodb_int_autoinc SET `col_varchar_255_ucs2_key` = CONVERT( 'degsotrsfannidwyvkuvlkeslrryhpkeevqmbksdrzadzpyisznignsytihyjixyalxfxpnafjwzgnkbbayklurufrsajtzohanbuvcfyykvtmesobixwipkoihhqykvoejckythjnjshxgohmecmklxryubdexjgxehdiqqui' USING ASCII )
|
Session 2 runs in a loop
|
CHECK TABLE table100_innodb_int_autoinc EXTENDED
|
After short time the CHECK TABLE harvests a
|
test.table100_innodb_int_autoinc check Warning InnoDB: Index 'col_varchar_255_ucs2_key' contains 98 entries, should be 100.
|
|
sdp:/data/Results/1618846463/TBR-36/dev/shm/vardir/1618846463/4/1/rr
|
|
Attachments
Issue Links
- causes
-
MDEV-25758 InnoDB spatial indexes miss large geometry fields after MDEV-25459
-
- Closed
-
- relates to
-
MDEV-24402 CHECK TABLE may miss some cases of index inconsistencies
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | TBR-36.zz [ 57332 ] |
Attachment | TBR-36_micro.yy [ 57333 ] |
Attachment | simp_many_indexes.cfg [ 57334 ] |
Assignee | Matthias Leich [ mleich ] | Marko Mäkelä [ marko ] |
Description |
{noformat} origin/10.6 af418bb9ef7e422282dc976640409a6af8fcd58c 2021-04-19T14:04:02+10:00 Scenario: 1. Start the server, create one table and fill it with 100 rows. 2. Session 1 runs in a loop some update like UPDATE table100_innodb_int_autoinc SET `col_varchar_255_ucs2_key` = CONVERT( 'degsotrsfannidwyvkuvlkeslrryhpkeevqmbksdrzadzpyisznignsytihyjixyalxfxpnafjwzgnkbbayklurufrsajtzohanbuvcfyykvtmesobixwipkoihhqykvoejckythjnjshxgohmecmklxryubdexjgxehdiqqui' USING ASCII ) Session 2 runs in a loop CHECK TABLE table100_innodb_int_autoinc EXTENDED After short time the CHECK TABLE harvests a test.table100_innodb_int_autoinc check Warning InnoDB: Index 'col_varchar_255_ucs2_key' contains 98 entries, should be 100. sdp:/data/Results/1618846463/TBR-36/dev/shm/vardir/1618846463/4/1/rr {noformat} |
{noformat}
origin/10.6 af418bb9ef7e422282dc976640409a6af8fcd58c 2021-04-19T14:04:02+10:00 Scenario: 1. Start the server, create one table and fill it with 100 rows. 2. Session 1 runs in a loop some update like UPDATE table100_innodb_int_autoinc SET `col_varchar_255_ucs2_key` = CONVERT( 'degsotrsfannidwyvkuvlkeslrryhpkeevqmbksdrzadzpyisznignsytihyjixyalxfxpnafjwzgnkbbayklurufrsajtzohanbuvcfyykvtmesobixwipkoihhqykvoejckythjnjshxgohmecmklxryubdexjgxehdiqqui' USING ASCII ) Session 2 runs in a loop CHECK TABLE table100_innodb_int_autoinc EXTENDED After short time the CHECK TABLE harvests a test.table100_innodb_int_autoinc check Warning InnoDB: Index 'col_varchar_255_ucs2_key' contains 98 entries, should be 100. sdp:/data/Results/1618846463/TBR-36/dev/shm/vardir/1618846463/4/1/rr {noformat} |
Summary | Draft: Corrupt index caused by some UPDATE+CHECK TABLE | Corrupt index caused by some concurrent UPDATE+CHECK TABLE |
Status | Open [ 1 ] | In Progress [ 3 ] |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Affects Version/s | 10.2 [ 14601 ] | |
Affects Version/s | 10.3 [ 22126 ] | |
Affects Version/s | 10.4 [ 22408 ] | |
Affects Version/s | 10.5 [ 23123 ] | |
Affects Version/s | 10.6 [ 24028 ] | |
Affects Version/s | 10.6.0 [ 24431 ] | |
Labels | rr-profile | rr-profile-analyzed upstream |
Summary | Corrupt index caused by some concurrent UPDATE+CHECK TABLE | MVCC read from index on CHAR or VARCHAR wrongly omits rows |
Fix Version/s | 10.2.38 [ 25207 ] | |
Fix Version/s | 10.3.29 [ 25206 ] | |
Fix Version/s | 10.4.19 [ 25205 ] | |
Fix Version/s | 10.5.10 [ 25204 ] | |
Fix Version/s | 10.6.1 [ 24437 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Link |
This issue relates to |
Link |
This issue causes |
Labels | rr-profile-analyzed upstream | ServiceNow rr-profile-analyzed upstream |
Labels | ServiceNow rr-profile-analyzed upstream | 76qDvLB8Gju6Hs7nk3VY3EX42G795W5z rr-profile-analyzed upstream |
Labels | 76qDvLB8Gju6Hs7nk3VY3EX42G795W5z rr-profile-analyzed upstream | rr-profile-analyzed upstream |
Workflow | MariaDB v3 [ 121179 ] | MariaDB v4 [ 159166 ] |
Zendesk Related Tickets | 201658 | |
Zendesk active tickets | 201658 |