Method for the implementation of a high performance, high resiliency and high availability dual controller storage system

Patent metadata

Field	Value
Publication number	US-11221927-B2
Application number	US-202016736628-A
Country	US
Kind code	B2
Filing date	Jan 7, 2020
Priority date	Sep 5, 2017
Publication date	Jan 11, 2022
Grant date	Jan 11, 2022

Abstract

A controller-implemented method, according to one embodiment, includes: receiving, by a first controller, data. Metadata associated with the data is stored, by the first controller, in a specified system memory location. Second metadata received from a second controller is also stored, by the first controller, in the specified system memory location, thereby creating combined metadata. In response to the second controller entering a failed state: snapshots of the combined metadata are stored, by the first controller, to resilient storage at a predefined interval. Moreover, additional data continues to be received by the first controller. Metadata associated with the additional data is stored, by the first controller, in the specified system memory location, while changes to the metadata which occur between the snapshots of the combined metadata are also stored by the first controller. According to some approaches, the changes to the metadata are stored in a log structured array.

First claim

What is claimed is:

1. A controller-implemented method, comprising:
receiving, by a first controller, data;
storing, by the first controller, metadata associated with the data in a specified system memory location in random access memory;
storing, by the first controller, second metadata received from a second controller with the metadata in the specified system memory location, thereby creating combined metadata; and
in response to the second controller entering a failed state:
storing, by the first controller, snapshots of the combined metadata to resilient storage at a predefined interval,
continuing to receive, by the first controller, additional data,
storing, by the first controller, metadata associated with the additional data in the specified system memory location, and
storing, by the first controller, changes to the metadata which occur between the snapshots of the combined metadata, wherein the changes to the metadata are stored in a log structured array.

2. The controller-implemented method of claim 1 , wherein an external process is attached to the specified system memory location in response to the first controller entering a failed state while the second controller is also in a failed state, wherein the first and second controllers are included in a system, wherein the combined metadata stored in the specified system memory location is used to restore the system, wherein the system is returned to a normal operating mode in response to the system being restored.

3. The controller-implemented method of claim 2 , wherein the system is a data storage system, wherein the first and second controllers are each coupled to a load balancer.

4. The controller-implemented method of claim 1 , comprising:
storing, by the first controller, the data in a write cache in the random access memory.

5. The controller-implemented method of claim 1 , wherein the data is received from a load balancer, wherein the second metadata corresponds to second data received by the second controller from the load balancer, wherein information is split by the load balancer to form the data and the second data.

6. The controller-implemented method of claim 1 , wherein changes to the metadata which occur between the snapshots of the combined metadata and which are of a size that is in a predetermined range are blocked.

7. The controller-implemented method of claim 1 , wherein the resilient storage is different than the specified system memory location in random access memory.

8. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions readable and/or executable by a first controller to cause the first controller to:
receive, by the first controller, data;
store, by the first controller, metadata associated with the data in a specified system memory location in random access memory;
store, by the first controller, second metadata received from a second controller with the metadata in the specified system memory location, thereby creating combined metadata; and
in response to the second controller entering a failed state:
store, by the first controller, snapshots of the combined metadata to resilient storage at a predefined interval,
continue to receive, by the first controller, additional data,
store, by the first controller, metadata associated with the additional data in the specified system memory location, and
store, by the first controller, changes to the metadata which occur between the snapshots of the combined metadata, wherein the changes to the metadata are stored in a log structured array.

9. The computer program product of claim 8 , wherein an external process is attached to the specified system memory location in response to the first controller entering a failed state while the second controller is also in a failed state, wherein the first and second controllers are included in a system, wherein the combined metadata stored in the specified system memory location is used to restore the system, wherein the system is returned to a normal operating mode in response to the system being restored.

10. The computer program product of claim 9 , wherein the system is a data storage system, wherein the first and second controllers are each coupled to a load balancer.

11. The computer program product of claim 8 , wherein the program instructions are readable and/or executable by the first controller to cause the first controller to:
store, by the first controller, the data in a write cache in the random access memory.

12. The computer program product of claim 8 , wherein the data is received from a load balancer, wherein the second metadata corresponds to second data received by the second controller from the load balancer, wherein information is split by the load balancer to form the data and the second data.

13. The computer program product of claim 8 , wherein changes to the metadata which occur between the snapshots of the combined metadata and which are of a size that is in a predetermined range are blocked.

14. The computer program product of claim 8 , wherein the resilient storage is different than the specified system memory location in random access memory.

15. A system, comprising:
a first controller; and
logic integrated with the first controller, executable by the first controller, or integrated with and executable by the first controller, the logic being configured to:
receive, by the first controller, data;
store, by the first controller, metadata associated with the data in a specified system memory location in random access memory;
store, by the first controller, second metadata received from a second controller with the metadata in the specified system memory location, thereby creating combined metadata; and
in response to the second controller entering a failed state:
store, by the first controller, snapshots of the combined metadata to resilient storage at a predefined interval,
continue to receive, by the first controller, additional data,
store, by the first controller, metadata associated with the additional data in the specified system memory location, and
store, by the first controller, changes to the metadata which occur between the snapshots of the combined metadata, wherein the changes to the metadata are stored in a log structured array,
wherein the resilient storage is different than the specified system memory location.

16. The system of claim 15 , wherein an external process is attached to the specified system memory location in response to the first controller entering a failed state while the second controller is also in a failed state, wherein the combined metadata stored in the specified system memory location is used to restore the system, wherein the system is returned to a normal operating mode in response to the system being restored.

17. The system of claim 16 , wherein the system is a data storage system, wherein the first and second controllers are each coupled to a load balancer.

18. The system of claim 15 , the logic being configured to:
store, by the first controller, the data in a write cache in the random access memory.

19. The system of claim 15 , wherein the data is received from a load balancer, wherein the second metadata corresponds to second data received by the second controller from the load balancer, wherein information is split by the load balancer to form the data and the second data.

20. The system of claim 15 , wherein changes to the metadata which oc

Assignees

• IBM

Inventors

• Chen Lior
• Gan-Levi Daniel
• Gazit Ronen
• Leneman Ofer
• Messing Deborah A

Classifications

• G06F11/1435 Primary

  using file system or storage system metadata · CPC title

• G06F3/065

  Replication mechanisms · CPC title

• G06F11/1471

  involving logging of persistent data for recovery · CPC title

• G06F3/0619

  in relation to data integrity, e.g. data losses, bit errors · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title