Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#1583 closed defect (fixed)

Project object usage in spool should only be updated if it has changed

Reported by: markdixon Owned by: Mark Dixon <m.c.dixon@…>
Priority: normal Milestone:
Component: sge Version: 8.1.8
Severity: minor Keywords:
Cc:

Description

From the commit:

Fix xxx only update project usage in spool if it has changed

Like user objects, project objects used to only be updated in the spool
if they had changed. Monster change AA-2007-08-20-0 splitted user and
project usage into separate data structures but neglected to filter
project objects on scheduling sequence number.

This commit causes project objects in the spool only to be updated if
they have changed, instead of every scheduling interval.

Commit prepared against 8.1.9

Note that usage stored in the spool can still end up considerably out of date due to #1554.

Attachments (1)

0001-Fix-1583-only-update-project-usage-in-spool-if-it-ha.patch (2.2 KB) - added by markdixon 3 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 Changed 3 years ago by Mark Dixon <m.c.dixon@…>

  • Owner set to Mark Dixon <m.c.dixon@…>
  • Resolution set to fixed
  • Status changed from new to closed

In 4915/sge:

Fix #1583 only update project usage in spool if it has

comment:2 Changed 3 years ago by Mark Dixon <m.c.dixon@…>

In 4925/sge:

Fix #1583 only update project usage in spool if it has changed
Like user objects, project objects used to only be updated in the
spool
if they had changed. Monster change AA-2007-08-20-0 splitted user and
project usage into separate data structures but neglected to filter
project objects on scheduling sequence number.

This commit causes project objects in the spool only to be updated if
they have changed, instead of every scheduling interval.

[Duplicate changeset to correct missing log.]

Note: See TracTickets for help on using tickets.