View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007878 | Taler | sandcastle (containerized demo deployment) | public | 2023-07-03 14:15 | 2023-09-23 15:09 |
| Reporter | Florian Dold | Assigned To | javier.sepulveda | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0007878: sandcastle should limit max process run-time | ||||
| Description | Ideally systemd should be used for that. We need to stop and restart the services regularly, otherwise postgres will take up too much memory. | ||||
| Tags | No tags attached. | ||||
|
|
Fixed by Florian, by inserting on the bash (images/exchange/scripts/startup.sh) file which is executed, right after the container is put into operation (docker run) a little sleep process, which fails every hour. After that the docker-compose (exchange) restart-always directive, will take care of starting the container again and again. In this way we close the postgres connection every hour, and therefore avoid the accumulation of memory usage. I have checked the performance of this change and works okay, having currently as always 31% of memory in use. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-07-03 14:15 | Florian Dold | New Issue | |
| 2023-07-03 14:15 | Florian Dold | Assigned To | => javier.sepulveda |
| 2023-07-03 14:15 | Florian Dold | Status | new => assigned |
| 2023-07-11 15:58 | javier.sepulveda | Status | assigned => resolved |
| 2023-07-11 15:58 | javier.sepulveda | Resolution | open => fixed |
| 2023-07-11 15:58 | javier.sepulveda | Note Added: 0020351 | |
| 2023-07-13 23:55 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-07-13 23:55 | Christian Grothoff | Target Version | 0.9.4 => 0.9.3 |
| 2023-09-23 15:09 | Christian Grothoff | Status | resolved => closed |
