Steps to reproduce:
Started crawling across 13 different engines.
9 successfully completed but at engine number 10 this was the first log message:
The crawler worker responsible for this crawl has failed. The crawl is suspended automatically and will be resumed by another worker. You can check crawler logs for the details on the underlying issue.
Trying to cancel it via the API has left it stuck, tried restarting the cluster with no success, still in a stuck position.
Is there anything that can be done to restart the Queue Manager?