-
Enhancement
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
-
-
-
-
+
-
-
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.
- blocks
-
JBEAP-25879 [GSS](8.0.z) managed deployment in content repository duplicated in tmp/vfs/temp directory
- Closed
- clones
-
WFCORE-6524 Do not duplicate managed deployment in content repository in tmp/vfs/temp directory
- Resolved
- is cloned by
-
JBEAP-25881 (7.4.z) Do not duplicate managed deployment in content repository in tmp/vfs/temp directory
- Closed
- is incorporated by
-
JBEAP-25379 (8.0.z) Upgrade WildFly Core from 21.0.5.Final-redhat-00001 to 21.0.6.Final-redhat-00001
- Closed