Hi Benjamin, This bug came in yesterday with the same error around Aria (the only place the error can be produced), but there's shared aspects of Aria/S3 that might be relevant.
https://jira.mariadb.org/browse/MDEV-39668 A linked bug report with your table structure particulary data types, index, (but replace column/table/index names if desired) and sequence of SQL statements to hit this would be useful. On Mon, 18 May 2026 at 07:21, Benjamin Lin via discuss <[email protected]> wrote: > > Hi experts, > > I recently started using S3 engine to archive large table, it is working > for small table but for table with 20 million rows, I encounter this error > while ALTER table to S3 engine. > > ERROR 1034 (HY000): Key 3 - Found too many records; Can't continue > > Is there something you aware of or does anyone know any solution? I have > added following parameters but no help. > > key_buffer_size=268435456 > sort_buffer_size=268435456 > max_allowed_packet=33554432 > max_heap_table_size=67108864 > tmp_table_size=67108864 > table_open_cache=131072 > thread_cache_size=32 > aria_sort_buffer_size=268435456 > aria_log_file_size=2147483648 > aria_pagecache_buffer_size=2147483648 > _______________________________________________ > discuss mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
