[MAGNOLIA-6905] Removing a node with a lot of children is nearly impossible Created: 21/Dec/16  Updated: 22/Dec/16

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Adi De Masi Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

We have a folder with roughly 120 nodes. Each of this node has roughly 2500 subnodes.

Deleting the whole folder is impossible from the backend. It leads to high cpu-usage and crashes with out-of-memory.

We already contacted support and magnolia-forum and got suggestion that we need to delete it in batches of 500 nodes or so. This is of course not a good solution, as it adds unnecessary complexity and is error prone for something that should be a basic feature of every database.


Generated at Mon Feb 12 04:18:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.