Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to delete large entities #5803

Closed
MalwareCantFly opened this issue Feb 2, 2024 · 0 comments · Fixed by #5920
Closed

Unable to delete large entities #5803

MalwareCantFly opened this issue Feb 2, 2024 · 0 comments · Fixed by #5920
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@MalwareCantFly
Copy link

Description

Hi,
There is an issue that you can't really delete large entities.
For example, trying to delete APT28 intrusion set, would kill the CPU for more then 10 minutes.
During this time, the web interface is not responsive at all, and you won't be able to load anything.
During this time, only the server hosting the frontend platform would sweat, while the Elastic server is pretty relaxed.

By the end of this time, the intrusion-set is not even deleted.

Tried deleting APT28 on the demo.opencti.io environment, and it killed the environent. (sorry about that 🙈)

Thank you!

Environment

Demo environment and another 5.12.29

Reproducible Steps

Delete a large enitity with a lot of relationships and objects

Screenshots

Before
image
After:
image
image

@MalwareCantFly MalwareCantFly added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 2, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 5, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.0 milestone Feb 5, 2024
@richard-julien richard-julien self-assigned this Feb 9, 2024
@richard-julien richard-julien linked a pull request Feb 10, 2024 that will close this issue
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 12, 2024
Kedae pushed a commit that referenced this issue Feb 12, 2024
@Kedae Kedae modified the milestones: Release 6.0.0, Release 5.12.30 Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants