Deadlock's when running /init/allMappingsets call
We’ve noticed that during the recent upgrade, the ‘/init/allMappingsets’ call has been causing deadlocks. Following the advice from the change log to repeat the call, it had to be run over 20 times within a single dataspace. This process took several hours to complete. It has also raised concerns about the accuracy of the dataset mapping, due to it being needed to run several times.
Was there a process that we missed that would have avoided this issue happening as much as it did? Or, is there future work happening to reduce/eliminate the deadlocks that happen when running this call?
Thanks for taking the time to read this and I'm looking forward to your response.