-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
EXECUTION_SWEEP job queue is growing #20255
Comments
|
|
1 similar comment
|
@wieldes Hi, could you try to execute the above same SQLs on the task table? |
|
I noticed that sweep IMAGE_SCAN executions took long time which caused the high latency for the EXECUTION_SWEEP job.
Could you also try to check the size of the of IMAGE_SCAN vendor type includes execution and task table? |
A lot of records for IMAGE_SCAN.... Some time ago we disabled the automatic image scan. Will it be safe to remove IMAGE_SCAN records from task and execution tables? |
If you don't need to keep the scan status or report for the artifacts, you can manually delete these records. Even after deletion, you can still re-trigger the image scan to re-analyze vulnerabilities for the artifacts. |
In the current situation, the job can't complete in 1 hour, we should adjust the default execution sweep schedule from every hour to every day or editable setting |
Editable setting, it sounds good) |
Hello
We are seeing a problem with the growth of the job queue for the EXECUTION_SWEEP job type.
logs:
The job cannot delete a job for type EXECUTION_SWEEP in the "task" table because there is no entry for the execution_id.
for example:
The "task" table does not have entries for executions in the "Error" status for vendor_type = 'EXECUTION_SWEEP'
Q:
Version v2.9.3-f65d2380
The text was updated successfully, but these errors were encountered: