On Aug 30, 2011, at 9:26 AM, John Hearns wrote:
> On 30 August 2011 02:55, Ralph Castain wrote:
>> Instead, all used dynamic requests - i.e., the job that was doing a
>> comm_spawn would request resources at the time of the comm_spawn call. I
>> would pass the request to Torque, and if resourc
On 30 August 2011 02:55, Ralph Castain wrote:
> Instead, all used dynamic requests - i.e., the job that was doing a
> comm_spawn would request resources at the time of the comm_spawn call. I
> would pass the request to Torque, and if resources were available,
> immediately process them into OMP
On Aug 29, 2011, at 5:40 AM, Reuti wrote:
> Am 27.08.2011 um 16:35 schrieb Ralph Castain:
>
>>
>> On Aug 27, 2011, at 8:28 AM, Rayson Ho wrote:
>>
>>> On Sat, Aug 27, 2011 at 9:12 AM, Ralph Castain wrote:
OMPI has no way of knowing that you will turn the node on at some future
point
Am 27.08.2011 um 16:35 schrieb Ralph Castain:
>
> On Aug 27, 2011, at 8:28 AM, Rayson Ho wrote:
>
>> On Sat, Aug 27, 2011 at 9:12 AM, Ralph Castain wrote:
>>> OMPI has no way of knowing that you will turn the node on at some future
>>> point. All it can do is try to launch the job on the provid
On Aug 27, 2011, at 8:28 AM, Rayson Ho wrote:
> On Sat, Aug 27, 2011 at 9:12 AM, Ralph Castain wrote:
>> OMPI has no way of knowing that you will turn the node on at some future
>> point. All it can do is try to launch the job on the provided node, which
>> fails because the node doesn't respond
On Sat, Aug 27, 2011 at 9:12 AM, Ralph Castain wrote:
> OMPI has no way of knowing that you will turn the node on at some future
> point. All it can do is try to launch the job on the provided node, which
> fails because the node doesn't respond.
> You'll have to come up with some scheme for telli
OMPI has no way of knowing that you will turn the node on at some future point.
All it can do is try to launch the job on the provided node, which fails
because the node doesn't respond.
You'll have to come up with some scheme for telling the node to turn on in
anticipation of starting a job -
I would like to know how to add nodes during a job execution.
Now my hostfile has the node 10.0.0.23 that is off,
I would start this node during the execution so that the job can use it
When I run the command:
mpirun -np 2 -hostfile /tmp/hosts application
the following message appears:
ssh: conn
