#1968 Memory grows if subdomain goes away in the AD provider
Closed: Fixed None Opened 9 years ago by jhrozek.

If the AD provider detects that a subdomain went away, we currently only remove a sdap_domain structure from a linked list to deactivate it. But the structure stays in memory potentially indefinitely. Normally this is not a big deal because a) subdomains do not disappear that often and b) sssd restart would fix the issue. But nevertheless, it is a bug and should be fixed.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.1

Fields changed

rhbz: => 0

Moving tickets that didn't make 1.10.1 to the 1.10.2 bucket.

Moving tickets that didn't make 1.10.1 to 1.10.2

milestone: SSSD 1.10.1 => SSSD 1.10.2

Fields changed

owner: somebody => okos
status: new => assigned

This might not be very easy to fix, but I'm interested in other approaches. One thing I was considering is
to terminate all domain lookups (cancel their requests with EIO or similar) that use the subdomain that went away. We would lose the results, which is completely acceptable I think given that there is no way to reference the domain anymore with lookups.

The approach above would require some kind of backchannel towards the sssd_be that would enumerate the be_req structures and cancel those that point to the subdomain that no longer exists.

Or we can take first step to encapsulate be_ctx and create a getter for domain, duplicating it.

Fields changed

patch: 0 => 1

The patch is on list but since we've moved all supported releases to 1.11.x, I'd rather not add additional non trivial fix to 1.10. Moving to 1.11.2

milestone: SSSD 1.10.2 => SSSD 1.11.2

Fields changed

owner: okos => pbrezina
status: assigned => new

Fields changed

priority: major => minor

Fields changed

status: new => assigned

The patches are on the list but need revision. I don't want to delay 1.11.2 any longer.

milestone: SSSD 1.11.2 => SSSD 1.11.3

The issues were resolved. Pulling back to 1.11.2

milestone: SSSD 1.11.3 => SSSD 1.11.2

- da34cf4
- 44e8e96
- 6e3f797
- 4d6edda
- d19e343
- a09ef85
- 8464054
- bc30ce9
- 92eb572
- cd4cc8d
- d71b1a2
- 8d368a6
- 3acf081
- bc0d2a4
- e1ac589
- 6f31312
- f6dee70
- ed01e2d
- 3b37e5e
- 4bee540

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => N/A just a bugfix

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.11.2

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3010

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.