IP Library Granted Patent US 7,076,645
Granted Patent B2
US 7,076,645 · App. 10/606,645 · Granted Jul 11, 2006

Method of rebooting a multi-device cluster while maintaining cluster operation

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,076,645
App. No.
10/606,645
Granted
Jul 11, 2006
Kind
B2
Abstract

The present invention is directed at rebooting a cluster while maintaining cluster operation. Cluster operation is automatically maintained during the reboot since at least one member of the cluster stays active during the process. An administrator triggers the reboot process and then does not have to perform any other steps during the reboot process. An algorithm executes which reboots members of the cluster at different times, while always maintaining operation of at least one member of the cluster.

Claims (33)

1. A method for rebooting a cluster, comprising:

initiating a reboot of the cluster;

determining cluster members; and

rebooting each of the cluster members while at least one of the cluster members remains active while the other cluster members are being rebooted, wherein rebooting each of the cluster members comprises removing the cluster member being rebooted and determining when the removed cluster member has been rebooted.

2. The method of claim 1 , further comprising determining an initiating cluster member that initiated the reboot and controlling the rebooting from the initiating cluster member.

3. The method of claim 1 , wherein rebooting each of the cluster members while the at least one of the cluster members remains active while the other cluster members are being rebooted further comprises rebooting the cluster members other than the at least one of the cluster members that remains active in parallel.

4. The method of claim 2 , wherein the at least one of the cluster members that is maintaining normal operation is the initiating cluster member.

5. The method of claim 1 , wherein initiating the reboot of the cluster is performed by a user.

6. The method of claim 1 , wherein determining when the removed cluster member has been rebooted further comprises attempting to re-establish contact wit the removed cluster member.

7. The method of claim 1 , further comprising halting the reboot process when it is determined that an error occurs during the reboot process.

8. A system for rebooting a cluster while maintaining operation of the cluster, comprising:

a network interface configured to communicate with cluster members;

a memory configured to store information relating to the cluster;

a remote management broker (RMB) configured to distribute information to the cluster members; and

a processor configured to perform actions, including:

initiating a reboot of the cluster;

determining the cluster members; and

rebooting each of the cluster members while at least one of the cluster members remains active while the other cluster members are being rebooted, wherein rebooting each of the cluster members comprises removing the cluster member being rebooted and determining when the removed cluster member has been rebooted.

9. The system of claim 8 , further comprising determining an initiating cluster member that initiated the reboot and controlling the rebooting from the initiating cluster member.

10. The system of claim 8 , wherein rebooting each of the cluster members further comprises rebooting each cluster member other than at least one cluster member that remains active in parallel.

11. The system of claim 10 , wherein the at least one of the cluster member is the initiating cluster member.

12. The system of claim 8 , further comprising a user interface used to initiate the reboot of the cluster.

13. The system of claim 8 , wherein determining when the removed cluster member has been rebooted farther comprises attempting to re-establish contact with the removed cluster member.

14. The system of claim 8 , further comprising halting the reboot process when it is determined that an error occurs during the reboot process.

15. An apparatus for rebooting a cluster while maintaining operation of the cluster, comprising:

means for initiating a reboot of the cluster;

means for determining cluster members; and

means for rebooting each of the cluster members while at least one of the cluster members remains active while the other cluster members are being rebooted, wherein the means for rebooting each of the cluster members comprises means for removing the cluster member being rebooted and means for determining when the removed cluster member has been rebooted.

16. The apparatus of claim 15 , wherein determining when the removed cluster member has been rebooted further comprises means for attempting to re-establish contact with the removed cluster member.

17. A computer readable storage medium, comprising executable instructions for performing actions, including:

initiating a reboot of the cluster;

determining cluster members; and

rebooting each of the cluster members while at least one of the cluster members remains active while the other cluster members are being rebooted, wherein rebooting each of the cluster members comprises removing the cluster member being rebooted and determining when the removed cluster member has been rebooted.

Assignments (11)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CORPORATION
Reel/Frame 054486/0422 →
PATENT SECURITY AGREEMENT Recorded Oct 23, 2020
From: RPX CLEARINGHOUSE LLC; RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 054198/0029 →
PATENT SECURITY AGREEMENT Recorded Oct 23, 2020
From: RPX CLEARINGHOUSE LLC; RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 054244/0566 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CORPORATION
To: JEFFERIES FINANCE LLC
Reel/Frame 046486/0433 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2015
From: NOKIA SOLUTIONS AND NETWORKS OY
To: RPX CORPORATION
Reel/Frame 036187/0312 →
CHANGE OF NAME Recorded Nov 19, 2014
From: NOKIA SIEMENS NETWORKS OY
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 034294/0603 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 25, 2008
From: NOKIA CORPORATION
To: NOKIA SIEMENS NETWORKS OY
Reel/Frame 020550/0521 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2008
From: NOKIA INC
To: NOKIA CORPORATION
Reel/Frame 020540/0061 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2003
From: MITTAL, AJAY; XU, LAURA; KONERU, SRIKANTH
To: NOKIA INC.
Reel/Frame 014243/0781 →