Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-4419

Memcached should not be used for persistent data

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2013-03-11
    • Component/s: Release editor
    • Labels:
      None

      Description

      AS A sysadmin
      I WANT to be able to restart the memcached instances without breaking the user experience
      SO THAT I don't have to co-ordinate with the user base to perform basic sysadmin

      GIVEN a service that uses memcached
      WHEN memcached entirely disappears
      THEN other services should still function (but perhaps be slower)

      GIVEN a service that uses memcached
      WHEN memcached data is lost (e.g. due to a restart, or cache full)
      THEN other services should still function (but perhaps be slower)

      It should be possible to lose memcached at any time, and the effect to the user should be negligible. I believe the release editor violates this principal, by storing session data in memcached.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                warp Kuno Woudt
                Reporter:
                djce Dave Evans
              • Votes:
                1 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  2013-03-11