#2607 sssd should not always read entire autofs map from ldap
Opened 4 years ago by henson. Modified 2 years ago

Currently sssd always reads the entire autofs map from ldap, even when that is not necessary. This makes using sssd with large maps infeasible.

Rather than always reading the entire map, sssd should lookup individual entries as needed when getautomntbyname is called, and only pull in the entire map when getautomntent is called.

This is equivalent to how autofs works with its native ldap backend and will be much more efficient for indirect maps as well as allowing large maps to work without excessive load and resource utilization.

It appears the sss autofs backend does not need any modification, as it already passes through getautomntbyname, the only change is on the sssd side.


Legitimate request, but so far out of scope of 1.13

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Fields changed

milestone: SSSD 1.14 beta => SSSD 1.14.0
sensitive: => 0

Unfortunately the autofs responder/provider work is still not started and we need to release the 1.14 version soon. Therefore, I'm bumping this ticket to the next version.

milestone: SSSD 1.14.0 => SSSD 1.16 beta

Fields changed

milestone: SSSD Future releases (no date set yet) => SSSD 1.15.2

Metadata Update from @henson:
- Issue set to the milestone: SSSD 1.15.2

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: None
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.2 (was: SSSD 1.15.3)

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: cleanup-one-sixteen

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue untagged with: cleanup-one-sixteen
- Issue tagged with: cleanup-future

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue untagged with: cleanup-future
- Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.15.4)

2 years ago

Login to comment on this ticket.

Metadata