Hi,
Could some one please help me arrange the hierarchy of Conductor node, Section leader and player in the image.
Thanks for the help
Conductor node, Section leader and player help
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 150
- Joined: Tue Mar 13, 2007 1:17 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I believe all you need to do is to drag them into place.
There is one conductor process, one section leader per processing node, and one player process per operator on each processing node. The number of operators is determined from the score, which is composed at run time using generated osh and the configuration file as inputs.
There is one conductor process, one section leader per processing node, and one player process per operator on each processing node. The number of operators is determined from the score, which is composed at run time using generated osh and the configuration file as inputs.
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.
Re: Conductor node, Section leader and player help
Hi
Operators. These underlie the stages in a DataStage job. A single
stage may correspond to a single operator, or a number of
operators, depending on the properties you have set, and whether
you have chosen to partition or collect or sort data on the input
link to a stage. At compilation, DataStage evaluates your job
design and will sometimes optimize operators out if they are
judged to be superfluous, or insert other operators if they are
needed for the logic of the job.
Players. Players are the workhorse processes in a parallel job.
There is generally a player for each operator on each node. Players
are the children of section leaders; there is one section leader per
processing node. Section leaders are started by the conductor
process running on the conductor node (the conductor node is
defined in the configuration file.
I am giving genaral information.
Operators. These underlie the stages in a DataStage job. A single
stage may correspond to a single operator, or a number of
operators, depending on the properties you have set, and whether
you have chosen to partition or collect or sort data on the input
link to a stage. At compilation, DataStage evaluates your job
design and will sometimes optimize operators out if they are
judged to be superfluous, or insert other operators if they are
needed for the logic of the job.
Players. Players are the workhorse processes in a parallel job.
There is generally a player for each operator on each node. Players
are the children of section leaders; there is one section leader per
processing node. Section leaders are started by the conductor
process running on the conductor node (the conductor node is
defined in the configuration file.
I am giving genaral information.
hitmanthesilentassasin wrote:Hi,
Could some one please help me arrange the hierarchy of Conductor node, Section leader and player in the image.
Thanks for the help
-
- Premium Member
- Posts: 145
- Joined: Fri Sep 15, 2006 12:23 pm
-
- Participant
- Posts: 150
- Joined: Tue Mar 13, 2007 1:17 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Re: Conductor node, Section leader and player help
There is ALWAYS a player for each operator (each operator mentioned in the score) on each node.sreddy wrote:There is generally a player for each operator on each node.
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.