SYSTEM AND METHOD FOR SUPPORTING A SERVER-SIDE EVENT MODEL IN A DISTRIBUTED DATA GRID

• US 20130074101A1
• Filed: 05/02/2012
• Published: 03/21/2013
• Est. Priority Date: 09/15/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Oliver, Brian, Arliss, Noah, Gleyzer, Gene, Lee, Robert H.
• Granted Patent: US 9,348,668 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2209/542 Intercept
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A system and method can provide a server-side event model in a distributed data grid with a plurality of cluster nodes storing data partitions distributed throughout the cluster, each cluster node being responsible for a set of partitions. The system can map one or more event interceptors to an event dispatcher placed in the cluster. The one or more event interceptors can handle at least one event dispatched from the event dispatcher, wherein the at least one event is associated with an operation in the distributed data grid. The system can defer completion of the operation in the distributed data grid pending completion of the handling of the at least one event by said one or more event interceptors.

Claims

1. A method for providing a server-side event model in a distributed data grid, said system comprising:

mapping one or more event interceptors to an event dispatcher, wherein the event dispatcher operates to dispatch at least one event associated with an operation in the distributed data grid;

handling, via said one or more event interceptors, the at least one event that is dispatched from the event dispatcher to said one or more event interceptors; and

deferring completion of the operation in the distributed data grid pending completion of the handling of the at least one event by said one or more event interceptors.

2. The method of claim 1, further comprising:

registering one or more event interceptors with a registry that is associated with the distributed data grid.

3. The method of claim 1, further comprising:

defining the at least one event in an event hierarchy.

4. The method of claim 1, further comprising:

providing an interface that allows an end user to implement customized logic for handling events

5. The method of claim 1, further comprising:

chaining said one or more event interceptors together when they are registered for a same event.

6. The method of claim 1, further comprising:

triggering, via the event dispatcher, said one or more event interceptors for events they are registered for.

7. The method of claim 1, further comprising:

executing said one or more event interceptors in an order that they are added to the event dispatcher.

8. The method of claim 1, further comprising:

avoiding blocking a service thread that is responsible for handling all incoming requests and coordinating their execution.

9. The method of claim 1, further comprising:

allowing a pre-commit work flow to know whether the event interceptors should move forward to a commit phase of request processing.

10. The method of claim 1, further comprising:

supporting continuation by posting events to the event dispatcher.

11. A system for providing a server-side event model in a distributed data grid, said system comprising:

an event dispatcher, wherein the event dispatcher operates to dispatch at least one event associated with an operation in the distributed data grid; and

one or more event interceptors, wherein said one or more event interceptors are mapped to the event dispatcher, and wherein said one or more event interceptors operates to handle the at least one event that is dispatched from the event dispatcher to said one or more event interceptors, and

wherein the distributed data grid defers completion of the operation in the distributed data grid pending completion of the handling of the at least one event by said one or more event interceptors.

12. The system of claim 11, further comprising:

a registry that is associated with the distributed data grid, wherein said one or more event interceptors are registered with the registry.

13. The system of claim 11, wherein:

the at least one event is defined in an event hierarchy.

14. The system of claim 11, further comprising:

an interface that allows an end user to implement customized logic for handling events

15. The system of claim 11, wherein:

said one or more event interceptors are chained together when they are registered for a same event.

16. The system of claim 11, wherein:

the event dispatcher triggers said one or more event interceptors for events that they are registered for.

17. The system of claim 11, wherein:

said one or more event interceptors are executed in an order that they are added to the event dispatcher.

18. The system of claim 11, wherein:

the distributed data grid avoids blocking a service thread that is responsible for handling all incoming requests and coordinating their execution.

19. The system of claim 11, wherein:

the distributed data grid allows a pre-commit work flow to know whether the event interceptors should move forward to a commit phase of request processing.

20. The system of claim 11, wherein:

the distributed data grid supports continuation by posting events to a event dispatcher process.