This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
I can't really test this solution as the Torque dynamic host allocator
appears to be something you are adding to that system (so it isn't part of
the released code). However, the attached code should cleanly add any nodes
to any existing allocation known to OpenRTE.
I hope to resume working on the "next-gen" OpenRTE allocation system in the
fairly near future. This will include support for dynamically obtaining and
updating host allocations via (hopefully!) convenient APIs. Since I expect
that won't be included in the Open MPI releases until at least 1.3 (release
date not known yet, but sometime in the not-near future), I will post a
patch on the OpenRTE web site in the interim - I'll announce that here as
well so people can go pick it up if they need that capability.
Please let me know how this works and/or any changes you have to make to it
to get it to work. Feel free to holler for help.
On 4/2/07 11:07 AM, "Prakash Velayutham" <Prakash.Velayutham_at_[hidden]>
> Thanks Ralph. I will wait for your Torque dynamic host addition solution.
>>>> rhc_at_[hidden] 04/02/07 1:00 PM >>>
> Hi Prakash
> This is telling you that you have an error in the comm_spawn command itself.
> I am no expert there, so I'll have to let someone else identify it for you.
> There are no limits to launching on nodes in a hostfile - they are all
> automatically considered "allocated" when the file is read. If you had the
> node name in the file, then there is no "dynamic" addition of nodes going
> Meantime, I am going to send you a different solution to dynamically adding
> nodes under Torque (or any other resource manager).
> On 4/2/07 10:53 AM, "Prakash Velayutham" <Prakash.Velayutham_at_[hidden]>
>> Thanks for the patch. I still do not know the internals of Open MPI, so can't
>> test this right away. But here is another test I ran and that failed too.
>> I have now removed Torque from the equation. I am NOT requesting nodes
>> Torque. I SSH to a compute node and start up the code as below.
>> prakash_at_wins04:~/thesis/CS/Samples>mpirun -np 4 --bynode --hostfile
>> machinefile ./parallel.laplace
>> [wins01:17699] *** An error occurred in MPI_Comm_spawn
>> [wins01:17699] *** on communicator MPI_COMM_WORLD
>> [wins01:17699] *** MPI_ERR_ARG: invalid argument of some other kind
>> [wins01:17699] *** MPI_ERRORS_ARE_FATAL (goodbye)
>> mpirun noticed that job rank 1 with PID 25074 on node wins02 exited on signal
>> 15 (Terminated).
>> 2 additional processes aborted (not shown)
>> What happened here? Why would orted not let me spawn on new nodes? What kind
>> of restrictions apply in this case? I even have the new node name in the
>> hostfile (machinefile), just in case.
>>>>> jbuisson_at_[hidden] 04/02/07 12:34 PM >>>
>> Ralph Castain a écrit :
>>> The runtime underneath Open MPI (called OpenRTE) will not allow you to spawn
>>> processes on nodes outside of your allocation. This is for several reasons,
>>> but primarily because (a) we only know about the nodes that were allocated,
>>> so we have no idea how to spawn a process anywhere else, and (b) most
>>> resource managers wouldn't let us do it anyway.
>>> I gather you have some node that you know about and have hard-coded into
>>> your application? How do you know the name of the node if it isn't in your
>> Because I can give that names to OpenMPI (or OpenRTE, or whatever). I
>> also would like to do the same, and I don't want OpenMPI to restrict to
>> what it thinks to be the allocation, while I'm sure to know better than
>> it what I am doing.
>> The concept of nodes being in allocations fixed at launch-time is really
>> rigid; and it prevents the application (or whatever else) to modify the
>> allocation at runtime, which may be quite nice.
>> Here is an ugly patch I've quickly done for my own use, which changes
>> the round-robin rmaps such that is first allocates the hosts to the
>> rmgr, as a copy&paste of some code in the dash_host ras component. It's
>> far from being bugfree, but it can be a startpoint to hack.
>>> On 4/2/07 10:05 AM, "Prakash Velayutham" <Prakash.Velayutham_at_[hidden]>
>>>> I have built Open MPI (1.2) with run-time environment enabled for Torque
>>>> (2.1.6) resource manager. Initially I am requesting 4 nodes (1 CPU each)
>>>> from Torque. The from inside of my MPI code I am trying to spawn more
>>>> processes to nodes outside of Torque-assigned nodes using
>>>> MPI_Comm_spawn, but this is failing with an error below:
>>>> [wins04:13564] *** An error occurred in MPI_Comm_spawn
>>>> [wins04:13564] *** on communicator MPI_COMM_WORLD
>>>> [wins04:13564] *** MPI_ERR_ARG: invalid argument of some other kind
>>>> [wins04:13564] *** MPI_ERRORS_ARE_FATAL (goodbye)
>>>> mpirun noticed that job rank 1 with PID 15070 on node wins03 exited on
>>>> signal 15 (Terminated).
>>>> 2 additional processes aborted (not shown)
>>>> MPI_Info info;
>>>> MPI_Comm comm, *intercomm;
>>>> char *key, *value;
>>>> key = "host";
>>>> value = "wins08";
>>>> rc1 = MPI_Info_create(&info);
>>>> rc1 = MPI_Info_set(info, key, value);
>>>> rc1 = MPI_Comm_spawn(slave,MPI_ARGV_NULL, 1, info, 0,
>>>> MPI_COMM_WORLD, intercomm, arr);
>>>> Would this work as it is or is something wrong with my assumption? Is
>>>> OpenRTE stopping me from spawning processes outside of the initially
>>>> allocated nodes through Torque?
>>>> users mailing list
>>> users mailing list
> users mailing list
- application/octet-stream attachment: test.c