Node Pool &resource constaint; Resource pool not visible

Tejas Pujari · Post by **Tejas Pujari** » Sun May 08, 2011 2:01 am

Hi All,

I'm trying to create new Config file "con1.apt". I have following problem.

I have created new config file and removed the default node from it.
removed default resource DISK AND SCRATCH DISK.
i have add two pools for each resource disk,scratch disk and node.
i have not included any default pool in the file.
i have changed APT_CONFIG_FILE for a particular job.

now when I'm trying to use this in
Node Pool &resource constaint
i can see node pools but i'm not able to see or select resource option over there.

where as when i declare node name from default file i.e. default node in the "con1.apt" file along with new node "con1.apt".

then i can see resource disk pool of new node "con1.apt" but i do not see resource scratch disk pool, and none of the disk pool from default file.

order wise new has been defied 1st in the config file and default node has been defiled 2nd.

Can any body suggest why this is happeing.
what do i need to do if i want to have 2 disk and 2scrtch disks.?

Tejas Pujari · Post by **Tejas Pujari** » Sun May 08, 2011 2:31 am

Default Config:
{
node "node1"
{
fastname "W2PZ2MMX03"
pools ""
resource disk "C:/Ascential/DataStage/Datasets" { pools "" }
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "" }
}
}

New config

{

node "no2"
{
fastname "W2PZ2MMX03"
pools "T1" "sort"
resource disk "D:/Dataset"{pools "" "D3" "D2"}
resource scratchdisk "D:/scratch"{pools "" "sort" "S1"}
resource disk "C:/Ascential/DataStage/Datasets" { pools "A" }
resource scratchdisk "C:/Ascential/DataStage/Scratch" { pools "B" }

}

}

Here i'm not able to see resource in the constarint drop down list.

greggknight · Post by **greggknight** » Sun May 08, 2011 8:01 am

Is there a reason you have only one node?

This is one of my configs
I have a 4core cpu.
12G mem
three drives
C:\ Where datastage is installed and used for scratch.
D:\ San Drive
E:\ San Drive

{
node "node0"
{
fastname "DC1VMASCEN001"
pools ""
resource disk "D:/DW_PROJECTS/1_DSProjectDataFiles/PROJ_CORP_DataWareHouse/DataSets/DataSets" {pools ""}
resource scratchdisk "C:/DS_SCRATCH/ONE" {pools "" pools "sort"}
}
node "node1"
{
fastname "DC1VMASCEN001"
pools ""
resource disk "E:/DW_PROJECTS/1_DSProjectDataFiles/PROJ_CORP_DataWareHouse/DataSets/DataSets" {pools ""}
resource scratchdisk "C:/DS_SCRATCH/TWO" {pools "" pools "sort"}
}
}

Tejas Pujari · Post by **Tejas Pujari** » Sun May 08, 2011 9:03 am

greggknight wrote:Is there a reason you have only one node?

Well i was wrong my machine iual core CPU so that means it has 2 CPU.

Can you tell me is the 2nd Config file that i have mentioned earlier is correct?

For resource scratch disk pools you have mentioned 2 pools.
{pools "" pools "sort"}

is it necessary to put pools keyword twice for two seperate pools?

ray.wurlod · Post by **ray.wurlod** » Sun May 08, 2011 1:14 pm

At least one node must be in the default node pool (""). Whenever you create a configuration file, use the Check facility to make sure it's one that will work. This can be done in the Configurations manager from the GUI or using the orchadmin -check command.

greggknight · Post by **greggknight** » Sun May 08, 2011 7:25 pm

Node pools and the default node pool
Node pools allow association of processing nodes based on their characteristics. For example, certain nodes can have large amounts of physical memory, and you can designate them as compute nodes. Others can connect directly to a mainframe or some form of high-speed I/O. These nodes can be grouped into an I/O node pool.

The option pools is followed by the quoted names of the node pools to which the node belongs. A node can be assigned to multiple pools, as in the following example, where node1 is assigned to the default pool ("") as well as the pools node1, node1_css, and pool4.

node "node1"
{
fastname "node1_css"
pools "" "node1" "node1_css" "pool4"
resource disk "/orch/s0" {}
resource scratchdisk "/scratch" {}
}

A node belongs to the default pool unless you explicitly specify a pools list for it, and omit the default pool name ("") from the list.

Once you have defined a node pool, you can constrain a parallel stage or parallel job to run only on that pool, that is, only on the processing nodes belonging to it. If you constrain both an stage and a job, the stage runs only on the nodes that appear in both pools.

Nodes or resources that name a pool declare their membership in that pool.

When you initially configure your system you can place all nodes in pools that are named after the node's name and fast name. Additionally include the default node pool in this pool, as in the following example:

node "n1"
{
fastname "nfast"
pools "" "n1" "nfast"
}

By default, the parallel engine executes a parallel stage on all nodes defined in the default node pool. You can constrain the processing nodes used by the parallel engine either by removing node descriptions from the configuration file or by constraining a job or stage to a particular node pool.

Tejas Pujari · Post by **Tejas Pujari** » Sun May 08, 2011 10:42 pm

Agrred.

I had tested above cofig files.
In datastage manager with check option there were 0 errors.

I have do not have any problem with node pool.
problem is with resource disk pool and resource scratchdisk pool.

they are present in the configuration file but i'm not able to view them in the
Node Pool &resource constaint drop down list for any Job's stages's advance tab