Ben Weisburd

This is not currently supported. It's non-trivial to add this behavior in a robust way.

or it might not be that difficult. If you still need this, please submit a PR, adding an option to the ArgParser constructor to enable this behavior (since enabling it...

There's no such feature currently.

I don't remember exactly which issues this was intended to address. If you feel like you can create a backward-compatible fix, a PR to fix this would be appreciated.

This looks like a bug. A PR to fix this would be appreciated.

Yes, this was human data. It might have been a long variant.

I've run a stable cluster with `-Xms3900m -Xmx3900m` or more. I think memory usage will depend on what you're doing in terms of data size, indexing, and queries. (https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html) Why...

I've looked at exporting elasticsearch snapshots to google buckets, but these aren't 100% reliable (I/O errors cause incomplete backup/restore ~10% of the time) Is there some way to use GCE...

looks like there's gradual progress toward snaphot/restore for PVCs: https://github.com/kubernetes/website/issues/1691

At least 2 forks are being actively maintained, with output genotypes that AFAIK are identical to the official version: https://github.com/bw2/ExpansionHunter (this one is mine) and https://gitlab.com/andreassh/ExpansionHunter