You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On call to Scale API, every call (in my case with spring-cloud-skipper through Spring Cloud Data Flow & alertmanager) causes a new directories created under the workingDirectoriesRoot
The problem is below, the createWorkingDir is called before checking if deltaCount == 0
So even if there is no scaling needed the directories are created.
With a huge amount of alerts this causes too many empty directories which saturates the files system
Even if i use the tmp dir, the time that the cleaning is done, it creates too many directories
On call to Scale API, every call (in my case with spring-cloud-skipper through Spring Cloud Data Flow & alertmanager) causes a new directories created under the workingDirectoriesRoot
The problem is below, the createWorkingDir is called before checking if deltaCount == 0
So even if there is no scaling needed the directories are created.
With a huge amount of alerts this causes too many empty directories which saturates the files system
Even if i use the tmp dir, the time that the cleaning is done, it creates too many directories
LocalAppDeployer
`
`
I use 2.7.4 but this is the case now
Used with Autoscaling with Prometheus, Alertmanager and SCDF Scale API
I propose
`
The text was updated successfully, but these errors were encountered: