There are many ways:
1) You can specify the "hostname" command instead of the benchmark executable when you run mpirun.
(Note that you can run non MPI programs with mpirun.)
2) Use MPI_Get_processor_name() to find the name of the host in your MPI benchmark.
3) You can even ssh into the nodes and see if they really are running on the nodes.
(This method may slow down your benchmark by a bit...)
Rayson
=================================
Open Grid Scheduler / Grid Engine
http://gridscheduler.sourceforge.net/
Scalable Grid Engine Support Program
http://www.scalablelogic.com/
________________________________
From: Subbarao Kota <subbarao.kota_at_gmail.com>
To: Justin Riley <jtriley_at_mit.edu>
Cc: starcluster_at_mit.edu
Sent: Monday, April 23, 2012 8:12 PM
Subject: Re: [StarCluster] Error when running mpich2 plugin using Starcluster
Hi Justin, Thanks so much.
I was able to use one of the 32-bit public AMIs. MPICH2 plugin appeared to have worked. And also the passwordless login into the nodes. I was also able to execute the benchmarks in the head node. But I couldn't confirm if the benchmark was executed in the cluster or just the head-node. Attached is an example of the log when attempted for STREAM benchmark. It was run as root from master node. I passed only master, node001 in the arguments for mpirun command but number of nodes (processes) -np as 4 just to check.
The result indicates the benchmark ran on 4 nodes. But I only have master node and 1 worker node in the cluster. How can I confirm if the benchmark really ran on all the nodes?
Please advise,
Subbarao Kota.
Subbarao Kota.On Feb 22, 2012, at 11:54 AM, Justin Riley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Also, use the 'listpublic' command to get a list of StarCluster
> supported AMIs which you can use in the node_image_id setting. Keep in
> mind that 32bit AMIs can only be used with 32bit-compatible instance
> types and similarly for 64bit AMIs. StarCluster will let you know when
> you've specified an incompatible AMI/instance type combo.
>
> ~Justin
>
> On 02/22/2012 11:52 AM, Justin Riley wrote:
>> Subbarao,
>>
>> You're missing a required option in the config file. Open your
>> StarCluster config ($HOME/.starcluster/config) and search for
>> "t1-micro-trial-cluster". In that [cluster] section you are
>> missing 'node_image_id' setting. This setting specifies the AMI id
>> to use for all worker nodes (also applies for master node if
>> master_image_id is not set).
>>
>> HTH,
>>
>> ~Justin
>>
>> On 02/20/2012 03:18 PM, Subbarao Kota wrote:
>>> Hello star cluster:
>>
>>> Can you please help me fix this error? Where should set the
>>> option node_image_id in the config file?
>>
>>> $ starcluster runplugin mpich2 t1-micro-trial-cluster StarCluster
>>> - (http://web.mit.edu/starcluster) (v. 0.93.1) Software Tools
>>> for Academics and Researchers (STAR) Please submit bug reports
>>> to starcluster_at_mit.edu
>>
>>> !!! ERROR - missing required option node_image_id in section
>>> "cluster t1-micro-trial-cluster"
>>
>>
>>> Thanks. _______________________________________________
>>> StarCluster mailing list StarCluster_at_mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>
>> _______________________________________________ StarCluster mailing
>> list StarCluster_at_mit.edu
>> http://mailman.mit.edu/mailman/listinfo/starcluster
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk9FHdgACgkQ4llAkMfDcrljbgCeJJ2kaukbngu24yxm9JvCt2Pv
> YocAoIVsyjI6dN/Bw7UHg3yABR0GGIVB
> =HZfv
> -----END PGP SIGNATURE-----
_______________________________________________
StarCluster mailing list
StarCluster_at_mit.edu
http://mailman.mit.edu/mailman/listinfo/starcluster
Received on Thu Apr 26 2012 - 12:03:03 EDT