#1400 [RFE] In memory fast cache should support negative caching
Closed: wontfix 4 months ago by pbrezina. Opened 8 years ago by simo.

When opening a tarball apparently tar keeps querying the nsswitch interface for each file it needs to create to set the owner.
It seem it doesn't cache so if the owner is unknown it will hit the sssd_nss pipe for each file slowing down operations considerably.

A very short time Negative cache with shared memory cache would probably solve this and other bad behaviour neatly.


This is a performance enhancement.

description:
When opening a tarball apprently tar keeps querying the nsswitch interface for each file it needs to create to set the owner.
It seem it doesn't cache so if the owner is unknown it will hit the sssd_nss pipe for each file slowing down operations considerably.

A very short time Negative cache with shared memory cache would probably solve this and other bad behaviour neatly.
=>
When opening a tarball apparently tar keeps querying the nsswitch interface for each file it needs to create to set the owner.
It seem it doesn't cache so if the owner is unknown it will hit the sssd_nss pipe for each file slowing down operations considerably.

A very short time Negative cache with shared memory cache would probably solve this and other bad behaviour neatly.

milestone: NEEDS_TRIAGE => SSSD 1.10.0
summary: opening a tar archive may be slow do tue unknown user queries => [RFE] In memory fast cache should support negative caching
type: defect => enhancement

Fields changed

rhbz: => todo

Fields changed

proposed_priority: => Important

Cleaning the 1.10 milestones before putting tickets into it.

milestone: SSSD 1.10.0 => Temp milestone

Moving planned features and bug fixes into the 1.10 bucket.

milestone: Temp milestone => SSSD 1.10.0

Fields changed

milestone: SSSD 1.10.0 => Temp milestone

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: Temp milestone => SSSD 1.10 beta

Fields changed

priority: major => minor

Fields changed

priority: minor => major

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 0

We will take a look at memcache in 1.13, but perhaps not at the negcache, not sure..

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
review: => 0

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

This makes total sense and might be a good stretch goal for 1.14.

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

Fields changed

selected: Not need => May

Actually, the tickets to implement SID caching in memcache should come first..

milestone: SSSD 1.14 backlog => SSSD Patches welcome

Metadata Update from @simo:
- Issue set to the milestone: SSSD Patches welcome

3 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 months 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/2442

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.

Metadata