Hi Reuti,<br> <br> Thanks again for your
reply. We were able to add a PE using qconf -ap. As I had mentioned earlier, mpirun points to the correct location, and now I can get the job script to execute the mpirun command. However, it seems to disregard the number of processes specified. Instead, the job is run on one processor only. <br>
<br>Here is how the PE looks like <br><br>[root@Spinode ~]# qconf -sp mpich2<br>pe_name mpich2<br>slots 999<br>user_lists NONE<br>xuser_lists NONE<br>start_proc_args NONE<br>stop_proc_args NONE<br>
allocation_rule $fill_up<br>control_slaves TRUE<br>job_is_first_task FALSE<br>urgency_slots min<br>accounting_summary FALSE<br><br>The list of all the PEs on the cluster is as follows, <br><br>[root@Spinode ~]# qconf -spl<br>
make<br>mpich2<br><br>Next, I added the PE to one of the queues running on the cluster. It looks like this, <br><br>[root@Spinode ~]# qconf -sq molsim.q<br>qname molsim.q<br>hostlist @molsimhosts<br>
seq_no 0<br>load_thresholds np_load_avg=1.75<br>suspend_thresholds NONE<br>nsuspend 1<br>suspend_interval 00:05:00<br>priority 0<br>min_cpu_interval 00:05:00<br>
processors UNDEFINED<br>qtype BATCH INTERACTIVE<br>ckpt_list NONE<br>pe_list make mpich2<br>rerun FALSE<br>slots 1,[compute-0-1.local=16],[compute-0-2.local=16], \<br>
[compute-0-3.local=16],[compute-0-4.local=16], \<br> [compute-0-5.local=16],[compute-0-6.local=16]<br>tmpdir /tmp<br>shell /bin/bash<br>prolog NONE<br>
epilog NONE<br>shell_start_mode posix_compliant<br>starter_method NONE<br>suspend_method NONE<br>resume_method NONE<br>terminate_method NONE<br>notify 00:00:60<br>
owner_list NONE<br>user_lists NONE<br>xuser_lists NONE<br>subordinate_list NONE<br>complex_values NONE<br>projects NONE<br>xprojects NONE<br>calendar NONE<br>
initial_state default<br>s_rt INFINITY<br>h_rt INFINITY<br>s_cpu INFINITY<br>h_cpu INFINITY<br>s_fsize INFINITY<br>h_fsize INFINITY<br>
s_data INFINITY<br>h_data INFINITY<br>s_stack INFINITY<br>h_stack INFINITY<br>s_core INFINITY<br>h_core INFINITY<br>s_rss INFINITY<br>
h_rss INFINITY<br>s_vmem INFINITY<br>h_vmem INFINITY<br><br>Then, we tried to submit a job using a job script<br>--------------------------------------------------------------<br>
#!/bin/sh<br><br># request Bourne shell as shell for job<br>#$ -S /bin/sh<br><br># Name of the job<br>#$ -N mpich2_lammps_test<br><br># Name of the output log file<br>#$ -o lammps_test.log<br><br># Combine output/ error messages into one file<br>
#$ -j y<br><br># Use current working directory<br>#$ -cwd<br><br># Commands to be executed<br>mpirun -np 8 ./a.out < input > output<br>-------------------------------------------------------------<br><br>The problem is that no matter what number I specify after the -np option, the job is always executed on a single processor. <br>
<br>Your help would be appreciated. <br><br>Thanks in advance<br><br>Regards<br>Tilak<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Message: 7<br>
Date: Wed, 13 Jul 2011 12:30:18 +0200<br>
From: Reuti <<a href="mailto:reuti@staff.uni-marburg.de" target="_blank">reuti@staff.uni-marburg.de</a>><br>
Subject: Re: [mpich-discuss] mpich2 does not work with SGE<br>
To: <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
Message-ID:<br>
<<a href="mailto:33B507D9-C8E7-4F10-89E9-942633D81547@staff.uni-marburg.de" target="_blank">33B507D9-C8E7-4F10-89E9-942633D81547@staff.uni-marburg.de</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi,<br>
<br>
Am 13.07.2011 um 12:13 schrieb tilakraj dattaram:<br>
<br>
> Hi Reuti<br>
><br>
> Thanks for your reply. I forgot to mention in my previous message, but I had tried adding a Parallel Environment in SGE using qconf -ap. I did the following,<br>
><br>
> qconf -Ap mpich<br>
<br>
`qconf -Ap mpich` is the command to add a parallel environment after you edited the configuration file already beforehand. This will then be stored in SGE's configuration. Editing it later on won't be honored. If you want to edit a configuration which is already stored in SGE, you can use:<br>
<br>
`qconf -mp mpich`<br>
<br>
or start form scratch after deleting the old one by:<br>
<br>
`qconf -ap mpich`<br>
<br>
To see a list of all PEs:<br>
<br>
`qconf -spl`<br>
<br>
Don't forget to add the PE to any of your queues by editing them with `qconf -mq all.q` or alike.<br>
<br>
General rule: uppercase commands will read configuration from files, while lowercase commands will open an editor for interactive setup.<br>
<br>
<br>
> and then edited the pe file to,<br>
><br>
> pe_name mpich<br>
> slots 999<br>
> user_lists NONE<br>
> xuser_lists NONE<br>
> start_proc_args NONE<br>
> stop_proc_args NONE<br>
> allocation_rule $fill_up<br>
> control_slaves TRUE<br>
> job_is_first_task FALSE<br>
> urgency_slots min<br>
> accounting_summary FALSE<br>
><br>
> This did not work. However, here I don't see how SGE would know where to look for mpich2/ hydra. I do see a mpi directory in the $SGE_ROOT directory, where there is rocks-mpich.template file that reads the following<br>
><br>
> pe_name mpich<br>
> slots 9999<br>
> user_lists NONE<br>
> xuser_lists NONE<br>
> start_proc_args /opt/gridengine/mpi/startmpi.sh -catch_rsh $pe_hostfile<br>
> stop_proc_args /opt/gridengine/mpi/stopmpi.sh<br>
> allocation_rule $fill_up<br>
> control_slaves TRUE<br>
> job_is_first_task FALSE<br>
> urgency_slots min<br>
> accounting_summary TRUE<br>
<br>
This was for the old MPICH1. I don't know what ROCKS delivers, I would ignore it.<br>
<br>
SGE don't have to know anything about MPICH2. You only have to setup an appropriate PATH in your jobscript, so that you can access the `mpirun` of MPICH2 (and not one of any other MPI implementation) without the need of a hostlist and that's all. So, your jobscript will call `mpirun`, and a proper built MPICH2 will know about SGE and detect that it's running under SGE by checking some environment variables and then start processes on slave nodes by calling `qrsh -inherit ...` for the granted nodes.<br>
<br>
On the master node of the parallel job you can check the invocation chain by:<br>
<br>
`ps -e f`<br>
<br>
(f w/o -).<br>
<br>
-- Reuti<br>
<br>
<br>
> Does SGE need re-configuration after the mpich2 install?<br>
><br>
> Thanks in advance!<br>
><br>
> Regards<br>
> Tilak<br>
><br>
> Message: 6<br>
> Date: Tue, 12 Jul 2011 13:19:18 +0200<br>
> From: Reuti <<a href="mailto:reuti@staff.uni-marburg.de" target="_blank">reuti@staff.uni-marburg.de</a>><br>
> Subject: Re: [mpich-discuss] mpich2 does not work with SGE<br>
> To: <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
> Message-ID:<br>
> <<a href="mailto:8768BE3D-BE2D-498C-98A6-D3A72F397291@staff.uni-marburg.de" target="_blank">8768BE3D-BE2D-498C-98A6-D3A72F397291@staff.uni-marburg.de</a>><br>
> Content-Type: text/plain; charset=us-ascii<br>
><br>
> Hi,<br>
><br>
> Am 12.07.2011 um 13:03 schrieb tilakraj dattaram:<br>
><br>
> > We have a rocks cluster with 10 nodes, with sun grid engine installed and running. I then installed the most recent version of mpich2 (1.4) on the master and compute nodes. However, we are unable to run parallel jobs through SGE (we can submit serial jobs without a problem). I am a sge newbie, and most of the installation that we have done is by reading step-by-step tutorials on the web.<br>
> ><br>
> > The mpich2 manual says that hydra is the default process manager for mpich2, and I have checked that the mpiexec command points to mpiexec.hydra. Also, which mpicc, which mpiexec point to the desired location of mpich2. I understand that in this version of mpich2, hydra should be integrated with SGE by default. But maybe I am missing something here.<br>
> ><br>
> > We are able to run parallel jobs using command line by specifying a host file (e.g, mpiexec -f hostfile -np 16 ./a.out), but would like the resource manager to take care of allocating resources on the cluster.<br>
><br>
> it's necessary to set up a so called parallel environment (i.e. a PE) in SGE and request it during the job submission. Then a plain mpirun without any hostfile or -np specification will do, as all is directly delivered by SGE. If all is set up in a proper way, you could even switch off `rsh` and `ssh` inside the cluster completely, as SGE's internal startup mechanism is used then to start processes on other nodes. In fact, disabling or limiting `ssh` to admin staff is a good way to check whether your parallel application has a tight integration into the queuingsystem where all slave processes are accounted also correctly and under full SGE control for a delition by `qdel`.<br>
><br>
> For SGE there is also a mailing list: <a href="http://gridengine.org/mailman/listinfo/users" target="_blank">http://gridengine.org/mailman/listinfo/users</a><br>
><br>
> -- Reuti<br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> mpich-discuss mailing list<br>
> <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
> <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
><br>
><br>
> End of mpich-discuss Digest, Vol 34, Issue 15<br>
> *********************************************<br>
><br>
> _______________________________________________<br>
> mpich-discuss mailing list<br>
> <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
> <a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a><br>
<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss</a><br>
<br>
<br>
End of mpich-discuss Digest, Vol 34, Issue 16<br>
*********************************************<br>
</blockquote></div><br><br><br><br>