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

Timeout when deleting a report and resulting corrupted data #9190

Open
Lhorus6 opened this issue Nov 29, 2024 · 1 comment
Open

Timeout when deleting a report and resulting corrupted data #9190

Lhorus6 opened this issue Nov 29, 2024 · 1 comment
Labels
bug use for describing something not working as expected
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Nov 29, 2024

Description

Deleting a report failed. Looking in the logs, it appears to be a timeout. The timeout happens quite quickly, like 1 minute (AFAIK, it should be 5 minutes).

Looking in Elastic, it appears that the report ID has been removed from the entities contained in the report (at least in part of the entities). However, the report still has its object_ref, and the internal_relation still exists. -> The start of the deletion was therefore made, but stopped in the middle.

NB: @SouadHadjiat knows the situation, otherwise you can ping me.

Environment

OCTI 6.4.1

Reproducible Steps

The problematic report is in one of our SaaS platforms. It contains around 150 entities, and 70 inferred relationships.

I was unable to reproduce the problem by creating a report with the same characteristics.

Expected Output

Be able to delete my entity

And, if it fails, I don't want to end up with a corrupted database after only partially deleting things and stopped in the middle of cleaning.

Additional information

Note not necessarily related to this bug:

If we reach a timeout when deleting an element, we end up with corrupted entities! This approach should perhaps be reviewed.

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Nov 29, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Dec 2, 2024
@nino-filigran
Copy link

nino-filigran commented Dec 2, 2024

Could not reproduce either, but @Lhorus6 & @SouadHadjiat seem to be aware of the situation.
I guess the fix should be to either extend the timeout or to prevent timing-out when a deletion occurs.

@romain-filigran romain-filigran added this to the Bugs backlog milestone Dec 2, 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
Projects
None yet
Development

No branches or pull requests

3 participants