|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 6274 | minor | always | 08-05-19 11:23 | 08-23-19 13:59 | |
|
|
|||||
| Reporter: | nam | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.62 | ||
| Product Build: | Resolution: | no change required | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||