@@ -552,6 +552,18 @@ Change this to a higher value if you notice that regular usage consumes all or c
See [MB_APPLICATION_DB_MAX_CONNECTION_POOL_SIZE](#mb_application_db_max_connection_pool_size) for setting maximum connections to the Metabase application database.
Metabase's query processor will normally kill connections when their queries time out, but in practice some connections can be severed and go undetected by Metabase, staying alive even after a query returns or times out. This environment variable tells Metabase how long to wait before killing connections if no response is received from the connection.
This variable affects connection that are severed and undetected by Metabase (i.e. Metabase never receives connection closed signal and is treating an inactive connection as active). It is most often adjusted when connecting to unreliable or dynamic connections that are behind a SSH tunnel where the connection to the SSH tunnel host may stay active even after the connection from the SSH tunnel host to the Database is severed.
If left blank, the default production value for `metabase.query-processor.query-timeout-ms` is used which is 1,200,000 ms (i.e. 1,200 seconds or 20 minutes).
