Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-25677

[GSS](7.4.z) managed deployment in content repository duplicated in tmp/vfs/temp directory

    XMLWordPrintable

Details

    Description

      It looks like we have are duplicating deployments in the content repository when VFS mounts them.

      deploy a test app with jboss-cli.sh

      deploy helloWorld.ear

      The deployment gets uploaded into the content repository:

      $JBOSS_HOME/standalone/data/content/63/30e18e648eba2242f16bbe11a8eea0dcdb8a1d/content 
      ls standalone/tmp/helloWorld.ear.helloWorld.war/
[empty] 
      ls -r standalone/tmp/vfs/deployment/deployment9a5e4ddb6e3ea138/helloWorld*
standalone/tmp/vfs/deployment/deployment9a5e4ddb6e3ea138/helloWorld.war-20dcb94b1af44bbe:
index.jsp com WEB-INF META-INF
standalone/tmp/vfs/deployment/deployment9a5e4ddb6e3ea138/helloWorld-standalone-client.jar-863ffeb82cec36f5:helloWorld-standalone-client.jar contents
standalone/tmp/vfs/deployment/deployment9a5e4ddb6e3ea138/helloWorld-ejb.jar-2f9faedea31298d7:helloWorld-ejb.jar contents
standalone/tmp/vfs/deployment/deployment9a5e4ddb6e3ea138/helloWorld-api.jar-3a27e75ba1533497:
helloWorld-api.jar contents

       

      ls standalone/tmp/vfs/temp/temp6fb91ce22bbbf480/content-be5e0d197ed4d21f/contents/
[empty]

      Doing a shasum, I can see the standalone/data/content... file has the same hash as the VFS temp file tmp/vfs/temp/temp6fb91ce22bbbf480... , so this is a copy of the deployment, which is still compressed, thus it is doubling the disk space usage for this application.

      shasum standalone/data/content/63/30e18e648eba2242f16bbe11a8eea0dcdb8a1d/content standalone/tmp/vfs/temp/temp6fb91ce22bbbf480/content-be5e0d197ed4d21f/content
6330e18e648eba2242f16bbe11a8eea0dcdb8a1d  standalone/data/content/63/30e18e648eba2242f16bbe11a8eea0dcdb8a1d/content
6330e18e648eba2242f16bbe11a8eea0dcdb8a1d  standalone/tmp/vfs/temp/temp6fb91ce22bbbf480/content-be5e0d197ed4d21f/content

      The files / dirs under tmp/vfs/deployment/deployment9a5e4ddb6e3ea138 are the decompressed contents of application.

      Since we have to decompress, we will have 2 x file size (the content and the extracted dir), but it looks like we 3 x , with this extra content that looks like we could fix.

      Attachments

        Issue Links

          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-25879 [GSS](8.0.z) managed deployment in content repository duplicated in tmp/vfs/temp directory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-25881 (7.4.z) Do not duplicate managed deployment in content repository in tmp/vfs/temp directory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-engineering-lgao Lin Gao
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: