Uploaded image for project: 'Document Management System (closed)'
  1. Document Management System (closed)
  2. MGNLDMS-172

DMS Module Shouldn't Require Cache Module

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Major
    • None
    • 1.2.8
    • None

    Description

      When we ugraded from DMS version 1.2.6 to 1.2.8, a new runtime dependency was introduced: the cache module.

      Since we're using an external cache, we have not previously included the cache module. Unfortunately, since we needed other fixes in DMS 1.2.8, leaving it out was no longer an option for us because of the new dependency.

      When we deployed the updated version of the DMS, some of our backups suddenly started failing. As it turned out, this was due to low memory conditions caused by the cache module's filters. (I suspect the GZIP filter was reading the whole huge XML file into memory and trying to zip it up before sending it along.) Removing the cache and GZIP filters has given us a viable workaround for now.

      While I recognize from the diffs that the DMS module needed to be able to talk to the cache module when it is present to ensure data gets flushed at the appropriate time, it would be better to make that an optional dependency so that if the cache module isn't installed, the DMS module simply doesn't try to flush the cache data and works as it had been previous to the newer releases. This will allow Magnolia users a maximum degree of flexibility when deciding whether to use Magnolia's internal caching or an external solution.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              seanmctex Sean McMains
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: