« Return to Thread: Broadening the scope of the negative connection cache

Re: Broadening the scope of the negative connection cache

by simo-7 :: Rate this Message:

Reply to Author | View in Thread

On Tue, 2008-05-13 at 10:06 -0500, Gerald (Jerry) Carter wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> simo wrote:
>
> >> PS: I do believe that Winbind's idmap cache needs to be cleaned
> >> up.  For example, caching the forward and reverse map entries
> >> should be in a single transaction.
> >
> > We should also make the cache be readable by any winbindd process too,
> > so that we save some round trips, it was not done in initial design to
> > keep it simpler, but it is time to IMO.
>
> That's a different issue.  In general the design should be
> that tha parent winbindd process always hits cache first
> and only calls out to a child process when the cache is
> empty or expired.  This is more in line with the original
> dual-daemon design Tridge implemented.  Which I think
> would work really well with the state machine model we
> have now.
>
> So it's not just the idmap cache that needs to be readable,
> but the entire cache manager should be moved to the parent.

That's what I meant.

Simo.

--
Simo Sorce
Samba Team GPL Compliance Officer <simo@...>
Senior Software Engineer at Red Hat Inc. <ssorce@...>

 « Return to Thread: Broadening the scope of the negative connection cache