understanding sequencer.sh to allocate nodes to job
Posted: Sat Jan 05, 2013 4:59 am
I was going through the Deploying Grid solution with Infosphere Information Server Redbook where a section describes the usage of sequencer.sh script to be run from within the sequence to create dynamic configuration file and use the same for jobs downstream.
The individual jobs however have different approach where osh_conductor.sh triggers Dynamic_Grid.sh which creates dynamic config file and holds resources and when the job finishes releases the resources back to resource manager.
In the sequencer if sequencer.sh is used only to return a dynamic configuration file, I presume the dynamic config file is created based on idle nodes at the time of creation but when the downstream jobs run how are resources held and released back as and when downstream jobs trigger and finish ?
The individual jobs however have different approach where osh_conductor.sh triggers Dynamic_Grid.sh which creates dynamic config file and holds resources and when the job finishes releases the resources back to resource manager.
In the sequencer if sequencer.sh is used only to return a dynamic configuration file, I presume the dynamic config file is created based on idle nodes at the time of creation but when the downstream jobs run how are resources held and released back as and when downstream jobs trigger and finish ?