Bugzilla – Bug 4944
Multijob resources never yield to memory pressure and can't be destroyed
Last modified: 2012-09-05 11:43:34
You need to
before you can comment on or make changes to this bug.
It seems that when multijob resources set up their subjobs they subscribe to
subjob notifications in such a way that they will never exit memory. In
particular, the multijob resource itself implements implements the notify
callback interface and is registered with the notification consumer manager for
each subjob, which ends up keeping it in memory (this step needs to be
proxied). The other issue is that upon destroy we only remove one of the subjob
notification consumers, which essentially leaves the multijob resource in
Reassigning to current GRAM developer to close/fix as appropriate.
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: