Friends, someone could me explain how to configure the file default.apt. I would like to configure 4 nodes.
I found the example below. You could explain me what each line means? What is N1, S1, S2, app1, app2 and bigdata? Because some nodes are configured different from the others?
EXEMPLE:
{
node "n1" {
fastname "s1"
pool "" "n1" "s1" "app2" "sort"
resource disk "/orch/n1/d1" {}
resource disk "/orch/n1/d2" {"bigdata"}
resource scratchdisk "/temp" {"sort"}
}
node "n2" {
fastname "s2"
pool "" "n2" "s2" "app1"
resource disk "/orch/n2/d1" {}
resource disk "/orch/n2/d2" {"bigdata"}
resource scratchdisk "/temp" {}
}
node "n3" {
fastname "s3"
pool "" "n3" "s3" "app1"
resource disk "/orch/n3/d1" {}
resource scratchdisk "/temp" {}
}
node "n4" {
fastname "s4"
pool "" "n4" "s4" "app1"
resource disk "/orch/n4/d1" {}
resource scratchdisk "/temp" {} }
}
Thanks
Igor Bastos Martins
http://www.oportunidadesembi.com.br
default.apt
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 161
- Joined: Mon Mar 17, 2008 10:33 am
default.apt
Last edited by igorbmartins on Sun Jul 20, 2008 8:53 am, edited 2 times in total.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
node is a unique name for each (logical) processing name; it is used primarily in reporting error messages - internally DataStage uses node #0, node #1 and so on.
fastname is the network node name of the machine on which that processing node will execute. If you are only using one machine the value of fastname must be the name of that machine in each node specification.
app1, app2, sort and so on are examples of "node pool" names; stages can be constrained to execute in a node pool (a subset of available processing nodes) - some stages do so automatically, for example the Sort stage seeks out a node pool called "sort".
bigdata is an example of a "disk pool" name. It's a similar concept to node pool - you can specify that a stage uses the directories mentioned in a disk pool.
It is a good idea to configure a large amount of scratchdisk.
fastname is the network node name of the machine on which that processing node will execute. If you are only using one machine the value of fastname must be the name of that machine in each node specification.
app1, app2, sort and so on are examples of "node pool" names; stages can be constrained to execute in a node pool (a subset of available processing nodes) - some stages do so automatically, for example the Sort stage seeks out a node pool called "sort".
bigdata is an example of a "disk pool" name. It's a similar concept to node pool - you can specify that a stage uses the directories mentioned in a disk pool.
It is a good idea to configure a large amount of scratchdisk.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
is this config right?
Do you guys see anything wrong in this default.apt.
I tried to run seq gen stage in parallel and it gives me duplicate keys.
node "node1"
{
fastname "SMIMetlt001mgt"
pools ""
resource disk "/data/DataStage/datasets" {pools ""}
resource scratchdisk "/data/DataStage/scratch" {pools ""}
}
node "node2"
{
fastname "SMIMetlt001mgt"
pools ""
resource disk "/data/DataStage/datasets" {pools ""}
resource scratchdisk "/data/DataStage/scratch" {pools ""}
}
I tried to run seq gen stage in parallel and it gives me duplicate keys.
node "node1"
{
fastname "SMIMetlt001mgt"
pools ""
resource disk "/data/DataStage/datasets" {pools ""}
resource scratchdisk "/data/DataStage/scratch" {pools ""}
}
node "node2"
{
fastname "SMIMetlt001mgt"
pools ""
resource disk "/data/DataStage/datasets" {pools ""}
resource scratchdisk "/data/DataStage/scratch" {pools ""}
}
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 467
- Joined: Tue Mar 20, 2007 6:36 am
- Location: Chennai
- Contact:
Use the surrogate key generator stage to generate your keys or use the system variables which give you the Partition number and the number of partitions to get keys which are not duplicates.
Minhajuddin
<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>