Implemented
0
SQLite database file never shrinks after execution pruning/deletion — disk fills up despite pruning being enabled
Source: n8n-io/n8n#37926 · opened by @welectronic
Describe the problem/error/question database.sqlite grows without bound and disk space is never reclaimed, even with execution pruning enabled (maxAge/maxCount configured, confirmed active per Debug Info below) and even after manually deleting old executions from the Executions UI. Timeline of what happened on our self-hosted instance: • A workflow run processing ~14,000 items (each creating several sub-executions via Execute Workflow) generated a very large volume of execution data over a few hours. • The server's disk (120GB) filled completely, and the n8n container became unresponsive / the UI became inaccessible. • We resized the underlying disk volume to 160GB and grew the filesystem, restoring access to the UI. • From the UI, we deleted executions down to only 17 remaining in execution_entity (confirmed via SELECT COUNT(*) FROM execution_entity; directly on the SQLite file → returned 17). • Despite that, database.sqlite on disk was still 101G…
No pledges yet. Be the first to back this.
Comments
Similar requests
When custom Ollama credentials are configured and the endpoint is inaccessible, the '/home/chat' page keeps displaying a loading status when selecting a model, resulting in a timeout for the API endpoint /rest/chat/models.
0 votes · 0 comments
MCP tool calls fail in queue mode: `Tool node "<name>" does not have supplyData method` + `Worker tool execution timeout`
0 votes · 0 comments
Copper 'Get many companies' node does not paginate Copper companies properly.
0 votes · 0 comments
AI Agent: return tool-schema validation failures to the model as recoverable errors instead of terminating the execution
0 votes · 0 comments
Cannot connect local mongo db with 'MongoDB Chat Memory' node
0 votes · 0 comments
No comments yet.