Issue Feature Closed

#33445Handle unavailable storages

Tom Ruether 01/25/12, 19:42 updated 03/24/20, 11:15

Description

We need an error handling for “Storage is not reachable”

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 14

  1. Andreas Wolf commented 02/02/12, 16:30

    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.

  2. Andreas Wolf commented and changed tracker Task Feature subject Filelist: Error handling for Storage is not reachable Handle not available status New Accepted 04/12/12, 11:59

    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.

  3. Andreas Wolf changed subject Handle not available Handle unavailable storages 04/13/12, 14:11

  4. Ingmar Schlecht changed target version 04/30/12, 16:16

  5. Steffen Ritter changed target version 09/03/12, 11:05

  6. Alexander Opitz changed target version 01/14/14, 15:53

  7. Alexander Opitz changed project id 01/14/14, 15:53

  8. Alexander Opitz changed category TYPO3 Version 6.0 01/14/14, 15:54

  9. Ingo Schmitt commented and changed status Accepted Needs Feedback 01/18/15, 22:07

    Hey Tom,

    does this issue still exist in 6.2.x

  10. Tom Ruether commented 02/09/15, 21:46

    yes it still exists

  11. Alexander Opitz changed status Needs Feedback New 06/18/15, 10:54

  12. Sascha Egerer commented 08/24/16, 09:27

    Andreas Wolf wrote:
    > 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.

    IMO if a storage points to a non existing folder that does not mean that the storage is invalid. If the local storage is a mounted folder and that becomes unavailable for a short time that must not mean that the storage is invalid. Thats the same case as for remote storages.
    Maybe we should add an option to the storage to automatically reactivate it if its back?

  13. Susanne Moog commented and changed status New Needs Feedback 03/07/19, 15:34

    Can someone involved in the topic write a bit more about what needs to be done here and which cases need to be considered? As far as I can see, we currently have the “is Online” check for storages, which is automatically checked and set to false if a storage is offline. What else needs to be done?

  14. Susanne Moog commented and changed status Needs Feedback Closed 03/24/20, 11:15

    No feedback and clarification for a long time, closing the issue now.