Difference between revisions of "LCMAPS Tracking GroupID plugin"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 18: Line 18:
 
         |-dhclient
 
         |-dhclient
 
         |-events/0
 
         |-events/0
      ├─pbs_mom
+
        ├─pbs_mom
      │  ├─bash
+
        │  ├─bash
      │  │  └─1337.stro.n /var/spool/pbs/mom_priv/jobs/1337.stro.nikhef.nl.SC
+
        │  │  └─1337.stro.n /var/spool/pbs/mom_priv/jobs/1337.stro.nikhef.nl.SC
      │  │      └─jobwrapper /opt/lcg/libexec/jobwrapper ./CREAM31337_jobWrapper.sh
+
        │  │      └─jobwrapper /opt/lcg/libexec/jobwrapper ./CREAM31337_jobWrapper.sh
      │  │          └─CREAM31337_ -l ./CREAM31337_jobWrapper.sh
+
        │  │          └─CREAM31337_ -l ./CREAM31337_jobWrapper.sh
      │  │              └─perl -e...
+
        │  │              └─perl -e...
      │  │                  ├─perl -e...
+
        │  │                  ├─perl -e...

Revision as of 11:52, 9 April 2011

Tracking Group IDs are added to batch jobs to be able to track them regardless if they escape the process tree.

Batch systems that use this feature are:

  • Sun Grid Engine (SGE, now known as the Oracle Grid Engine)
  • Condor-C batch system

Other batch systems are known to have the feature, but it doesn't seem to be used in (known) Grid deployments:

  • LSF
  • Torque/PBS

Why do we need this plugin?

Processes are nested. They are always spawned from another process. The root is the init process.

Here is an example process tree:

init-+-crond
       |-dbus-daemon
       |-dhclient
       |-events/0
       ├─pbs_mom
       │   ├─bash
       │   │   └─1337.stro.n /var/spool/pbs/mom_priv/jobs/1337.stro.nikhef.nl.SC
       │   │       └─jobwrapper /opt/lcg/libexec/jobwrapper ./CREAM31337_jobWrapper.sh
       │   │           └─CREAM31337_ -l ./CREAM31337_jobWrapper.sh
       │   │               └─perl -e...
       │   │                   ├─perl -e...