#1039 [RFE] Improve SSSD operation on diskless systems
Closed: wontfix 4 years ago by pbrezina. Opened 12 years ago by nahamu.

By default SSSD stores important data in {{{/var/lib/sss}}} which on many diskless systems is not a an appropriate filesystem type for the job.

Currently the best suggestion is to symlink {{{/dev/shm/sssd}}} to {{{/var/lib/sss}}}
to move that directory into RAM.


For additional information, the reason this does not behave well is that TDB (and by extension: LDB) requires filesystem-level locking that is not available on NFS filesystems. As a result, the possibility for data corruption exists if two transactions are being processed simultaneously.

We need to identify a better way to maintain the LDB on such systems. One approach might be to specify a config option to specify the location of the cache file.

Note: this also applies to the config LDB, not just the cache LDB files.

The are other issues like the fact tdb is mmap()d, and NFS does not guarantee (of course) cache coherency, it can't.
Besides what's the point of a cache for offline use if it breaks when the networks goes away ?

We should probably offer a 'diskless' mode where we store these DBs in a tmpfs we mount on the fly.

Can't do just in-memory DBs because we need to access the same data from multiple processes.

Fields changed

summary: Improve SSSD operation on diskless systems => [RFE] Improve SSSD operation on diskless systems

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.9.0 => SSSD Deferred

Fields changed

rhbz: => 0

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

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

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