Skip to content

Validate behaviour of DirectFileStore in the presence of existing files #109

Description

@Sinjo

We (GoCardless) run our services in containers, which means a clean file system every time we boot the app.

We should look at what the behaviour is like for people who have file systems that persist between versions of the app. If so, we should look at what mitigations we can implement to make DirectFileStore work by default.

Any edge-cases should be added to the DirectFileStore’s docs.

Activity

  1. added this to the multi-process milestone on May 1, 2019
  2. self-assigned this
    on Jun 17, 2019
  3. dmagliola commented on Jul 11, 2019

    @dmagliola
    Contributor

    See Lawrence's comment on file locking as a potential way of knowing which files are still owned by living processes.

    #143 (comment)

    Valid warning from Brian that it may not work in all OSes, plus we can't just delete "some" files, but this may be an idea to start building a solution around

  4. removed their assignment
    on Jul 11, 2019
  5. removed this from the v0.10.0 milestone on Aug 19, 2019
  6. Sinjo commented on Aug 19, 2019

    @Sinjo
    MemberAuthor

    Similar to #143, and for the same reasons outlined in this comment, I'm taking this out of the v0.10.0 milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions