Feature #33445
Handle unavailable storages
| Status: | Accepted | Start date: | 2012-01-25 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 6.0 beta 2 | |||
| Votes: | 0 |
Description
We need an error handling for "Storage is not reachable"
Related issues
| duplicated by File Abstraction Layer - Feature #34013: Handle unavailable storages | Resolved | 2012-02-11 |
History
Updated by Andreas Wolf over 1 year ago
This is especially important for remote storages, as these might easily become unavailable (network problems, server downtime etc).
The foremost problem is that we have to store this state internally, otherwise we always have to wait for a network timeout on each access (which might be many even within one request). We should mark a storage as unavailable for a certain amount of time in case of a timeout - but this should be handled on a per-driver level.
Updated by Andreas Wolf about 1 year ago
- Tracker changed from Task to Feature
- Subject changed from Filelist: Error handling for Storage is not reachable to Handle not available
- Status changed from New to Accepted
The filelist (and all other parts of the UI) should also react accordingly.
I agreed with Benni to have this in two flavors: If the configuration of a storage is invalid (e.g. it points to a non-existing folder), we will permanently disable the storage and an admin has to reactivate it (could be by saving the TCA record).
If a storage is temporarily unavailable (e.g. because of network errors), we should disable it for some minutes (on a per-user base in the backend) and then automatically check again. For the frontend we want to have as little impact as possible - which means we should e.g. not throw exceptions for inaccessible storages there.
Updated by Andreas Wolf about 1 year ago
- Subject changed from Handle not available to Handle unavailable storages
Updated by Ingmar Schlecht about 1 year ago
- Target version set to 6.0 beta1
Updated by Steffen Ritter 10 months ago
- Target version changed from 6.0 beta1 to 6.0 beta 2