You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 10, 2023. It is now read-only.
The Stash connection pool timeout (default is 10 mins) is greater than the mysql cookbook wait_timeout (default 3 mins).
I've updated my node attributes to this:
node['mysql']['tunable']['wait_timeout'] = '720'
Now Stash reaps connections before mysql has the chance and the errors haven't reappeared for the last 24 hours.
Should we include a setting in stash-config.properties for db.pool.idle.testInterval so that we can override the stash default and default it to node['mysql']['tunable']['wait_timeout'] or 120 seconds where mysql isn't on the box?
I've installed a monolithic Stash stack on a single Centos 6.4 x64 virtual machine.
I get the Oops 500 page appearing randomly and I'm pretty sure I'm bumping into this bug.
https://confluence.atlassian.com/display/STASHKB/Connection+Timeout+with+MySQL+Database
The Stash connection pool timeout (default is 10 mins) is greater than the mysql cookbook wait_timeout (default 3 mins).
I've updated my node attributes to this:
Now Stash reaps connections before mysql has the chance and the errors haven't reappeared for the last 24 hours.
Should we include a setting in stash-config.properties for db.pool.idle.testInterval so that we can override the stash default and default it to node['mysql']['tunable']['wait_timeout'] or 120 seconds where mysql isn't on the box?