Method and apparatus of subsidiary volume management
US-2017206021-A1 · Jul 20, 2017 · US
US10313251B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10313251-B2 |
| Application number | US-201615011919-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 1, 2016 |
| Priority date | Feb 1, 2016 |
| Publication date | Jun 4, 2019 |
| Grant date | Jun 4, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and systems for a networked storage system are provided. One method includes assigning a quality of service (QOS) parameter for a storage volume of a networked storage environment having a first storage node and a second storage node, where the QOS parameter is defined by a throughput value that defines a maximum data transfer rate and a number of input/output (I/O) operations executed within a time period (IOPS); distributing the QOS parameter between the first storage node and the second storage node; determining that throughput credit is available for processing an I/O request for using the storage volume; determining that IOPS credit is available for processing the request by the first storage node; and processing the I/O request when both the throughput credit and the IOPS credit is available.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: assigning a quality of service (QOS) parameter for a storage volume of a networked storage system, accessible via a first node and a second node of the networked storage system, wherein the QOS parameter is based on a throughput value defining a maximum data transfer rate and a number of input/output (I/O) operations executed within a time period (IOPS) for the storage volume for storing and retrieving data; dividing the QOS parameter between the first node and the second node, based on a traffic pattern of using the first node and the second node; determining whether both throughput credit and IOPS credit are available for processing an I/O request by the first node, the I/O request classified based on a request attribute and assigned to the storage volume, the throughput credit indicating that first node has not reached a throughput threshold and the IOPS credit indicating that the first node has not reached an IOPS threshold; processing the I/O request by the first node when the throughput credit and the IOPS credit are available; and using the second node for processing the I/O request, if both the throughput and the IOPS credit are available for the second node and partially unavailable for the first node. 2. The method of claim 1 , further comprising; when throughput or IOPS credit is unavailable for both the first node and the second node for processing the request, then delaying request processing until credit for both throughput and IOPS is available. 3. The method of claim 1 , wherein the throughput for the first storage node is based on an assigned number of IOPS, a total number of IOPS and a total throughput rate for the storage volume. 4. The method of claim 1 , wherein when the request is processed, then available throughput and IOPS credit for the storage volume is decreased. 5. The method of claim 1 , wherein the QOS parameter value is based on a service level objective assigned to the storage volume. 6. The method of claim 1 , wherein the first node and the second node operate within a cluster managing storage space for storing data on behalf of the storage volume and the I/O request is for storing data or reading data from the storage space. 7. The method of claim 1 , wherein the request attribute for classifying the request is based on one of a request type, a request target and a request protocol. 8. A non-transitory, machine readable storage medium having stored thereon instructions for performing a method, comprising machine executable code which when executed by at least one machine, causes the machine to: assign a quality of service (QOS) parameter for a storage volume of a networked storage system accessible via a first node and a second node of the networked storage system, wherein the QOS parameter is based on a throughput value defining a maximum data transfer rate and a number of input/output (I/O) operations executed within a time period (IOPS) for the storage volume for storing and retrieving data; divide the QOS parameter between the first node and the second node based on a traffic pattern of using the first node and the second node; determine whether both throughput credit and IOPS credit are available for processing an I/O request by the first node, the I/O request classified based on a request attribute and assigned to the storage volume, the throughput credit indicating that first node has not reached a throughput threshold and the IOPS credit indicating that the first node has not reached an IOPS threshold; process the I/O request by the first node when the throughput credit and the IOPS credit are available; and use the second node for processing the I/O request, if both the throughput and the IOPS credit are available for the second node and partially unavailable for the first node. 9. The non-transitory, machine readable storage medium of claim 8 , wherein when throughput or IOPS credit is unavailable for both the first and second node for processing the request, then request processing is delayed until credit for both throughput and IOPS is available. 10. The non-transitory, machine readable storage medium of claim 8 , wherein the throughput for the first node is based on an assigned number of IOPS, a total number of IOPS and a total throughput rate for the storage volume. 11. The non-transitory, machine readable storage medium of claim 8 , wherein when the request is processed, then available throughput and IOPS credit for the storage volume is decreased. 12. The non-transitory, machine readable storage medium of claim 8 , wherein the QOS parameter value is based on a service level objective assigned to the storage volume. 13. The non-transitory, machine readable storage medium of claim 8 , wherein the first node and the second node operate within a cluster managing storage space for storing data on behalf of the storage volume and the I/O request is for storing data or reading data from the storage space. 14. The non-transitory, machine readable storage medium of claim 8 , wherein the request attribute for classifying the request is based on one of a request type, a request target and a request protocol. 15. A system comprising: a memory containing machine readable medium comprising machine executable code having stored thereon instructions; and a processor coupled to the memory, the processor configured to execute the machine executable code to: assign a quality of service (QOS) parameter for a storage volume of a networked storage system accessible via a first node and a second node of the networked storage system, wherein the QOS parameter is based on a throughput value defining a maximum data transfer rate and a number of input/output (I/O) operations executed within a time period (IOPS) for the storage volume for storing and retrieving data; divide the QOS parameter between the first node and the second node based on a traffic pattern of using the first node and the second node; determining whether both throughput credit and IOPS credit are available for processing an I/O request by the first node, the I/O request classified based on a request attribute and assigned to the storage volume, the throughput credit indicating that first node has not reached a throughput threshold and the IOPS credit indicating that the first node has not reached an IOPS threshold; processing the I/O request by the first node when the throughput credit and the IOPS credit are available; and using the second node for processing the I/O request, if both the throughput and the IOPS credit are available for the second node and partially unavailable for the first node. 16. The system of claim 15 , wherein when throughput or IOPS credit is unavailable for both the first node and the second node for processing the request, then the I/O request processing is delayed until credit for both throughput and IOPS is available. 17. The system of claim 15 , wherein the throughput for the first storage node is based on an assigned number of IOPS, a total number of IOPS and a total throughput rate for the storage volume. 18. The system of claim 15 , wherein when the request is processed, then available throughput and IOPS credit for the storage volume is decreased. 19. The system of claim 15 , wherein the QOS parameter value is based on a service level objective assigned to the storage volume. 20. The system of claim 15 , wherein the first node and the second node operate within a cluster managing storage space for storing data on behalf of the stor
by changing the path, e.g. traffic rerouting, path reconfiguration · CPC title
Traffic characterised by specific attributes, e.g. priority or QoS · CPC title
Assignment of logical groups to network elements · CPC title
Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title
Improving I/O performance · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.