Thanks to new stack trace feature I was able to know where each thread was blocked.
After enhancing the job execution and throughput, apparently the ss api is blocking while updating the cimi resources. This occurring because api use request which is not thread safe (supposed at certain level). The fix is to create a new instance for each thread of ss api to avoid such conflict. The patch is actually running on Nuvla.
Thanks to new stack trace feature I was able to know where each thread was blocked. After enhancing the job execution and throughput, apparently the ss api is blocking while updating the cimi resources. This occurring because api use request which is not thread safe (supposed at certain level). The fix is to create a new instance for each thread of ss api to avoid such conflict. The patch is actually running on Nuvla.