Allow DataStore to auto disable on connection failure

you’re off the mark here… GeoServer tries to connect to the stores, and disables them on failure, only during startup, and only if the global setting about skipping misconfigured layers is disabled (otherwise it does not even try, making startup so much faster).

Even when enabled, it’s not useful if a connection issue happens later, and the connection fails to timeout and throw an exception quickly. We have experienced tens of minutes of wait on both WMS/WMTS cascading and Oracle stores, due to network issues. When this happens, we don’t want GeoServer to try again and then again and so on, blocking more request threads, and never getting back to a sane state. With the flag turned on, after the first time out the store is disabled and the server resumes operations.

The flag is opt-in, the behavior by default is not changing, it can be used by those experiencing problems like the ones above, if they choose to do so.

I see the PR was merged; okay then…

Setting enabled flag in the catalog is disabling the datastore :)

Issue with setting enabled false and storing that is in the catalog is … when a database that was offline returns to service the WFS does not resume serving those layers.

The enabled status in the UI also has a “warning” state when a datastore is enabled but not available. If this is not meeting your needs perhaps it could be improved?

My apologies for late response on your comment Jody.

The functionality aims at setting to false the enable flag and persist the modification in the catalog in case the new option is flagged. The resourcepool is not disabling any store when the connection fails.

I thought they already did this? Perhaps only during initial connection attempt?

So what is the user experience you are trying for here …