-
Notifications
You must be signed in to change notification settings - Fork 110
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
abyss-pe 2.1.0 segfault with Open MPI 3.1.0 #236
Comments
Hi, @jdmontenegro. Thanks for the detailed bug report. You have good timing. I am seeing a nearly identical error message right now and am also troubleshooting it. The only difference is that I'm not seeing
ABySS 2.1.0 I'm wondering whether it may be an issue with Open MPI 3.1.0. I'm going to try compiling ABySS against open-mpi 2.1.3. Are you able to try an older version of Open MPI? |
Hi Shaun,
Thank you for your quick reply. I'm sure we can try an older version of
openmpi. Which version would you recommend we try?
Cheers,
|
We've had success with OpenMPI 1.6.3. I've seen 3.1.0 fail. The |
Thank you Shaun. I'll run some tests and let you know how it goes. Cheers,
|
I tried with no luck ABySS 2.1.0 with OpenMPI 3.1.0 with |
You can also use the ABySS Bloom filter assembler, which does not require OpenMPI and reduces the memory requirement by about ten fold. |
@jdmontenegro Which distribution of Linux, Linux kernel version, and compiler are you using? Did you use a package manager like Conda or Linuxbrew to install ABySS, Open MPI, or any of their dependencies, or did you install manually from source?
|
Dear Shaun,
Please find below the details of the system I am using at the moment. BTW,
I submitted a test using a version of balder compiled agains openmpi/2.1.3.
It is taking quite a bit more time to reach the same breakpoint as before
(more than twice as long as a matter of fact) so I cannot give you an
update on the success of this test.
I will keep you updated though. Thank you!
>> cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
>> uname -a
Linux balder.agrf.org.au 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12
22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>> gcc --version
gcc (GCC) 5.2.0
2018-06-22 3:57 GMT+10:00 Shaun Jackman <[email protected]>:
… @jdmontenegro <https://github.com/jdmontenegro> Which distribution of
Linux, Linux kernel version, and compiler are you using?
❯❯❯ cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
❯❯❯ uname -a
Linux hpce705 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Sep 15 15:05:51 UTC 2015 x86_64 GNU/Linux
❯❯❯ gcc --version
gcc (Homebrew gcc 5.5.0_4) 5.5.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#236 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AI8lusqJz8Ahfxgbh705NjzMqKXRXvqtks5t-96CgaJpZM4UsoRv>
.
|
I'm running a job with Open MPI 2.1.3 using the abyss-pe mpirun='mpirun --mca btl self,sm --mca btl_sm_eager_limit 8192' The |
Hi Shaun, Cheers, |
@jdmontenegro To do misassembly correction and scaffolding with Chromium reads, you will need to install Tigmint and ARCS, and add the See this section of the ABySS README.md for further info: https://github.com/bcgsc/abyss#scaffolding-with-linked-reads |
That's great news, @jdmontenegro! Open MPI 2.1.3 also worked for me, but I had to use the I'd recommend setting |
I've added a new entry to the FAQ: https://github.com/bcgsc/abyss/wiki/ABySS-Users-FAQ#6-why-does-abyss-crash-with-a-segmentation-fault-during-abyss-p-with-open-mpi-3x |
Thank you, Shaun! |
I'll report this issue upstream to the Open MPI developers next week when I get a chance. |
I'm getting a very similar error message:
OS: Debian Buster (docker) I'm compiling from source within the container. |
I'd suggest using the ABySS Bloom filter assembler, which does not require OpenMPI and reduces the memory requirement by about ten fold. See https://github.com/bcgsc/abyss#assembling-using-a-bloom-filter-de-bruijn-graph |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Please report
System
Hi all I am using abyss 2.1.0 compiled under openmpi/3.1.0, boost/1.66 and sparsehash/2.0.3 on a CENTOS/7 cluster with 1.5 Tb of RAM and 128 threads available.
Assembly error
My abyss command line is the following:
abyss-pe name=NewAssembly G=3000000000 s=500 v=-v np=64 k=97 in="reads1.fastq reads2.fastq"
After 9 and a half hours running I get this error:
The total number of bases sequenced was 160 Gbp for a 3 Gbp diplod genome (~50X sequencing depth )
I am using the slurm scheduler and asking for 1Tb of memory and 64 cpus (64 tasks and 1 cpu per task) for this assembly. I can see that each thread is using around 8.5 Gbp, so 64 * 8.5 = 544 Gbp. That is roughly half the memory allocated for this process. The system administrator is looking into the details of the failure, but so far I cannot find a way around this. I have tried reducing the number of threads to 32 and 16 and the error is the same.
Any help would be much appreciated.
Kind regards,
The text was updated successfully, but these errors were encountered: