Hi,
We ONLY have non-persistent pools, non-replicated, destroyed on logout.
Just curious what are the caveats of turning this feature OFF on our pools.
Having this feature enabled has occasionally disabled the pool when there has been some sort of hiccup. This can be annoying when it's after 5pm, and the service might be down all night, just because 1 machine had a problem provisioning.
If we disable this setting, what might go wrong in our environment? DB gets messed up? Resource allocation goes out of control?
I'm trying to justify that the occasional all night pool downtime might be a better scenario over.... what? At the moment I'm thinking just disable it to have 100% uptime and avoid incidents on a Friday morning 