#1198 Change behavior of clients once shared memory cache is enabled
Closed: wontfix 7 months ago by pbrezina. Opened 8 years ago by simo.

Right now we do not close the socket used to contact the responders from the clients. This is to avoid overheads when many operations are performed.

Once the shared memory cache is implemented the number of times we will need to contact the responders should be dramatically reduced, therefore we should try to close the socket after each operation. An exception could be enumerations, which spans multiple calls/operations.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9 beta
priority: major => minor
type: defect => enhancement

Fields changed

rhbz: => 0

Fields changed

milestone: SSSD 1.9 beta => SSSD 1.10 beta

Fields changed

proposed_priority: => Optional

Cleaning the 1.10 milestones before putting tickets into it.

milestone: SSSD 1.10 beta => Temp milestone

Fields changed

milestone: Temp milestone => SSSD 1.11 beta

This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.

Fields changed

milestone: SSSD 1.11 beta => SSSD 1.12 beta

We haven't seen any issues with the current behaviour so far. We should reconsider when we work on the local accounts feature.

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
mark: => 0
milestone: SSSD 1.14 beta => SSSD 1.15 beta
review: => 0
selected: =>
sensitive: => 0

This is not possible really unless the memory cache implements more name format types like FQDN.

review: 0 => 1
selected: => May

Until all possible name formats are implemented in the memory cache, I'm moving the request to patches welcome.

milestone: SSSD Future releases (no date set yet) => 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)

7 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/2240

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.