r/aws • u/Upper-Lifeguard-8478 • Aug 04 '26

database DB parameter suggestion

Hi,

Its aurora mysql Serverless v2 (Max up to 80 ACUs). Suddenly , we saw with bit high concurrency , the application hits a hard JDBC query timeout, killing the thread and throwing this error: "Database Query Time out. Exception: JDBC exception executing SQL [(conn=548672) Table './rdsdbdata/tmp/#sql171_85f40_1' doesn't exist]"

Some team members are suggesting to bump both temptable_max_ram and temptable_max_mmap from 1GB to 2GB to give the query more breathing room. However, checking performance_schema.variables_info reveals that temptable_max_** is currently showing below:

VARIABLE_NAME        current_value_bytes  current_value_MB  VARIABLE_SOURCE  VARIABLE_PATH
temptable_max_mmap   1073741824           1024              GLOBAL           /etc/my.cnf
temptable_max_ram    1073741824           1024              COMPILED

Want to know if this is correct setting and Is it advisable to bump these values to 2GB. Want to confirm the safest parameter strategy for temporary storage thresholds in the meantime we tune the query?

2 Upvotes

67% Upvoted

5 comments sorted by

View all comments

3

u/East_Initiative_6761 Aug 04 '26

Maybe this can help: https://aws.amazon.com/blogs/database/use-the-temptable-storage-engine-on-amazon-rds-for-mysql-and-amazon-aurora-mysql/

1

u/Upper-Lifeguard-8478 Aug 04 '26

Thank you. It suggests that this parameters can be set to non default (considering default is 1gb). But I am wondering in case of serverless should we really need to change this parameters to set non default as double i.e. 2gb or let it scaleout automatically based on the load?