Distributed and optimized garbage collection of exported data objects
First Claim
Patent Images
1. A system for managing distributed client-server object handles, the system comprising:
- a remote client computer containing a first one or more hardware processors;
a server computer containing a second one or more hardware processors;
the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including;
creating a remote object handle manager;
establishing a connection with a remote query processor on the server computer;
establishing a liveness indication system with the remote query processor;
receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object;
the remote object handle manager constructing the remote object handle;
the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies;
the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object;
the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including;
creating a remote query processor, the remote query processor performing remote query processor operations including;
creating an exported object handle manager;
sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and
preserving a liveness of the exported object at least until any of the following events;
receipt of the release notification from the remote object handle manager; and
the liveness indication system determines the remote client computer is not connected,the first operations further including;
the remote object handle manager monitoring a handle cleanup reference queue;
after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method;
the handle cleanup reference cleanup method decrementing a remote object handle reference count on a second remote object handle associated with the handle cleanup reference;
the handle cleanup reference cleanup method removing the handle cleanup reference from a set of handle cleanup references monitored by the remote object handle manager;
when the remote object handle reference count after decrementing is zero, sending a digital message to the remote query processor to release an associated exported object handle; and
when the remote object handle reference count after decrementing is greater than zero, maintaining a strong reference to the second remote object handle in order to ensure liveness for dependent client objects.
3 Assignments
0 Petitions
Accused Products
Abstract
Described are methods, systems and computer readable media for distributed and optimized garbage collection of remote and exported object handle links to update propagation graph nodes.
521 Citations
29 Claims
-
1. A system for managing distributed client-server object handles, the system comprising:
-
a remote client computer containing a first one or more hardware processors; a server computer containing a second one or more hardware processors; the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including; creating a remote object handle manager; establishing a connection with a remote query processor on the server computer; establishing a liveness indication system with the remote query processor; receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object; the remote object handle manager constructing the remote object handle; the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies; the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object; the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including; creating a remote query processor, the remote query processor performing remote query processor operations including; creating an exported object handle manager; sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and preserving a liveness of the exported object at least until any of the following events; receipt of the release notification from the remote object handle manager; and the liveness indication system determines the remote client computer is not connected, the first operations further including; the remote object handle manager monitoring a handle cleanup reference queue; after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method; the handle cleanup reference cleanup method decrementing a remote object handle reference count on a second remote object handle associated with the handle cleanup reference; the handle cleanup reference cleanup method removing the handle cleanup reference from a set of handle cleanup references monitored by the remote object handle manager; when the remote object handle reference count after decrementing is zero, sending a digital message to the remote query processor to release an associated exported object handle; and when the remote object handle reference count after decrementing is greater than zero, maintaining a strong reference to the second remote object handle in order to ensure liveness for dependent client objects.
-
-
2. A system for managing distributed client-server object handles, the system comprising:
-
a remote client computer containing a first one or more hardware processors; a server computer containing a second one or more hardware processors; the remote client computer containing a first computer readable data storage device coupled to the first one or more hardware processors, the first computer readable data storage device having stored thereon software instructions that, when executed by the first one or more hardware processors, cause the first one or more hardware processors to perform first operations including; creating a remote object handle manager; establishing a connection with a remote query processor on the server computer; establishing a liveness indication system with the remote query processor; receiving, from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object; the remote object handle manager constructing the remote object handle; the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies; the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object; the server computer containing a second computer readable data storage device coupled to the second one or more hardware processors, the second computer readable data storage device having stored thereon software instructions that, when executed by the second one or more hardware processors, cause the second one or more hardware processors to perform second operations including; creating a remote query processor, the remote query processor performing remote query processor operations including; creating an exported object handle manager; sending the exported object handle information including the exported object identifier from the exported object handle manager to the remote client computer; and preserving a liveness of the exported object at least until any of the following events; receipt of the release notification from the remote object handle manager; and the liveness indication system determines the remote client computer is not connected, wherein the preserving a liveness of the exported object comprises; maintaining a reference count associated with the exported object; decrementing the reference count associated with the exported object after receipt of the release notification from the remote object handle manager; decrementing the reference count associated with the exported object after the liveness indication system determines the remote client computer is not connected; when the reference count associated with the exported object after decrementing is zero, removing a strong reference to the exported object from the exported object handle; and when the reference count associated with the exported object after decrementing is greater than zero, maintaining the strong reference to the exported object from the exported object handle.
-
-
3. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:
-
creating a remote object handle manager; establishing a connection with a remote query processor on a server computer; establishing a liveness indication system with the remote query processor; receiving from the remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object; the remote object handle manager constructing the remote object handle; the remote object handle manager monitoring liveness of all client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies; the remote object handle manager sending a release notification to the remote query processor including the exported object identifier, after no client objects depend on the exported object; creating a remote query processor, the remote query processor performing remote query processor operations including; creating an exported object handle manager; sending the exported object handle information including the exported object identifier from the exported object handle manager to a remote client; and preserving a liveness of the exported object until receipt of the release notification from the remote object handle manager or until the liveness indication system determines the remote client is not connected, wherein the preserving a liveness of the exported object comprises; maintaining a reference count associated with the exported object; decrementing the reference count associated with the exported object after receipt of the release notification from the remote object handle manager; decrementing the reference count associated with the exported object after the liveness indication system determines the remote client computer is not connected; when the reference count associated with the exported object after decrementing is zero, removing a strong reference to the exported object from the exported object handle; and when the reference count associated with the exported object after decrementing is greater than zero, maintaining the strong reference to the exported object from the exported object handle.
-
-
4. A system comprising:
-
one or more hardware processors; and a computer readable data storage device coupled to the one or more hardware processors, the computer readable data storage device having stored thereon software instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations including; receiving, from a remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object; constructing the remote object handle; monitoring liveness of client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies, the monitoring including; maintaining a remote object handle reference count on the remote object handle, and decrementing the remote object handle reference count after a dependent client object no longer depends on the remote object handle; when the remote object handle reference count is zero after the decrementing, sending a release notification to the remote query processor to release an associated exported object handle, the release notification including the exported object identifier, after no client objects depend on the exported object; monitoring a handle cleanup reference queue; and after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method, the handle cleanup reference being associated with the remote object handle, the handle cleanup reference cleanup method performing cleanup operations including; performing the decrementing of the remote object handle reference count on the remote object handle associated with the handle cleanup reference, and removing the handle cleanup reference from a plurality of handle cleanup references being monitored. - View Dependent Claims (5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A method comprising:
-
receiving, from a remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object; constructing the remote object handle; monitoring liveness of client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies, the monitoring including; maintaining a remote object handle reference count on the remote object handle, and decrementing the remote object handle reference count after a dependent client object no longer depends on the remote object handle; determining that the remote object handle reference count is zero after the decrementing; in response to the determining, sending a release notification to the remote query processor to release an associated exported object handle, the release notification including the exported object identifier, after no client objects depend on the exported object; monitoring a handle cleanup reference queue; determining that a handle cleanup reference appears in the handle cleanup reference queue, the handle cleanup reference being associated with the remote object handle; and in response to the determining that the handle cleanup reference appears in the handle cleanup reference queue invoking a handle cleanup reference cleanup method, the handle cleanup reference cleanup method performing cleanup operations including; performing the decrementing of the remote object handle reference count on the remote object handle associated with the handle cleanup reference, and removing the handle cleanup reference from a plurality of handle cleanup references being monitored. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20)
-
-
21. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:
-
receiving, from a remote query processor, exported object handle information to construct a remote object handle, including an exported object identifier, the exported object identifier identifying an exported object; constructing the remote object handle; monitoring liveness of client objects that depend on the remote object handle, the remote object handle depending on the exported object and indirectly depending on the exported object'"'"'s dependencies, the monitoring including; maintaining a remote object handle reference count on the remote object handle, and decrementing the remote object handle reference count after a dependent client object no longer depends on the remote object handle; when the remote object handle reference count is zero after the decrementing, sending a release notification to the remote query processor to release an associated exported object handle, the release notification including the exported object identifier, after no client objects depend on the exported object; monitoring a handle cleanup reference queue; and after a handle cleanup reference appears in the handle cleanup reference queue, invoking a handle cleanup reference cleanup method, the handle cleanup reference being associated with the remote object handle, the handle cleanup reference cleanup method performing cleanup operations including; performing the decrementing of the remote object handle reference count on the remote object handle associated with the handle cleanup reference, and removing the handle cleanup reference from a plurality of handle cleanup references being monitored. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29)
-
Specification