Anonymous | Login | Signup for a new account | 03-29-2024 00:46 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | 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 | ||||||
Status | closed | Product Version | 4.0.62 | ||||||
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? |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
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. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |