-
Notifications
You must be signed in to change notification settings - Fork 115
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
versionpurge job getting Job Queue stuck. #1365
Comments
Hi @cemusta , |
Hi, We will update to 1.8.5 and update this issue afterward. Best, |
Mesh v1.8.6 is recently released, targeting more job improvements - couldn't you please try it? |
Will try and update. |
Gentics Mesh Version, operating system, or hardware.
Operating System
Problem
There are some version purge jobs in the list. When we re-queue these jobs, the cms instance starts a deadlock. This deadlock makes the instance stop responding to API calls.
When we restart the instance, that job is still in the queue (not failed). if re-queue another job, the cms instance still takes the first version purge job ( 1st job in the queue ) instead. and the same process happens (deadlock and cms getting not responsive)
Because of this, all other jobs got stuck in the queue. We cannot make any schema changes. All schema migration jobs are in the job list and cannot be processed.
problematic job:
Reproducer
Expected behaviour and actual behaviour.
The text was updated successfully, but these errors were encountered: