-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible race condition in GenomicsDBImport multi-interval mode. #5300
Comments
@kgururaj @nalinigans Any thoughts on this one? |
Will let @kgururaj comment before looking at this code. |
Would it be possible to provide the interval list used? |
I hit this error as well when I was doing a "plumbing" test for the new exome joint calling (I meant to merge the intervals like you suggested, but I made a mistake). That was just one sample over half of chr20. I can email you the inputs. |
I can actually replicate this with an interval list with two intervals:
throws
We typically run with |
@kgururaj @nalinigans Just pinging you to make sure you notice @ldgauthier 's comment above where she reproduces this with just 2 intervals. |
We were looking at this just now, and it seems like the problem might be this line in
Notice that it's unconditionally calling |
reader-threads are used in the importer. Not a race condition in GenomicsDB - InitializedQueryWrapper wasn't written for multiple intervals. CI test with multiple reader threads
I had same issue. @ldgauthier 's comment work well in my case. |
reader-threads are used in the importer. Not a race condition in GenomicsDB - InitializedQueryWrapper wasn't written for multiple intervals. CI test with multiple reader threads
reader-threads are used in the importer. Not a race condition in GenomicsDB - InitializedQueryWrapper wasn't written for multiple intervals. CI test with multiple reader threads
* The newest release of GenomicsDB treats spanning deletions (spanning from earlier positions) as deletions in the min PL value computation. This behavior now matches the behavior of CombineGVCFs. A more detailed description of the issue is provided in #4963 * Deleted a couple of files which are no longer necessary. * Fixed the index of newMQcalc.combined.g.vcf * Fix for #5300 when multiple reader-threads are used in the importer. Not a race condition in GenomicsDB - InitializedQueryWrapper wasn't written for multiple intervals.
@vdauwera reports getting this error when running
GenomicsDBImport
with a large interval list as the-L
input:Looking at the code that produces this error, this seems like a "should never happen" type of error that would likely only be produced by a race condition of some kind.
Full stderr log follows:
The text was updated successfully, but these errors were encountered: