Open Xuehai-Chen opened 3 months ago
I think the root cause is the method ensureCapacity of GenotypesCache is not synchronized. So when multiple task threads run into this method, the new added cache is not fully initialized.
Hi @Xuehai-Chen HaplotypeCallerSpark is not developed regularly as the original HaplotypeCaller therefore it has its own quirks and issues present. It can be considered as an experimental tool/a conceptual tool to show that HaplotypeCaller may be accelerated using spark. It is not endorsed as a ready to be used tool for any purpose. Its development is not a high priority therefore we don't recommend using it.
Bug Report
Affected tool(s) or class(es)
HaplotypeCallerSpark
Affected version(s)
Description
spark task failed, here is the stack trace:
Steps to reproduce
Run HaplotypeCallerSpark multiple times, it had a chance to fail. Looks like the method ensureCapacity of GenotypesCache is not synchronized. So when multiple task threads run into this method, the new added cache is not fully initialized.
Expected behavior
spark tasks success
Actual behavior
spark tasks failed