US 10,705,930 B2Granted

Service takeover method, storage device, and service takeover apparatus

AssigneeHuawei Technologies Co., Ltd.

InventorCheng Zhang

Life of this patent

Estimating the term…

Loading patent…

Abstract

The present disclosure describes example service takeover methods, storage devices, and service takeover apparatuses. In one example, when a communication fault occurs between two storage devices in a storage system, the two storage devices respectively obtain running statuses of the two storage devices. A running status can reflect current usage of one or more system resources of a particular storage device. Then, a delay duration is determined according to the running statuses, where the delay duration is a duration for which the storage device waits before sending an arbitration request to a quorum server. The two storage devices respectively send, after the delay duration, arbitration requests to the quorum server to request to take over a service. The quorum server then can select a storage device in a relatively better running status to take over a host service.

Claims10

Dependent claims

A service takeover method in a storage system, wherein the storage system comprises a first storage device, a second storage device, and a quorum server, wherein data communication is performed between the first storage device and the second storage device by using a link, and wherein the service takeover method being performed by the first storage device comprises:

obtaining a running status of the first storage device when a communication fault occurs between the first storage device and the second storage device, wherein the running status reflects current usage of a system resource of the first storage device, and wherein the system resource comprises at least one of:
a processor resource, a hard disk resource, a cache resource, or a host bandwidth resource;
determining a delay duration according to the running status that reflects the current usage of the system resource of the first storage device, wherein the delay duration is a duration for which the first storage device waits before sending an arbitration request to the quorum server, wherein the delay duration for which the first storage device waits before sending the arbitration request to the quorum server is proportional to a running status value indicating the current usage of the system resource of the first storage device;
and
sending, after the delay duration, the arbitration request to the quorum server to request to take over a service.

2 more elements

A storage device, wherein the storage device is located in a storage system, and the storage device comprises:

a communications interface, the communications interface configured to communicate with another storage device and a quorum server in the storage system;
and
at least one processor, the at least one processor configured to:
obtain a running status of the storage device when determining that a communication fault occurs between the storage device and the another storage device, wherein the running status reflects current usage of a system resource of the storage device, and wherein the system resource comprises at least one of:
a processor resource, a hard disk resource, a cache resource, and a host bandwidth resource;
determine a delay duration according to the running status, wherein the delay duration is a duration for which the storage device waits before sending an arbitration request to the quorum server, wherein the delay duration for which the first storage device waits before sending the arbitration request to the quorum server is proportional to a running status value indicating the current usage of the system resource of the first storage device;
and
send, using the communications interface and after the delay duration, the arbitration request to the quorum server to request to take over a service.

5 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/874,722Filed 18 Jan 2018 · continuation
Priority: 23 Dec 2015
Published: US 2018/0143887 A124 May 2018
Granted: 7 Jul 2020
Term ends: Not estimatedThe source records don’t support an estimate.

Classification17 codes

G06F 11/2033
Failover techniques: switching over of hardware resources
G06F 11/1645
Where the comparison is not performed by the redundant processing components: and the comparison itself uses redundant hardware
G06F 11/165
Error detection by comparing the output of redundant processing systems: with continued operation after detection of the error
G06F 11/2025
Failover techniques: using centralised failover control functionality