-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 6.0, 7.10, 8.10
-
Fix Version/s: 10.3
-
Component/s: Events / Works, Redis
-
Tags:
-
Backlog priority:700
-
Sprint:nxcore 10.3.7
-
Story Points:2
When the workmanager uses Redis, stopping brutally a Nuxeo instance while there are running jobs will not clean the work status stored in Redis.
As a result when restarting the Nuxeo instance the old workers are listed as running.
If these jobs are ElasticsearchIndexing work this will mess up the Elasticsearch indexing status on the Admin center.
It will also mess up the waitForCompletion method that count scheduled and running jobs.
A workaround is to flush the Redis database when the cluster is down.