Projects
Wiki     Timeline     Roadmap     Browse Source     View Tickets     New Ticket     Search

Ticket #119 (closed Defect: Software changed)

Opened 4 years ago

Last modified 3 years ago

Server keeps reloading empty OD data

Reported by: wsanchez@… Owned by: wsanchez@…
Priority: 3: Important Milestone: CalendarServer-1.0
Component: Calendar Server Severity: Performance
Keywords: Cc:

Description

We have an optimization in the server which we keep a timed cache of OpenDirectory data for a while, but in order to avoid wiping our data store out when OD hiccups, we don't reset the cache timer if we get back an empty set for a record type.

In cases where there really is no data for that record type, this means the timed cache isn't used, even though is should.

Change History

Changed 4 years ago by cdaboo@…

PyOpenDirectory now raises exception when there is a an error, so in theory we could rely on that to determinethe error state. However, we need to check that when using the /Search node, if a particular LDAP node is unreachable, that an error is generated rather than it returning results for all the other working nodes. We need to make sure that a failure in any node explicitly included in the /Search results in a failure for the whole.

Another option might be to go with an explicit LDAP node rather than /Search. The one benefit of that is that it avoids problems with figuring out whether users from different LDAP servers need to be in different "realms" on the calendar server.

Changed 3 years ago by wsanchez@…

  • status changed from new to closed
  • resolution set to fixed

Changed 3 years ago by wsanchez@…

  • milestone changed from Preview 1 to Version One

Milestone Preview 1 deleted

Note: See TracTickets for help on using tickets.