IP Library Granted Patent US 7,925,761
Granted Patent B2
US 7,925,761 · App. 12/495,059 · Granted Apr 12, 2011

System and method for implementing a dead man dependency technique for cluster resources

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,925,761
App. No.
12/495,059
Granted
Apr 12, 2011
Kind
B2
Abstract

Method and system for implementing a dead man dependency technique in a cluster comprising a plurality of interconnected nodes, one of the nodes comprising a cluster resource manager (CRM), and one of the nodes comprising a policy engine (PE), the PE maintaining at least one dependency associated with a first resource executing on one of the nodes. In an embodiment, the method comprises, responsive to a status change of an attribute associated with the first resource, the PE receiving from the CRM an indication of the status change and information regarding a configuration of the cluster; responsive to receipt of the status change indication and the configuration information, identifying by the PE a manner of terminating and migrating the first resource to another one of the nodes; and providing by the PE to the CRM an instruction sequence for causing the identified manner of terminating and migrating the first resource.

Claims (43)

1. A method for implementing a dead man dependency technique in a cluster comprising a plurality of interconnected nodes, one of the nodes comprising a cluster resource manager, and one of the nodes comprising a policy engine, the policy engine maintaining at least one dependency associated with a first resource executing on one of the nodes, the method comprising:

responsive to a status change of an attribute associated with the first resource, the policy engine receiving from the cluster resource manager an indication of the status change;

the policy engine receiving from the cluster resource manager information regarding a configuration of the cluster;

responsive to receipt of the status change indication and the configuration information, identifying by the policy engine a manner of terminating the first resource and migrating the first resource to another one of the nodes; and

providing by the policy engine to the cluster resource manager an instruction sequence for causing the identified manner of terminating the first resource and migrating the first resource to another one of the nodes.

2. The method of claim 1 wherein the attribute includes ownership of a token.

3. The method of claim 2 wherein the status change includes loss of ownership of the token.

4. The method of claim 1 wherein the attribute includes a connection between the node on which the first resource is executing and another node in the cluster.

5. The method of claim 4 wherein the status change includes loss of the connection.

6. The method of claim 1 wherein the configuration information includes configuration of the cluster around the time of the status change of the attribute associated with the first resource.

7. The method of claim 1 ,

wherein the manner of migrating the first resource to another node includes migrating the first resource to a geographically dispersed node;

wherein the dependency includes dependence on a second resource; and

wherein the manner of terminating the first resource includes simultaneously terminating the first resource and the second resource.

8. The method of claim 1 , wherein the policy engine is distributed among more than one of the nodes in the cluster.

9. A system for implementing a dead man dependency technique in a cluster comprising a plurality of interconnected nodes, one of the nodes comprising a cluster resource manager, and one of the nodes comprising a policy engine, the policy engine maintaining at least one dependency with a first resource executing on one of the nodes, the method comprising:

responsive to a status change of an attribute associated with the first resource, means for receiving from the cluster resource manager an indication of the status change;

means for the policy engine receiving from the cluster resource manager information regarding a configuration of the cluster;

responsive to receipt of the status change indication and the configuration information, means for identifying by the policy engine a manner of terminating the first resource and migrating the first resource to another one of the nodes; and

means for providing by the policy engine to the cluster resource manager an instruction sequence for causing the identified manner of terminating the first resource and migrating the first resource to another one of the nodes.

10. The system of claim 9 wherein the attribute includes ownership of a token.

11. The system of claim 10 wherein the status change includes loss of ownership of the token.

12. The system of claim 9 wherein the attribute includes a connection between the node on which the first resource is executing and another node in the cluster.

13. The system of claim 12 wherein the status change includes loss of the connection.

14. The system of claim 9 ,

wherein the configuration information includes configuration of the cluster around the time of the status change of the attribute associated with the first resource;

wherein the manner of migrating the first resource to another node includes means for migrating the first resource to a geographically dispersed node;

wherein the dependency includes dependence on a second resource; and

wherein the manner of terminating the first resource includes simultaneously terminating the first resource and the second resource.

15. A computer program product comprising computer-readable medium having stored thereon instructions executable by a computer for implementing a dead man dependency technique in a cluster comprising a plurality of interconnected nodes, one of the nodes comprising a cluster resource manager, and one of the nodes comprising a policy engine, the policy engine maintaining at least one dependency associated with a first resource executing on one of the nodes, the instructions executable by the computer for causing the computer to:

responsive to a status change of an attribute associated with the first resource, receive by the policy engine from the cluster resource manager an indication of the status change;

receive by the policy engine from the cluster resource manager information regarding a configuration of the cluster;

responsive to receipt of the status change indication and the configuration information, identifying by the policy engine a manner of terminating the first resource and migrating the first resource to another one of the nodes; and

provide from the policy engine to the cluster resource manager an instruction sequence for causing the identified manner of terminating the first resource and migrating the first resource to another one of the nodes.

16. The computer program product of claim 15 the attribute includes ownership of a token.

17. The computer program product of claim 16 wherein the status change includes loss of ownership of the token.

18. The computer program product of claim 15 wherein the attribute includes a connection between the node on which the first resource is executing and another node in the cluster.

19. The computer program product of claim 18 wherein the status change includes loss of the connection.

20. The computer program product of claim 19 ,

wherein the configuration information includes configuration of the cluster around the time of the status change of the attribute associated with the first resource;

wherein the manner of migrating the first resource to another node includes migrating the first resource to a geographically dispersed node;

wherein the dependency includes dependence on a second resource; and

wherein the manner of terminating the first resource includes simultaneously terminating the first resource and the second resource.

Assignments (19)
RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.)
Reel/Frame 062623/0009 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME - 042388/0386 AND REEL/FRAME - 044183/0577 Recorded Mar 18, 2019
From: JPMORGAN CHASE BANK, N.A.
To: SUSE LLC
Reel/Frame 048628/0221 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME - : 044183/0718 Recorded Mar 18, 2019
From: JPMORGAN CHASE BANK, N.A.
To: SUSE LLC
Reel/Frame 048628/0436 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2019
From: MICRO FOCUS SOFTWARE INC.
To: SUSE LLC
Reel/Frame 048379/0548 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TO CORRECT TYPO IN APPLICATION NUMBER 10708121 WHICH SHOULD BE 10708021 PREVIOUSLY RECORDED ON REEL 042388 FRAME 0386. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE OF SUCCESSION OF AGENCY. Recorded Jul 26, 2018
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 048793/0832 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
NOTICE OF SUCCESSION OF AGENCY Recorded May 2, 2017
From: BANK OF AMERICA, N.A., AS PRIOR AGENT
To: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT
Reel/Frame 042388/0386 →
CHANGE OF NAME Recorded Sep 13, 2016
From: NOVELL, INC.
To: MICRO FOCUS SOFTWARE INC.
Reel/Frame 040020/0703 →
SECURITY INTEREST Recorded May 13, 2015
From: MICRO FOCUS (US), INC.; BORLAND SOFTWARE CORPORATION; ATTACHMATE CORPORATION; NETIQ CORPORATION; NOVELL, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 035656/0251 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0216 Recorded Nov 24, 2014
From: CREDIT SUISSE AG
To: NOVELL, INC.
Reel/Frame 034470/0680 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0316 Recorded Nov 24, 2014
From: CREDIT SUISSE AG
To: NOVELL, INC.
Reel/Frame 034469/0057 →
GRANT OF PATENT SECURITY INTEREST SECOND LIEN Recorded May 23, 2012
From: NOVELL, INC.
To: CREDIT SUISSE AG, AS COLLATERAL AGENT
Reel/Frame 028252/0316 →
GRANT OF PATENT SECURITY INTEREST FIRST LIEN Recorded May 23, 2012
From: NOVELL, INC.
To: CREDIT SUISSE AG, AS COLLATERAL AGENT
Reel/Frame 028252/0216 →
RELEASE OF SECURITY INTEREST IN PATENTS FIRST LIEN (RELEASES RF 026270/0001 AND 027289/0727) Recorded May 22, 2012
From: CREDIT SUISSE AG, AS COLLATERAL AGENT
To: NOVELL, INC.
Reel/Frame 028252/0077 →
RELEASE OF SECURITY IN PATENTS SECOND LIEN (RELEASES RF 026275/0018 AND 027290/0983) Recorded May 22, 2012
From: CREDIT SUISSE AG, AS COLLATERAL AGENT
To: NOVELL, INC.
Reel/Frame 028252/0154 →
GRANT OF PATENT SECURITY INTEREST (SECOND LIEN) Recorded May 13, 2011
From: NOVELL, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 026275/0018 →
GRANT OF PATENT SECURITY INTEREST Recorded May 12, 2011
From: NOVELL, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 026270/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 30, 2009
From: MAROWSKY-BREE, LARS; BEEKHOF, ANDREW JOHN
To: NOVELL, INC.
Reel/Frame 022895/0089 →