Opened 14 years ago

Closed 8 years ago

#408 closed enhancement (fixed)

IZ2205: new option for qacct to select jobs based on their end times

Reported by: heywood Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0u8
Severity: minor Keywords: clients


[Imported from gridengine issuezilla]

        Issue #:      2205             Platform:     All           Reporter: heywood (heywood)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.0u8            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    ernst (ernst)
      QA Contact:     roland
       * Summary:     new option for qacct to select jobs based on their end times
   Status whiteboard:

     Issue 2205 blocks:
   Votes for issue 2205:

   Opened: Tue Mar 6 09:27:00 -0700 2007 

The man page for qacct says that the –b, -e, and –d options select jobs based on
start times. It would be nice an option could be added to qacct in the future so
that they select jobs based on their end times. The reason if that if you do
periodic qacct dumps using –b, -e, and/or –d to specify periods, you will only
catch jobs which begin and end in the same period (since a job is only written
to the accounting files when the job ends).

In other words, if a job ends in a period (say in the last day: “-d 1”) but
started 2 days ago, “qacct –d 1” will not account for it. And if I ran “qacct –d
1” yesterday, the job is not yet in the accounting file.

If job selection were possible by job end time instead of start time this
wouldn’t be a problem.

   ------- Additional comments from andreas Mon Mar 12 08:34:33 -0700 2007 -------
Moved to clients.

   ------- Additional comments from templedf Mon Jan 12 17:12:43 -0700 2009 -------
Changed summary to be more descriptive.

Change History (1)

comment:1 Changed 8 years ago by dlove

  • Resolution set to fixed
  • Severity set to minor
  • Status changed from new to closed

Should have been closed by [4317]

Note: See TracTickets for help on using tickets.