Bug 6019 - CEDPS: Add executable path to log statement
: CEDPS: Add executable path to log statement
Status: RESOLVED WONTFIX
: GRAM
wsrf managed job factory service
: development
: Macintosh All
: P3 normal
: 4.2.1
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-04-15 13:36 by
Modified: 2012-09-05 11:43 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-04-15 13:36:36
Currently the CEDPS logging does not include the executable.  This is the one
element from the job description that makes sense to log.

On one of the initial CEDPS logging statements like this one:

ts=2008-04-10T13:55:13.675-05:00  guid=a6e73310-072f-11dd-92cb-c2d2a177e4c0
event=org.globus.execution.job.create.start jobResource.id=null 
clientSubmission.id=a6206a3c-072f-11dd-862c-0013d4c3b957 
service=ManagedJobFactoryService

Please add the executable path like this:

ts=2008-04-10T13:55:13.675-05:00  guid=a6e73310-072f-11dd-92cb-c2d2a177e4c0
event=org.globus.execution.job.create.start jobResource.id=null 
clientSubmission.id=a6206a3c-072f-11dd-862c-0013d4c3b957 
service=ManagedJobFactoryService executable=/bin/date
------- Comment #1 From 2008-04-15 15:24:18 -------
I would add it to the submission-event instead of the create-event:

ts=2008-04-10T13:55:17.372-05:00 
event=org.globus.execution.job.submission.start
jobResource.id=a6f38f20-072f-11dd-92cb-c2d2a177e4c0 
service=ManagedExecutableJobService executable=/bin/date

Would that be ok, too?
------- Comment #2 From 2008-04-15 16:30:45 -------
After some more discussion on our side we decided to add the requested
information plus some more information in the create.end event.

New elements in the create.end event:

jobType: executable for executable jobs, multi for multi jobs
         this element helps to understand the value "null" for executable
         in case the job is a multi job

localResourceManager: ["Fork","PBS","LSF","Condor",...] for executable jobs,
                      "Gram4" for multi jobs

executable: name of the executable for executable jobs (like "/bin/date"),
            "null" for multi jobs


example for a multi job:

ts=2008-04-10T13:55:13.675-05:00  guid=a6e73310-072f-11dd-92cb-c2d2a177e4c0
event=org.globus.execution.job.create.start jobResource.id=null 
clientSubmission.id=a6206a3c-072f-11dd-862c-0013d4c3b957 
service=ManagedJobFactoryService 
ts=2008-04-10T13:55:13.862-05:00  guid=a6e73310-072f-11dd-92cb-c2d2a177e4c0
event=org.globus.execution.job.create.end status=0
jobResource.id=a6f38f20-072f-11dd-92cb-c2d2a177e4c0 
clientSubmission.id=a6206a3c-072f-11dd-862c-0013d4c3b957 
service=ManagedJobFactoryService jobType=executable executable=/bin/date
localResourceManager=PBS


example for a multi-job:

ts=2008-04-10T13:55:13.675-05:00  guid=a6e73310-072f-11dd-92cb-c2d2a177e4c0
event=org.globus.execution.job.create.start jobResource.id=null 
clientSubmission.id=a6206a3c-072f-11dd-862c-0013d4c3b957 
service=ManagedJobFactoryService 
ts=2008-04-10T13:55:13.862-05:00  guid=a6e73310-072f-11dd-92cb-c2d2a177e4c0
event=org.globus.execution.job.create.end status=0
jobResource.id=a6f38f20-072f-11dd-92cb-c2d2a177e4c0 
clientSubmission.id=a6206a3c-072f-11dd-862c-0013d4c3b957 
service=ManagedJobFactoryService jobType=multi executable=null
localResourceManager=Gram4


Comments?
------- Comment #3 From 2008-04-15 16:32:39 -------
sorry, the first example in my comment #2 is of course for an executable job
and not for a multi job
------- Comment #4 From 2012-09-05 11:43:46 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363