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
pierremahot opened this issue
Jan 22, 2024
· 1 comment
· Fixed by #5631
Assignees
Labels
buguse for describing something not working as expectedcriticaluse to identify critical bug to fix ASAPsolveduse to identify issue that has been solved (must be linked to the solving PR)
The indexing process retry on error when elastic respond an error on parsing the file
Environment
docker / kube
OpenCTI version: 5.12.20
OpenCTI client: frontend
Reproducible Steps
1 start idexing
2 get error with elastic (don't know the exact cause can be no available heap related)
Expected Output
do not infinite retry
Actual Output
infinite retry.
this also restart the manager and update startup date of the manager.
get big logs because of the base 64 of the file send to the logs.
The text was updated successfully, but these errors were encountered:
pierremahot
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 22, 2024
When a file fail indexing, the process retry every minute on the same file
As we cant do anything, we only need to log the error instead of throw.
When a file fail indexing in elastic, we throw and log too much
Instead of throw we will log (point 1) but we need to log the error without the body content as it contains the file in base64.
buguse for describing something not working as expectedcriticaluse to identify critical bug to fix ASAPsolveduse to identify issue that has been solved (must be linked to the solving PR)
Description
The indexing process retry on error when elastic respond an error on parsing the file
Environment
Reproducible Steps
1 start idexing
2 get error with elastic (don't know the exact cause can be no available heap related)
Expected Output
do not infinite retry
Actual Output
infinite retry.
this also restart the manager and update startup date of the manager.
get big logs because of the base 64 of the file send to the logs.
The text was updated successfully, but these errors were encountered: