Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-38780

rename method in BaseContentService is actually copy/remove

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.6.x, 2.7.x, 2.8.x, 2.9.x
    • Fix Version/s: 2.9.x
    • Component/s: Kernel
    • Labels:
      None
    • Previous Issue Keys:
      KNL-817

      Description

      The "rename" method in BaseContentService does not actually rename resources or collections. It copies them and then removes the old copy. This may work all right for relatively small files and collections, but for large files and collections this can create I/O throughput issues as well as potential risks in multi-volume storage setups, when all that is needed is to update a few fields in existing database records. We've recently been experiencing performance problems on application servers struggling to keep up with multiple large "rename" activities on directories full of multi-gigabyte files, which quickly saturates the NFS I/O throughput available on that application server.

        Gliffy Diagrams

          Zeplin

            Attachments

            1. KNL-817_1.patch .txt
              22 kB
            2. KNL-817_2.patch.txt
              2 kB
            3. KNL-817_3.patch.txt
              3 kB
            4. KNL-817_4.patch.txt
              3 kB
            5. stack filepath.PNG
              stack filepath.PNG
              39 kB

              Issue Links

                Activity

                  People

                  Assignee:
                  aaronz Aaron Zeckoski (Inactive)
                  Reporter:
                  daveadams David Adams
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration