0006274: deploying and undeploying the same WAR file bloats up resin-data

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0006274

[Resin]

minor

always

08-05-19 11:23

08-23-19 13:59

Reporter

nam

View Status

public

Assigned To

ferg

Priority

normal

Resolution

no change required

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

Product Version

4.0.62

Product Build

Summary

0006274: deploying and undeploying the same WAR file bloats up resin-data

Description

(rep by M. Shimomura)

When we deploy/undeploy a war file repeatedly, the resin-data size will
bloat.

The resin-data is managed with git.
Is there the upper limit of resin-data size?
Is it correct to recognize the upper limit is an available disk size?
I consider the resin-data manages the difference of war files.
Is the difference managed until some point of the past generation? Or is it managed all generations?

Steps To Reproduce

Additional Information

Attached Files

Relationships

Notes
(0006915) ferg 08-23-19 13:59	The gc() time for the resin-data git is 60 minutes. If you redeploy a .war continuously before the timeout, the resin-data will bloat.

Issue History
Date Modified	Username	Field	Change
08-05-19 11:23	nam	New Issue
08-23-19 13:59	ferg	Note Added: 0006915
08-23-19 13:59	ferg	Assigned To	=> ferg
08-23-19 13:59	ferg	Status	new => closed
08-23-19 13:59	ferg	Resolution	open => no change required

Mantis 1.0.0rc3[^]

29 total queries executed.
26 unique queries executed.