parallel job on one node
Posted: Mon Feb 19, 2007 9:25 am
I have two configurations:
node1:
{
node "node1"
{
fastname "tnet368"
pools ""
resource disk "/prop/loc/tnbilfor/dtstnbilfor/work/node01/disk00/" {pools ""}
resource scratchdisk "/prop/loc/tnbilfor/dtstnbilfor/work/node01/scratch00/" {pools ""}
}
}
node2:
{
node "node2"
{
fastname "tnet368"
pools ""
resource disk "/prop/loc/tnbilfor/dtstnbilfor/work/node02/disk00/" {pools ""}
resource scratchdisk "/prop/loc/tnbilfor/dtstnbilfor/work/node02/scratch00/" {pools ""}
}
}
If I run a parallel job with the first configuration, it runs fine. if I run the same job with the seconde configuration, it aborts with:
descriptions: Error when checking operator: Node name "node1" not in config file
If I reset the job and run it again with the second, it runs fine. If I run then with the first, it aborts.
It seems that the engine remembers the last configuration and excepts that the same node is available.
Can anybody help?
node1:
{
node "node1"
{
fastname "tnet368"
pools ""
resource disk "/prop/loc/tnbilfor/dtstnbilfor/work/node01/disk00/" {pools ""}
resource scratchdisk "/prop/loc/tnbilfor/dtstnbilfor/work/node01/scratch00/" {pools ""}
}
}
node2:
{
node "node2"
{
fastname "tnet368"
pools ""
resource disk "/prop/loc/tnbilfor/dtstnbilfor/work/node02/disk00/" {pools ""}
resource scratchdisk "/prop/loc/tnbilfor/dtstnbilfor/work/node02/scratch00/" {pools ""}
}
}
If I run a parallel job with the first configuration, it runs fine. if I run the same job with the seconde configuration, it aborts with:
descriptions: Error when checking operator: Node name "node1" not in config file
If I reset the job and run it again with the second, it runs fine. If I run then with the first, it aborts.
It seems that the engine remembers the last configuration and excepts that the same node is available.
Can anybody help?