Self Hosted - MariaDB parameter setting - innodb_table_per_fileSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Customers may experience various database errors in their self-hosted, air-gapped ServiceNow environment running AWS RDS MariaDB. This specific error indicates that the innodb_file_per_table parameter should be set to 0 (OFF) to help minimize database downtime during reboots and failovers. While reviewing the MariaDB 10.6 my.cnf from the self-hosted software site, the customer may notice that this parameter is not explicitly configured, creating uncertainty about the intended default setting. They may be concerned about the operational impact of modifying this parameter and want to understand the risks, tradeoffs, and recommended configuration. Specifically, customers may be requesting guidance on whether this parameter should be disabled and what the best practice is for configuring it within a self-hosted ServiceNow deployment. Recommendations from ServiceNow Self-hosted database operations team: setting innodb_file_per_table = ON (or 1) has the following advantages 1) when tables are dropped or truncated, the underlying disk space is reclaimed, preventing the system tablespace (ibdata1) from growing indefinitely.2) Separate files allow for more efficient I/O and easier management of individual table files and improves the performance.It is better to to set nnodb_file_per_table = OFF if the following are true:1) Tens of thousands of tables2) Very slow storage3) Extremely constrained I/OIf reboot / failover time is a concern : Instead of disabling innodb_file_per_table, focus on these safer optimizations: 1) Tune redo logsinnodb_log_file_sizeinnodb_log_files_in_group2) Ensure frequent checkpoints3) Monitor crash recovery time Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } https://dev.mysql.com/doc/refman/8.4/en/innodb-file-per-table-tablespaces.htmlhttps://mariadb.com/docs/server/server-usage/storage-engines/innodb/innodb-tablespaces/innodb-file-per-table-tablespaces