JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCPEM Archives


CCPEM Archives

CCPEM Archives


CCPEM@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCPEM Home

CCPEM Home

CCPEM  May 2015

CCPEM May 2015

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: cluster jobs quitting prematurely

From:

Qiu-Xing Jiang <[log in to unmask]>

Reply-To:

Qiu-Xing Jiang <[log in to unmask]>

Date:

Thu, 21 May 2015 02:49:58 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (110 lines)

Dear Chris, Sjors and all others on this list,
We have had similar problems that our refinement jobs quit prematurely.
The admin for our in-house cluster had a monitor for the sizes of packets
passing through the switch boxes and blamed the limited RAM in our system
to be the culprit. But the size of the passing packets was topped at < 300
MB, and should not lead to premature quit. Last week I moved one
refinement job to the TACC STAMPEDE supercomputer where I could use four
1TB RAM nodes to test whether it was the limited memory that caused the
problem. The result was that with super large RAM, the refinement was able
to finish without glitch. In TACC, I have four nodes, and each node has 16
cores and each core launches 64 threads and 1.0 GB RAM per thread. At
home, we recently spent some money to upgrade all nodes to either 128 GB
or 256GB RAM, and when we ran the job, we limited to 2 cores per node, 12
threads per core, and 4 GB per thread. We had much more RAM left than in
TACC, but we still encountered premature quit, usually after the 7-8
iterations of refinement, and always as Chris pointed out, at the end of
an iteration. It is quite puzzling. We would like to know what is causing
it and how to manage it so that we donšt have to use TACC supercomputer if
possible.
BTW, we have been using Relion 1.3 and Relion 1.2 with a patch for helical
reconstruction.
Thanks for sharing your thoughts and experience.
Qiu-Xing






On 5/20/15, 7:41 PM, "Christopher Akey" <[log in to unmask]> wrote:

>Sjors and users-
>
>My previous refinements were running fine on 2 different clusters, but
>with occasional instances where the
>job would just stop, usually at the end of an iteration, one could just
>continue the job and would not
>every understand why it stopped. The errors often involve an early or
>improper exit by a process.
>
>After tweaking my openMPI submit command using -hostfile to use as many
>cores as possible while not having
>the job quit early due to insufficient memory, the job ran fine for the
>entire 3d refine iteration but
>crashed during the less memory intensive maximization (as below). It is
>very hard to know what to try
>next without understanding the cause of an "improper" exit.
>
>This job only differs from previous ones in that it is using a mask but
>this hardly seems a likely
>problem.
>
>To conserve memory I was using 36 of the cores on a 120 core cluster with
>the jobs spread
> amongst them using a hostfile to specify the number of slots/cores per
>node,
> based on how much memory the node has, but node1 which exited improperly
> belongs to the group with less memory, and thus proportionately fewer
>processes.
>
>Any suggestions???  I'd like to understand this problem.
>
>C Akey
>
>
>Expectation iteration 7
>3.78/3.78 hrs
>............................................................~~(,_,">
> Averaging half-reconstructions up to 40 Angstrom resolution to prevent
>diverging orientations ...
> Note that only for higher resolutions the FSC-values are according to
>the gold-standard!
> Calculating gold-standard FSC ...
> Maximization ...
>000/??? sec ~~(,_,">
>
>--------------------------------------------------------------------------
>-----------------------
>
>mpirun has exited due to process rank 2 with PID 6982 on
>node compute-0-1.local exiting improperly. There are two reasons this
>could occur:
>
>1. this process did not call "init" before exiting, but others in
>the job did. This can cause a job to hang indefinitely while it waits
>for all processes to call "init". By rule, if one process calls "init",
>then ALL processes must call "init" prior to termination.
>
>2. this process called "init", but exited without calling "finalize".
>By rule, all processes that call "init" MUST call "finalize" prior to
>exiting or it will be considered an "abnormal termination"
>
>This may have caused other processes in the application to be
>terminated by signals sent by mpirun (as reported here).
>
>--------------------------------------------------------------------------
>------------------------


________________________________

UT Southwestern


Medical Center



The future of medicine, today.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager