Hi @paultaylor,
So, this morning I got that nice message from my ISP telling me internet would be down all day. huray.
I told myself it would have been a good idea to pause the running fix task.
But I surprisingly saw that the fix was not running anymore.
When I started to analyse the logs here is what I found :
13/10/2022 08.58.56:CEST:TimeoutThreadPoolExecutor:shutdown:SEVERE: —Shutdown:Worker
13/10/2022 08.58.57:CEST:TimeoutThreadPoolExecutor:terminated:SEVERE: —Terminated:Worker
Do I understand correctly that SK will terminate the workers if timeouts do happen ? That would be very nice in today’s situation. But can I eventually tell SK to pause the running worker instead of killing it ?
Also another question, are there any tips, aside excluding already matched and unmatched tracks, to speedup the identification process ? I currently check an average of 150k tracks per 24h. Is this due to API limits of MB and discogs ?
Thanks !