System and method for invalidating data in a hierarchy of caches

• US 7,143,244 B2
• Filed: 12/02/2003
• Issued: 11/28/2006
• Est. Priority Date: 09/05/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Liu, Xiang, Ling, Shu, Jacobs, Lawrence, Goell, Fredric
• Primary Examiner(s): Padmanabhan, Mano
• Assistant Examiner(s): Doan, Duc T
• Application Number:
  US10/727,308
• Publication Number:
  US 20050055508A1
• Time in Patent Office: 1,092 Days
• Field of Search: None
• US Class Current: 711/141
• CPC Class Codes: G06F 12/0808 with cache invalidating means G06F12/0815 takes precedence

Abstract

A system and method for communicating a side effect of one data request, or other event, as part of a response to another data request or event. The side effect may include notification of the invalidation of cached data, from an upstream cache to a downstream cache. The upstream cache may store invalidation notifications as they are generated or received, and as responses to data requests are sent downstream, piggyback or merge one or more notifications with a response. This scheme avoids the need to open separate communication connections using specified invalidation accounts and passwords.

Claims

1. A computer-implemented method of piggybacking a message invalidating cached data on a response to a data request, the method comprising:

in a hierarchy of caches, passing a data request toward a data server;

at an upstream cache, detecting the invalidation of a set of data cached on one or more downstream caches, including a first downstream cache, wherein the set of data includes no data requested in the data request;

in a response to the data request, including an invalidation message to invalidate the set of data with the response to the first downstream cache; and

forwarding the response including the invalidation message toward the first downstream cache.

2. The method of claim 1, further comprising:

adding the set of data to a list of data to be invalidated on downstream caches.

3. The method of claim 2, further comprising:

removing the set of data from the list of data after data request responses including messages to invalidate the set of data have been forwarded to each of the one or more downstream caches.

4. The method of claim 1, wherein the set of data includes data requested in the data request.

5. The method of claim 1, further comprising, in the first downstream cache:

receiving the response;

retrieving the message;

invalidating the set of data if the set of data is cached on the first downstream cache; and

forwarding the response toward a second downstream cache.

6. The method of claim 1, further comprising, in the first downstream cache:

receiving the response;

removing the message from the response;

invalidating the set of data if the set of data is cached on the first downstream cache; and

serving the response to a client that initiated the data request.

7. The method of claim 1, wherein said detecting comprises:

receiving an invalidation message originated by the data server.

8. The method of claim 1, wherein said detecting comprises:

receiving a manual notification of the invalidation of the set of data.

9. The method of claim 1, wherein the data request is initiated by a first requestor and the response is targeted to a different requestor.

10. The method of claim 1, wherein the upstream cache is a cache local to the data server.

11. The method of claim 1, wherein the upstream cache and the first downstream cache are members of a cache cluster.

12. A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of piggybacking a message invalidating cached data on a response to a data request, the method comprising:

in a hierarchy of caches, passing a data request toward a data server;

at an upstream cache, detecting the invalidation of a set of data cached on one or more downstream caches, including a first downstream cache, wherein the set of data includes no data requested in the data request;

in a response to the data request, including an invalidation message to invalidate the set of data with the response to the first downstream cache; and

forwarding the response including the invalidation message toward the first downstream cache.

13. An automated method of asynchronously communicating a side effect of a first data request in a response to a second data request, the method comprising:

in a computing environment comprising a data server and a plurality of caches, processing a first data request to produce a first response;

identifying a side effect of the first data request;

communicating the side effect to a first cache upstream of one or more downstream caches;

at the first cache;

identifying a second response to a second data request;

including notification of the side effect in the second response, wherein the side effect is unrelated to the second response; and

forwarding the second response including the notification of the side effect toward a first downstream cache; and

at the first downstream cache, applying the side effect.

14. The method of claim 13, wherein the side effect comprises invalidation of data cached on the first downstream cache.

15. The method of claim 13, wherein the side effect comprises propagation of cache configuration data.

16. The method of claim 13, wherein the side effect comprises a password.

17. The method of claim 13, wherein the side effect comprises an update to a cache program.

18. The method of claim 13, wherein the side effect comprises a replacement cache program.

19. The method of claim 13, wherein said applying the side effect at the first downstream cache comprises applying the side effect after forwarding the second response.

20. The method of claim 19, wherein said applying the side effect at the first downstream cache comprises applying the side effect before a specified event.

21. The method of claim 13, further comprising:

at the first cache, tracking which of the one or more downstream caches has been notified of the side effect;

wherein a downstream cache other than the first downstream cache receives notification of the side effect in a communication other than the second response.

22. A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of asynchronously communicating a side effect of a first data request in a response to a second data request, the method comprising:

in a computing environment comprising a data server and a plurality of caches, processing a first data request to produce a first response;

identifying a side effect of the first data request;

communicating the side effect to a first cache upstream of one or more downstream caches;

at the first cache;

identifying a second response to a second data request;

including notification of the side effect in the second response, wherein the side effect is unrelated to the second response; and

forwarding the second response including the notification of the side effect toward a first downstream cache; and

at the first downstream cache, applying the side effect.

23. A system for piggybacking notification of a side effect of a first data request in a response to a second data request, comprising:

a data server configured to serve data in response to data requests;

one or more downstream caches configured to cache the served data; and

an upstream cache logically located between the data server and the one or more downstream caches, wherein the upstream cache is configured to include, in a response to one data request from the downstream cache, notification of a first side effect of a different data request, wherein the side effect is unrelated to the response to one data request.

24. The system of claim 23, wherein the upstream cache comprises:

a subscription table identifying each of the one or more downstream caches; and

a list of side effects that the one or more downstream caches are to be notified of.

25. The system of claim 24, wherein the upstream cache is further configured to remove the first side effect from the list of side effects after each of the one or more downstream caches have been notified of the first side effect.

26. The system of claim 23, wherein the first side effect comprises the invalidation of a set of data.

27. The system of claim 23, wherein:

the one or more downstream caches include a final downstream cache coupled to a client that initiated the one data request; and

the final downstream cache is configured to remove the notification of the first side effect of the different data request from the response before serving the response to the client.

28. The system of claim 23, wherein the upstream cache is a local cache of the data server.