IP Library Granted Patent US 12,572,432
Granted Patent B2
US 12,572,432 · App. 18/639,147 · Granted Mar 10, 2026

Cluster redundancy method when using low reliability nodes

Inventors: Takanobu Suzuki (San Jose, CA); Hiroyuki Osaki (Los Gatos, CA)
Assignee: HITACHI VANTARA, LTD.
G06F11/1666G06F11/076G06F11/0772
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 12,572,432
App. No.
18/639,147
Granted
Mar 10, 2026
Kind
B2
Abstract

Management of storage clusters involving high reliability and low reliability nodes, wherein active and standby pairs are chained across the high reliability and low reliability nodes such that each of the high reliability and low reliability nodes involve volumes of the active and standby pairs, including, for receipt of a request for volume creation with a specified volume application, selecting a storage cluster from the storage clusters to create the volume with the specified volume application based on policy of the volume and existence of spot instances in the storage clusters, the determining involving, for the policy of the volume indicative of a development volume, selecting the storage cluster having one or more spot instances from the storage clusters; and for the policy of the volume indicative of a production volume, selecting the storage cluster having no spot instances from the storage clusters.

Claims (40)

1 . A method of managing storage clusters involving high reliability and low reliability nodes, wherein active and standby pairs are chained across the high reliability and low reliability nodes such that each of the high reliability and low reliability nodes involve volumes of the active and standby pairs, the method comprising:

for receipt of a request for volume creation with a specified volume application:

selecting a storage cluster from the storage clusters for volume creation with the specified volume application based on volume policy and existence of spot instances in the storage clusters creating the volume; wherein the selecting comprises:

for the policy of the volume indicative of a development volume, selecting the storage cluster having one or more spot instances from the storage clusters; and

for the policy of the volume indicative of a production volume, selecting the storage cluster having no spot instances from the storage clusters.

2 . The method of claim 1 , further comprising, for no storage cluster being available based on the policy of the volume, creating a new cluster.

3 . The method of claim 1 , wherein for multiple storage clusters with the one or more spot instances being selectable for the development volume, selecting a volume based on a volume criteria.

4 . The method of claim 1 , further comprising for an occurrence of a node failure and for a type of a node associated with the node failure being a spot instance:

creating a new spot instance;

for the new spot instance creation being successful, replacing the node associated with the node failure with the created spot instance; and

for the new spot instance creation not being successful, waiting a constant time until retrying creation of the new spot instance while a number of retries is below a threshold.

5 . The method of claim 1 , further comprising, for the policy of the volume indicative of the development volume, determining whether the storage cluster having one or more spot instances from the storage clusters have sufficient capacity to meet the request for the volume creation; and

for the capacity determined to be insufficient, generating a warning to a storage provider associated with the request for the volume creation.

6 . A non-transitory computer readable medium, storing instructions for executing a process for managing storage clusters involving high reliability and low reliability nodes, wherein active and standby pairs are chained across the high reliability and low reliability nodes such that each of the high reliability and low reliability nodes involve volumes of the active and standby pairs, the instructions comprising:

for receipt of a request for volume creation with a specified volume application:

selecting a storage cluster from the storage clusters for volume creation with the specified volume application based on volume policy and existence of spot instances in the storage clusters creating the volume; wherein the selecting comprises:

for the policy of the volume indicative of a development volume, selecting the storage cluster having one or more spot instances from the storage clusters; and

for the policy of the volume indicative of a production volume, selecting the storage cluster having no spot instances from the storage clusters.

7 . The non-transitory computer readable medium of claim 6 , wherein the instructions further comprising, for no storage cluster being available based on the policy of the volume, creating a new cluster.

8 . The non-transitory computer readable medium of claim 6 , wherein for multiple storage clusters with the one or more spot instances being selectable for the development volume, selecting a volume based on a volume criteria.

9 . The non-transitory computer readable medium of claim 6 , further comprising for an occurrence of a node failure and for a type of a node associated with the node failure being a spot instance:

creating a new spot instance;

for the new spot instance creation being successful, replacing the node associated with the node failure with the created spot instance; and

for the new spot instance creation not being successful, waiting a constant time until retrying creation of the new spot instance while a number of retries is below a threshold.

10 . The non-transitory computer readable medium of claim 6 , further comprising, for the policy of the volume indicative of the development volume, determining whether the storage cluster having the one or more spot instances from the storage clusters have sufficient capacity to meet the request for the volume creation; and

for the capacity determined to be insufficient, generating a warning to a storage provider associated with the request for the volume creation.

11 . A management server, configured to manage storage clusters involving high reliability and low reliability nodes, wherein active and standby pairs are chained across the high reliability and low reliability nodes such that each of the high reliability and low reliability nodes involve volumes of the active and standby pairs, the management server comprising:

a processor, configured to:

for receipt of a request for volume creation with a specified volume application:

select a storage cluster from the storage clusters for volume creation with the specified volume application based on volume policy and existence of spot instances in the storage clusters creating the volume, by:

for the policy of the volume indicative of a development volume, select the storage cluster having one or more spot instances from the storage clusters; and

for the policy of the volume indicative of a production volume, select the storage cluster having no spot instances from the storage clusters.

12 . The management server of claim 11 , wherein the processor is further configured to, for no storage cluster being available based on the policy of the volume, create a new cluster.

13 . The management server of claim 11 , wherein the processor is further configured to, for multiple storage clusters with the one or more spot instances being selectable for the development volume, select a volume based on a volume criteria.

14 . The management server of claim 11 , wherein the processor is further configured to, for an occurrence of a node failure and for a type of a node associated with the node failure being a spot instance:

create a new spot instance;

for the new spot instance creation being successful, replace the node associated with the node failure with the created spot instance; and

for the new spot instance creation not being successful, wait a constant time until retry creation of the new spot instance while a number of retries is below a threshold.

15 . The management server of claim 11 , wherein the processor is further configured to, for the policy of the volume indicative of the development volume, determine whether the storage cluster having the one or more spot instances from the storage clusters have sufficient capacity to meet the request for the volume creation; and

for the capacity determined to be insufficient, generate a warning to a storage provider associated with the request for the volume creation.

Assignments (2)
DE-MERGER EFFECTIVE APRIL 1, 2024 Recorded Oct 1, 2024
From: HITACHI, LTD.
To: HITACHI VANTARA, LTD.
Reel/Frame 069083/0345 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 18, 2024
From: SUZUKI, TAKANOBU; OSAKI, HIROYUKI
To: HITACHI, LTD.
Reel/Frame 067152/0479 →
Continuity (1)
Related Publication 20250328434A1 · Oct 23, 2025
References Cited (4)
US 10621060B2 · Agetsuma et al. · 2020 [cited by applicant]
US 11360854B2 · Zhou · 2022 [cited by examiner]
US 20210019194A1 · Bahl · 2021 [cited by examiner]
US 20210334043A1 · Ito et al. · 2021 [cited by applicant]