US20190037013A1 - Methods for managing workload throughput in a storage system and devices thereof - Google Patents
Methods for managing workload throughput in a storage system and devices thereof Download PDFInfo
- Publication number
- US20190037013A1 US20190037013A1 US15/659,930 US201715659930A US2019037013A1 US 20190037013 A1 US20190037013 A1 US 20190037013A1 US 201715659930 A US201715659930 A US 201715659930A US 2019037013 A1 US2019037013 A1 US 2019037013A1
- Authority
- US
- United States
- Prior art keywords
- packets
- parsed
- computing device
- client
- set forth
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000013500 data storage Methods 0.000 description 35
- 238000005516 engineering process Methods 0.000 description 11
- 239000004744 fabric Substances 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 239000000835 fiber Substances 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 238000013341 scale-up Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000013403 standard screening design Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000000844 transformation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1023—Server selection for load balancing based on a hash applied to IP addresses or costs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
-
- H04L67/2804—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Definitions
- This technology relates to managing workload throughput in a storage system for storage devices.
- FIG. 1 is a block diagram of a network environment with exemplary data storage apparatuses each including a node computing device;
- FIG. 2 is a block diagram of an exemplary one of the node computing devices shown in FIG. 1 ;
- FIG. 3 is a flowchart of an exemplary method for managing network traffic in a storage system.
- FIG. 4 is a sequence diagram of an exemplary method for managing network traffic in a storage system.
- the clustered network environment 100 includes data storage apparatuses 102 ( 1 )- 102 (n) that are coupled over a cluster fabric 104 facilitating communication between the data storage apparatuses 102 ( 1 )- 102 (n) (and one or more modules, components, etc. therein, such as, node computing devices 106 ( 1 )- 106 (n), for example), although any number of other elements or components can also be included in the clustered network environment 100 in other examples.
- This technology provides a number of advantages including methods, non-transitory computer readable media, and devices that allow managing network traffic in a storage system.
- node computing devices 106 ( 1 )- 106 (n) can be primary or local storage controllers or secondary or remote storage controllers that provide client devices 108 ( 1 )- 108 (n), with access to data stored within data storage devices 110 ( 1 )- 110 (n) or the server devices 109 ( 1 )- 109 (n).
- the data storage apparatuses 102 ( 1 )- 102 (n) and/or node computing device 106 ( 1 )- 106 (n) of the examples described and illustrated herein are not limited to any particular geographic areas and can be clustered locally and/or remotely.
- the client devices 108 ( 1 )- 108 (n) may be general-purpose computers running applications, and may interact with the data storage apparatuses 102 ( 1 )- 102 (n) using a client/server model for exchange of information. That is, the client devices 108 ( 1 )- 108 (n) may request data from the data storage apparatuses 102 ( 1 )- 102 (n) (e.g., data on one of the data storage devices 110 ( 1 )- 110 (n) managed by a network storage control configured to process I/O commands issued by the client devices 108 ( 1 )- 108 (n)), and the data storage apparatuses 102 ( 1 )- 102 (n) may return results of the request to the client devices 108 ( 1 )- 108 (n) via the storage network connections 112 ( 1 )- 112 (n).
- the data storage apparatuses 102 ( 1 )- 108 (n) may return results of the request to the client devices 108 ( 1 )- 108 (n)
- a series of applications may run on the server devices 109 ( 1 )- 109 (n) include that allows the transmission of applications requested by the client devices 108 ( 1 )- 108 (n), or the node computing devices 106 ( 1 )- 106 (n).
- the server devices 109 ( 1 )- 109 (n) may provide data or receive data in response to requests directed toward the respective applications on the server devices 109 ( 1 )- 109 (n)from the client devices 108 ( 1 )- 108 (n) or the node computing devices 106 ( 1 )- 106 (n).
- the server devices 109 ( 1 )- 109 (n) may be hardware or software or may represent a system with multiple external resource servers, which may include internal or external networks.
- the network modules 114 ( 1 )- 114 (n) can provide connections with one or more other components through the cluster fabric 104 .
- the network module 114 ( 1 ) of node computing device 106 ( 1 ) can access the data storage device 110 (n) by sending a request via the cluster fabric 104 through the disk module 116 (n) of node computing device 106 (n).
- the cluster fabric 104 can include one or more local and/or wide area computing networks embodied as Infiniband, Fibre Channel (FC), or Ethernet networks, for example, although other types of networks supporting other protocols can also be used.
- Disk modules 116 ( 1 )- 116 (n) can be configured to connect data storage devices 110 ( 1 )- 110 ( 2 ), such as disks or arrays of disks, SSDs, flash memory, or some other form of data storage, to the node computing devices 106 ( 1 )- 106 (n). Often, disk modules 116 ( 1 )- 116 (n) communicate with the data storage devices 110 ( 1 )- 110 (n) according to the SAN protocol, such as SCSI or FCP, for example, although other protocols can also be used. Thus, as seen from an operating system on node computing devices 106 ( 1 )- 106 (n), the data storage devices 110 ( 1 )- 110 (n) can appear as locally attached. In this manner, different node computing devices 106 ( 1 )- 106 (n), etc. may access data blocks through the operating system, rather than expressly requesting abstract files.
- data storage devices 110 ( 1 )- 110 ( 2 ) such as disks or arrays of disks, SSDs, flash memory
- While the clustered network environment 100 illustrates an equal number of network modules 114 ( 1 )- 114 ( 2 ) and disk modules 116 ( 1 )- 116 (n), other examples may include a differing number of these modules.
- one or more of the client devices 108 ( 1 )- 108 (n) and server devices 109 ( 1 )- 109 (n) can be networked with the node computing devices 106 ( 1 )- 106 (n) in the cluster, over the storage connections 112 ( 1 )- 112 (n).
- respective client devices 108 ( 1 )- 108 (n) and the server devices 109 ( 1 )- 109 (n) that are networked to a cluster may request services (e.g., exchanging of information in the form of data packets) of node computing devices 106 ( 1 )- 106 (n) in the cluster, and the node computing devices 106 ( 1 )- 106 (n) can return results of the requested services to the client devices 108 ( 1 )- 108 (n).
- services e.g., exchanging of information in the form of data packets
- the client devices 108 ( 1 )- 108 (n) can exchange information with the network modules 114 ( 1 )- 114 (n) residing in the node computing devices 106 ( 1 )- 106 (n) (e.g., network hosts) in the data storage apparatuses 102 ( 1 )- 102 (n).
- the network modules 114 ( 1 )- 114 (n) residing in the node computing devices 106 ( 1 )- 106 (n) (e.g., network hosts) in the data storage apparatuses 102 ( 1 )- 102 (n).
- the storage apparatuses 102 ( 1 )- 102 (n) host aggregates corresponding to physical local and remote data storage devices, such as local flash or disk storage in the data storage devices 110 ( 1 )- 110 (n), for example.
- One or more of the data storage devices 110 ( 1 )- 110 (n) can include mass storage devices, such as disks of a disk array.
- the disks may comprise any type of mass storage devices, including but not limited to magnetic disk drives, flash memory, and any other similar media adapted to store information, including, for example, data (D) and/or parity (P) information.
- the aggregates include volumes 118 ( 1 )- 118 (n) in this example, although any number of volumes can be included in the aggregates.
- the volumes 118 ( 1 )- 118 (n) are virtual data stores that define an arrangement of storage and one or more file systems within the clustered network environment 100 .
- Volumes 118 ( 1 )- 118 (n) can span a portion of a disk or other storage device, a collection of disks, or portions of disks, for example, and typically define an overall logical arrangement of file storage.
- volumes 118 ( 1 )- 118 (n) can include stored data as one or more files or objects that reside in a hierarchical directory structure within the volumes 118 ( 1 )- 118 (n).
- Volumes 118 ( 1 )- 118 (n) are typically configured in formats that may be associated with particular storage systems, and respective volume formats typically comprise features that provide functionality to the volumes 118 ( 1 )- 118 (n), such as providing an ability for volumes 118 ( 1 )- 118 (n) to form clusters.
- a file system (e.g., write anywhere file system) may be implemented that logically organizes the information as a hierarchical structure of directories and files.
- respective files may be implemented as a set of disk blocks configured to store information
- directories may be implemented as specially formatted files in which information about other files and directories are stored.
- Virtual volumes are stored over an aggregate of disparate portions of different physical storage devices.
- Virtual volumes may be a collection of different available portions of different physical storage device locations, such as some available space from disks, for example. It will be appreciated that since the virtual volumes are not “tied” to any one particular storage device, virtual volumes can be said to include a layer of abstraction or virtualization, which allows them to be resized and/or flexible in some regards.
- virtual volumes can include one or more logical unit numbers (LUNs), directories, Qtrees, and/or files.
- LUNs logical unit numbers
- directories directories
- Qtrees Qtrees
- files files
- the LUNs may be characterized as constituting a virtual disk or drive upon which data within the virtual volumes is stored within an aggregate.
- LUNs are often referred to as virtual disks, such that they emulate a hard drive, while they actually comprise data blocks stored in various parts of a volume.
- the data storage devices 110 ( 1 )- 110 (n) can have one or more physical ports, wherein each physical port can be assigned a target address (e.g., SCSI target address).
- a target address on the data storage devices 110 ( 1 )- 110 (n) can be used to identify one or more of the LUNs.
- a connection between the one of the node computing devices 106 ( 1 )- 106 (n) and one or more of the LUNs underlying the volume is created.
- node computing device 106 in this particular example includes processor(s) 200 , a memory 202 , a network adapter 204 , a cluster access adapter 206 , and a storage adapter 208 interconnected by a system bus 210 .
- the node computing device 106 also includes a storage operating system 212 installed in the memory 206 that can, for example, implement a Redundant Array of
- the node computing device 106 (n) is substantially the same in structure and/or operation as node computing device 106 ( 1 ), although the node computing device 106 (n) can include a different structure and/or operation in one or more aspects than the node computing device 106 ( 1 ) in other examples.
- the storage operating system 212 can also manage communications for the node computing device 106 ( 1 ) among other devices that may be in a clustered network, such as attached to a cluster fabric 104 .
- the node computing device 106 ( 1 ) can respond to client device requests to manage data on one of the data storage devices 110 ( 1 )- 110 (n) (e.g., or additional clustered devices) in accordance with the client device requests.
- the storage operating system 212 can also establish one or more file systems including software code and data structures that implement a persistent hierarchical namespace of files and directories, for example. As an example, when a new data storage device (not shown) is added to a clustered network system, the storage operating system 212 is informed where, in an existing directory tree, new files associated with the new data storage device are to be stored. This is often referred to as “mounting” a file system.
- memory 202 can include storage locations that are addressable by the processor(s) 200 and adapters 204 , 206 , and 208 for storing related software application code and data structures.
- the processor(s) 200 and adapters 204 , 206 , and 208 may, for example, include processing elements and/or logic circuitry configured to execute the software code and manipulate the data structures.
- the storage operating system 212 invokes storage operations in support of a file service implemented by the node computing device 106 ( 1 ).
- Other processing and memory mechanisms including various computer readable media, may be used for storing and/or executing application instructions pertaining to the techniques described and illustrated herein.
- the storage operating system 212 can also utilize one or more control files (not shown) to aid in the provisioning of virtual machines.
- the examples may be embodied as one or more non-transitory computer readable media having machine or processor-executable instructions stored thereon for one or more aspects of the present technology, as described and illustrated by way of the examples herein, which when executed by the processor(s) 200 , cause the processor(s) 200 to carry out the steps necessary to implement the methods of this technology, as described and illustrated with the examples herein.
- the executable instructions are configured to perform one or more steps of a method, such as one or more of the exemplary methods described and illustrated later with reference to FIGS. 3-4 , for example.
- the network adapter 204 in this example includes the mechanical, electrical and signaling circuitry needed to connect the node computing device 106 ( 1 ) to one or more of the client devices 108 ( 1 )- 108 (n) over storage network connections 112 ( 1 )- 112 (n), which may comprise, among other things, a point-to-point connection or a shared medium, such as a local area network.
- the network adapter 204 further communicates (e.g., using TCP/IP) via the fabric 104 and/or another network (e.g. a WAN) (not shown) with cloud storage devices to process storage operations associated with data stored thereon.
- the storage adapter 208 cooperates with the storage operating system 212 executing on the node computing device 106 ( 1 ) to access information requested by one of the client devices 108 ( 1 )- 108 (n) (e.g., to access data on a data storage device 110 ( 1 )- 110 (n) managed by a network storage controller).
- the information may be stored on any type of attached array of writeable media such as magnetic disk drives, flash memory, and/or any other similar media adapted to store information.
- the storage adapter 208 can include input/output (I/O) interface circuitry that couples to the disks over an I/O interconnect arrangement, such as a storage area network (SAN) protocol (e.g., Small Computer System Interface (SCSI), iSCSI, hyperSCSI, Fiber Channel Protocol (FCP)).
- SAN storage area network
- SCSI Small Computer System Interface
- iSCSI iSCSI
- hyperSCSI HyperSCSI
- FCP Fiber Channel Protocol
- the information is retrieved by the storage adapter 208 and, if necessary, processed by the processor(s) 200 (or the storage adapter 208 itself) prior to being forwarded over the system bus 210 to the network adapter 204 (and/or the cluster access adapter 206 if sending to another node computing device in the cluster) where the information is formatted into a data packet and returned to a requesting one of the client devices 108 ( 1 )- 108 ( 2 ) and/or sent to another node computing device attached via the cluster fabric 104 .
- a storage driver 214 in the memory 202 interfaces with the storage adapter to facilitate interactions with the data storage devices 110 ( 1 )- 110 (n), as described and illustrated in more detail later with reference to FIG. 4 .
- the node computing device 106 ( 1 ) receives a TCP connection request from one of the client devices 108 ( 1 )- 108 (n), although the node computing device 106 ( 1 ) can receive other types of requests from other devices.
- the node computing device 106 ( 1 ) and the requesting client device of the client devices 108 ( 1 )- 108 (n) may in this example perform a three-way handshake, negotiating the desired TCP options.
- step 310 the node computing device 106 ( 1 ) establishes a connection with the requesting client device of the client devices 108 ( 1 )- 108 (n) and starts receiving the requests in form of network packets from the client device.
- the node computing device 106 ( 1 ) parses the received packets from the requesting client devices 108 ( 1 )- 108 (n). In this example, the node computing device 106 ( 1 ) parses the received packet to check whether the header information is complete in the packet and the type of the request (read or write), although the node computing device 106 ( 1 ) can parse the packet for other types of data. Additionally, in this example, the node computing device 106 ( 1 ) sends PUSH/ACK back to the requesting client device 108 ( 1 )- 108 (n) to set the TCP receive window to zero if the received request is a read request. By doing this, the node computing device 106 ( 1 ) prevents the client from issuing additional requests.
- the node computing device 106 ( 1 ) selects one of the servers 109 ( 1 )- 109 (n) based on the header information in the received packet, although the node computing device 106 ( 1 ) can select the server based on other types or numbers of parameters.
- the node computing device 106 ( 1 ) rewrites the destination internet protocol (IP) address of the received packets to that of the selected server and rewrites the source IP address of the packet to a logical IP address. By rewriting the source and destination IP address, the node computing device 106 ( 1 ) allows the packets to the directly exchanged between the selected server and the requesting client device.
- IP internet protocol
- the node computing device 106 ( 1 ) forwards the received packet to the selected server and the packets are directly exchanged between the requesting client and the selected server.
- the server when the client request is a write request, the server must only ACK the payload data of that request and not any additional data the client may have sent. However when the client request is a read request, the server sets the TCP receive window to zero to prevent the client from sending any further data. Additionally, the selected server ignores any TCP FIN the requesting client would send to prevent the client from closing the connection before the connection is handed back to the node computing device 106 ( 1 ). Further in this example, the node computing device 106 ( 1 ) can pass any state information associated with the requesting client device to the selected server so that the selected server can take over the connection established with the requesting client.
- the node computing device 106 ( 1 ) receives a data exchange complete message from the selected server when the data exchange between the client and the server is complete. Additionally in this example, the node computing device 106 ( 1 ) includes the data associated with the client connection such as TCP sequence, ACL numbers, timestamp options, although other types of data associated with the client connection can be included.
- the node computing device 106 ( 1 ) removes the rewrite rules that were included in the header and sends an ACK packet back to the requesting client device 108 ( 1 )- 108 (n) indicating that receiving window is open for a subsequent request. As a response, if the client sends a new request, the exemplary method again resumes as step 315 . However, when the node computing device 106 ( 1 ) receives a FIN handshake from the requesting client 108 ( 1 )- 108 (n), the node computing device 106 ( 1 ) terminates the connection and the exemplary method ends at step 345 .
- transaction payload data is exchanged directly between clients and backend servers, which eliminates the proxy bottleneck.
- the disclosed technology allows the proxy to handle only metadata thereby scaling much higher number of transaction rates when compared to the traditional proxies.
- the disclosed technology is more efficient than traditional proxy-based approaches, because it performs the necessary transformations to scale out the communication steam on the packet level, utilizing software-defined network switches and controllers to transform client network packets in the network.
Abstract
Description
- This technology relates to managing workload throughput in a storage system for storage devices.
- Many application's protocols communicate point-to-point over a single TCP connection, i.e., a client executes a potentially lengthy series of transactions with a server over a TCP connection. As demand grows, due to the point-to-point nature of the protocol the typical solution is the scale up the server by giving it more resources, instead of scaling out by spreading the client load to multiple back-end servers.
- Unfortunately, the scale-out solutions require protocols where the client is aware of the scaled-out nature of the back-end servers, or they require complicated hand-off procedures, where the back-end servers coordinate migration of client connections. These traditional techniques of scale-out result in low throughput of packets which in turn provides sub-standard experience to the client devices.
-
FIG. 1 is a block diagram of a network environment with exemplary data storage apparatuses each including a node computing device; -
FIG. 2 is a block diagram of an exemplary one of the node computing devices shown inFIG. 1 ; -
FIG. 3 is a flowchart of an exemplary method for managing network traffic in a storage system; and -
FIG. 4 is a sequence diagram of an exemplary method for managing network traffic in a storage system. - A
clustered network environment 100 that may implement one or more aspects of the technology described and illustrated herein is shown inFIG. 1 . Theclustered network environment 100 includes data storage apparatuses 102(1)-102(n) that are coupled over acluster fabric 104 facilitating communication between the data storage apparatuses 102(1)-102(n) (and one or more modules, components, etc. therein, such as, node computing devices 106(1)-106(n), for example), although any number of other elements or components can also be included in theclustered network environment 100 in other examples. This technology provides a number of advantages including methods, non-transitory computer readable media, and devices that allow managing network traffic in a storage system. - In this example, node computing devices 106(1)-106(n) can be primary or local storage controllers or secondary or remote storage controllers that provide client devices 108(1)-108(n), with access to data stored within data storage devices 110(1)-110(n) or the server devices 109(1)-109(n). The data storage apparatuses 102(1)-102(n) and/or node computing device 106(1)-106(n) of the examples described and illustrated herein are not limited to any particular geographic areas and can be clustered locally and/or remotely. Thus, in one example the data storage apparatuses 102(1)-102(n) and/or node computing device 106(1)-106(n) can be distributed over a plurality of storage systems located in a plurality of geographic locations; while in another example a clustered network can include data storage apparatuses 102(1)-102(n) and/or node computing device 106(1)-106(n) residing in a same geographic location (e.g., in a single onsite rack).
- In the illustrated example, one or more of the client devices 108(1)-108(n), which may be, for example, personal computers (PCs), computing devices used for storage (e.g., storage servers), and other computers or peripheral devices, are coupled to the respective data storage apparatuses 102(1)-102(n) by storage network connections 112(1)-112(n). Network connections 112(1)-112(n) may include a local area network (LAN) or wide area network (WAN), for example, that utilizes Network Attached Storage (NAS) protocols, such as a Common Internet File System (CIFS) protocol or a Network File System (NFS) protocol to exchange data packets, a
- Storage Area Network (SAN) protocol, such as Small Computer System Interface (SCSI) or Fiber Channel Protocol (FCP), an object protocol, such as S3, etc.
- Illustratively, the client devices 108(1)-108(n) may be general-purpose computers running applications, and may interact with the data storage apparatuses 102(1)-102(n) using a client/server model for exchange of information. That is, the client devices 108(1)-108(n) may request data from the data storage apparatuses 102(1)-102(n) (e.g., data on one of the data storage devices 110(1)-110(n) managed by a network storage control configured to process I/O commands issued by the client devices 108(1)-108(n)), and the data storage apparatuses 102(1)-102(n) may return results of the request to the client devices 108(1)-108(n) via the storage network connections 112(1)-112(n).
- The server devices 109(1)-109(n) include a central processing unit (CPU) or processor, a memory, and a communication system, which are coupled together by a bus or other link, although other numbers and/or types of network devices could be used. Generally, the server devices 109(1)-109(n) process requests for providing requested web pages or websites received from the client devices 108(1)-108(n), via the storage network connections 112(1)-112(n) according to the HTTP-based application RFC protocol or the CIFS or NFS protocol in this example, but the principles discussed herein are not limited to this example and can include other application protocols. A series of applications may run on the server devices 109(1)-109(n) include that allows the transmission of applications requested by the client devices 108(1)-108(n), or the node computing devices 106(1)-106(n). The server devices 109(1)-109(n) may provide data or receive data in response to requests directed toward the respective applications on the server devices 109(1)-109(n)from the client devices 108(1)-108(n) or the node computing devices 106(1)-106(n). It is to be understood that the server devices 109(1)-109(n) may be hardware or software or may represent a system with multiple external resource servers, which may include internal or external networks.
- The node computing devices 106(1)-106(n) of the data storage apparatuses 102(1)-102(n) can include network or host nodes that are interconnected as a cluster to provide data storage and management services, such as to an enterprise having remote locations, cloud storage (e.g., a storage endpoint may be stored within a data cloud), etc., for example. Such a node computing device 106(1)-106(n) can be a device attached to the
fabric 104 as a connection point, redistribution point, or communication endpoint, for example. One or more of the node computing devices 106(1)-106(n) may be capable of sending, receiving, and/or forwarding information over a network communications channel, and could comprise any type of device that meets any or all of these criteria. - In an example, the node computing device 106(1) may be located on a first storage site and the node computing device 106(n) may be located at a second storage site. The node computing devices 106(1) and 106(n) may be configured according to a disaster recovery configuration whereby a surviving node provides switchover access to the storage devices 110(1)-110(n) in the event a disaster occurs at a disaster storage site (e.g., the node computing device 106(1) provides client device 112(n) with switchover data access to storage devices 110(n) in the event a disaster occurs at the second storage site). In other examples, the node computing device 106(n) can be configured according to an archival configuration and/or the node computing devices 106(1)-106(n) can be configured based on another type of replication arrangement (e.g., to facilitate load sharing). Additionally, while two node computing devices are illustrated in
FIG. 1 , any number of node computing devices or data storage apparatuses can be included in other examples in other types of configurations or arrangements. - As illustrated in the
clustered network environment 100, node computing devices 106(1)-106(n) can include various functional components that coordinate to provide a distributed storage architecture. For example, the node computing devices 106(1)-106(n) can include network modules 114(1)-114(n) and disk modules 116(1)-116(n). Network modules 114(1)-114(n) can be configured to allow the node computing devices 106(1)-106(n) (e.g., network storage controllers) to connect with client devices 108(1)-108(n) over the storage network connections 112(1)-112(n), for example, allowing the client devices 108(1)-108(n) to access data stored in theclustered network environment 100. - Further, the network modules 114(1)-114(n) can provide connections with one or more other components through the
cluster fabric 104. For example, the network module 114(1) of node computing device 106(1) can access the data storage device 110(n) by sending a request via thecluster fabric 104 through the disk module 116(n) of node computing device 106(n). Thecluster fabric 104 can include one or more local and/or wide area computing networks embodied as Infiniband, Fibre Channel (FC), or Ethernet networks, for example, although other types of networks supporting other protocols can also be used. - Disk modules 116(1)-116(n) can be configured to connect data storage devices 110(1)-110(2), such as disks or arrays of disks, SSDs, flash memory, or some other form of data storage, to the node computing devices 106(1)-106(n). Often, disk modules 116(1)-116(n) communicate with the data storage devices 110(1)-110(n) according to the SAN protocol, such as SCSI or FCP, for example, although other protocols can also be used. Thus, as seen from an operating system on node computing devices 106(1)-106(n), the data storage devices 110(1)-110(n) can appear as locally attached. In this manner, different node computing devices 106(1)-106(n), etc. may access data blocks through the operating system, rather than expressly requesting abstract files.
- While the
clustered network environment 100 illustrates an equal number of network modules 114(1)-114(2) and disk modules 116(1)-116(n), other examples may include a differing number of these modules. For example, there may be a plurality of network and disk modules interconnected in a cluster that do not have a one-to-one correspondence between the network and disk modules. That is, different node computing devices can have a different number of network and disk modules, and the same node computing device can have a different number of network modules than disk modules. - Further, one or more of the client devices 108(1)-108(n) and server devices 109(1)-109(n) can be networked with the node computing devices 106(1)-106(n) in the cluster, over the storage connections 112(1)-112(n). As an example, respective client devices 108(1)-108(n) and the server devices 109(1)-109(n) that are networked to a cluster may request services (e.g., exchanging of information in the form of data packets) of node computing devices 106(1)-106(n) in the cluster, and the node computing devices 106(1)-106(n) can return results of the requested services to the client devices 108(1)-108(n). In one example, the client devices 108(1)-108(n) can exchange information with the network modules 114(1)-114(n) residing in the node computing devices 106(1)-106(n) (e.g., network hosts) in the data storage apparatuses 102(1)-102(n).
- In one example, the storage apparatuses 102(1)-102(n) host aggregates corresponding to physical local and remote data storage devices, such as local flash or disk storage in the data storage devices 110(1)-110(n), for example. One or more of the data storage devices 110(1)-110(n) can include mass storage devices, such as disks of a disk array. The disks may comprise any type of mass storage devices, including but not limited to magnetic disk drives, flash memory, and any other similar media adapted to store information, including, for example, data (D) and/or parity (P) information.
- The aggregates include volumes 118(1)-118(n) in this example, although any number of volumes can be included in the aggregates. The volumes 118(1)-118(n) are virtual data stores that define an arrangement of storage and one or more file systems within the clustered
network environment 100. Volumes 118(1)-118(n) can span a portion of a disk or other storage device, a collection of disks, or portions of disks, for example, and typically define an overall logical arrangement of file storage. In one example volumes 118(1)-118(n) can include stored data as one or more files or objects that reside in a hierarchical directory structure within the volumes 118(1)-118(n). Volumes 118(1)-118(n) are typically configured in formats that may be associated with particular storage systems, and respective volume formats typically comprise features that provide functionality to the volumes 118(1)-118(n), such as providing an ability for volumes 118(1)-118(n) to form clusters. - In one example, to facilitate access to data stored on the disks or other structures of the data storage device 110(1)-110(n), a file system (e.g., write anywhere file system) may be implemented that logically organizes the information as a hierarchical structure of directories and files. In this example, respective files may be implemented as a set of disk blocks configured to store information, whereas directories may be implemented as specially formatted files in which information about other files and directories are stored.
- Data can be stored as files or objects within a physical volume and/or a virtual volume, which can be associated with respective volume identifiers, such as file system identifiers (FSIDs). The physical volumes correspond to at least a portion of physical storage devices, such as the data storage device 110(1)-110(n) (e.g., a Redundant Array of Independent (or Inexpensive) Disks (RAID system)) whose address, addressable space, location, etc. does not change. Typically the location of the physical volumes does not change in that the (range of) address(es) used to access it generally remains constant.
- Virtual volumes, in contrast, are stored over an aggregate of disparate portions of different physical storage devices. Virtual volumes may be a collection of different available portions of different physical storage device locations, such as some available space from disks, for example. It will be appreciated that since the virtual volumes are not “tied” to any one particular storage device, virtual volumes can be said to include a layer of abstraction or virtualization, which allows them to be resized and/or flexible in some regards.
- Further, virtual volumes can include one or more logical unit numbers (LUNs), directories, Qtrees, and/or files. Among other things, these features, but more particularly the LUNS, allow the disparate memory locations within which data is stored to be identified, for example, and grouped as a data storage unit. As such, the LUNs may be characterized as constituting a virtual disk or drive upon which data within the virtual volumes is stored within an aggregate. For example, LUNs are often referred to as virtual disks, such that they emulate a hard drive, while they actually comprise data blocks stored in various parts of a volume.
- In one example, the data storage devices 110(1)-110(n) can have one or more physical ports, wherein each physical port can be assigned a target address (e.g., SCSI target address). To represent respective volumes, a target address on the data storage devices 110(1)-110(n) can be used to identify one or more of the LUNs. Thus, for example, when one of the node computing devices 106(1)-106(n) connects to a volume, a connection between the one of the node computing devices 106(1)-106(n) and one or more of the LUNs underlying the volume is created.
- In one example, respective target addresses can identify multiple of the LUNs, such that a target address can represent multiple volumes. The I/O interface, which can be implemented as circuitry and/or software in a storage adapter or as executable code residing in memory and executed by a processor, for example, can connect to volumes by using one or more addresses that identify the one or more of the LUNs.
- Referring to
FIG. 2 , node computing device 106(1) in this particular example includes processor(s) 200, amemory 202, anetwork adapter 204, a cluster access adapter 206, and astorage adapter 208 interconnected by asystem bus 210. Thenode computing device 106 also includes astorage operating system 212 installed in the memory 206 that can, for example, implement a Redundant Array of - Independent (or Inexpensive) Disks (RAID) data loss protection and recovery scheme to optimize a reconstruction process of data of a failed disk or drive in an array. In some examples, the node computing device 106(n) is substantially the same in structure and/or operation as node computing device 106(1), although the node computing device 106(n) can include a different structure and/or operation in one or more aspects than the node computing device 106(1) in other examples.
- The
storage operating system 212 can also manage communications for the node computing device 106(1) among other devices that may be in a clustered network, such as attached to acluster fabric 104. Thus, the node computing device 106(1) can respond to client device requests to manage data on one of the data storage devices 110(1)-110(n) (e.g., or additional clustered devices) in accordance with the client device requests. - The
storage operating system 212 can also establish one or more file systems including software code and data structures that implement a persistent hierarchical namespace of files and directories, for example. As an example, when a new data storage device (not shown) is added to a clustered network system, thestorage operating system 212 is informed where, in an existing directory tree, new files associated with the new data storage device are to be stored. This is often referred to as “mounting” a file system. - In the example node computing device 106(1),
memory 202 can include storage locations that are addressable by the processor(s) 200 andadapters adapters - The
storage operating system 212, portions of which are typically resident in thememory 202 and executed by the processor(s) 200, invokes storage operations in support of a file service implemented by the node computing device 106(1). Other processing and memory mechanisms, including various computer readable media, may be used for storing and/or executing application instructions pertaining to the techniques described and illustrated herein. For example, thestorage operating system 212 can also utilize one or more control files (not shown) to aid in the provisioning of virtual machines. - Accordingly, the examples may be embodied as one or more non-transitory computer readable media having machine or processor-executable instructions stored thereon for one or more aspects of the present technology, as described and illustrated by way of the examples herein, which when executed by the processor(s) 200, cause the processor(s) 200 to carry out the steps necessary to implement the methods of this technology, as described and illustrated with the examples herein. In some examples, the executable instructions are configured to perform one or more steps of a method, such as one or more of the exemplary methods described and illustrated later with reference to
FIGS. 3-4 , for example. - The
network adapter 204 in this example includes the mechanical, electrical and signaling circuitry needed to connect the node computing device 106(1) to one or more of the client devices 108(1)-108(n) over storage network connections 112(1)-112(n), which may comprise, among other things, a point-to-point connection or a shared medium, such as a local area network. In some examples, thenetwork adapter 204 further communicates (e.g., using TCP/IP) via thefabric 104 and/or another network (e.g. a WAN) (not shown) with cloud storage devices to process storage operations associated with data stored thereon. - The
storage adapter 208 cooperates with thestorage operating system 212 executing on the node computing device 106(1) to access information requested by one of the client devices 108(1)-108(n) (e.g., to access data on a data storage device 110(1)-110(n) managed by a network storage controller). The information may be stored on any type of attached array of writeable media such as magnetic disk drives, flash memory, and/or any other similar media adapted to store information. - In the exemplary data storage devices 110(1)-110(n), information can be stored in data blocks on disks. The
storage adapter 208 can include input/output (I/O) interface circuitry that couples to the disks over an I/O interconnect arrangement, such as a storage area network (SAN) protocol (e.g., Small Computer System Interface (SCSI), iSCSI, hyperSCSI, Fiber Channel Protocol (FCP)). The information is retrieved by thestorage adapter 208 and, if necessary, processed by the processor(s) 200 (or thestorage adapter 208 itself) prior to being forwarded over thesystem bus 210 to the network adapter 204 (and/or the cluster access adapter 206 if sending to another node computing device in the cluster) where the information is formatted into a data packet and returned to a requesting one of the client devices 108(1)-108(2) and/or sent to another node computing device attached via thecluster fabric 104. In some examples, astorage driver 214 in thememory 202 interfaces with the storage adapter to facilitate interactions with the data storage devices 110(1)-110(n), as described and illustrated in more detail later with reference toFIG. 4 . - Referring to
FIGS. 3 and 4 , an exemplary method for managing network traffic in a storage system. Instep 305 in this example, the node computing device 106(1) receives a TCP connection request from one of the client devices 108(1)-108(n), although the node computing device 106(1) can receive other types of requests from other devices. As would be appreciated by a person having ordinary skill in the art, the node computing device 106(1) and the requesting client device of the client devices 108(1)-108(n) may in this example perform a three-way handshake, negotiating the desired TCP options. - In
step 310, the node computing device 106(1) establishes a connection with the requesting client device of the client devices 108(1)-108(n) and starts receiving the requests in form of network packets from the client device. - Next in
step 315, the node computing device 106(1) parses the received packets from the requesting client devices 108(1)-108(n). In this example, the node computing device 106(1) parses the received packet to check whether the header information is complete in the packet and the type of the request (read or write), although the node computing device 106(1) can parse the packet for other types of data. Additionally, in this example, the node computing device 106(1) sends PUSH/ACK back to the requesting client device 108(1)-108(n) to set the TCP receive window to zero if the received request is a read request. By doing this, the node computing device 106(1) prevents the client from issuing additional requests. - In
step 320, the node computing device 106(1) selects one of the servers 109(1)-109(n) based on the header information in the received packet, although the node computing device 106(1) can select the server based on other types or numbers of parameters. - Next in
step 325, the node computing device 106(1) rewrites the destination internet protocol (IP) address of the received packets to that of the selected server and rewrites the source IP address of the packet to a logical IP address. By rewriting the source and destination IP address, the node computing device 106(1) allows the packets to the directly exchanged between the selected server and the requesting client device. - Next in
step 330, the node computing device 106(1) forwards the received packet to the selected server and the packets are directly exchanged between the requesting client and the selected server. In this example, when the client request is a write request, the server must only ACK the payload data of that request and not any additional data the client may have sent. However when the client request is a read request, the server sets the TCP receive window to zero to prevent the client from sending any further data. Additionally, the selected server ignores any TCP FIN the requesting client would send to prevent the client from closing the connection before the connection is handed back to the node computing device 106(1). Further in this example, the node computing device 106(1) can pass any state information associated with the requesting client device to the selected server so that the selected server can take over the connection established with the requesting client. - In
step 335, the node computing device 106(1) receives a data exchange complete message from the selected server when the data exchange between the client and the server is complete. Additionally in this example, the node computing device 106(1) includes the data associated with the client connection such as TCP sequence, ACL numbers, timestamp options, although other types of data associated with the client connection can be included. - Next in
step 340, the node computing device 106(1) removes the rewrite rules that were included in the header and sends an ACK packet back to the requesting client device 108(1)-108(n) indicating that receiving window is open for a subsequent request. As a response, if the client sends a new request, the exemplary method again resumes asstep 315. However, when the node computing device 106(1) receives a FIN handshake from the requesting client 108(1)-108(n), the node computing device 106(1) terminates the connection and the exemplary method ends atstep 345. - With this technology, transaction payload data is exchanged directly between clients and backend servers, which eliminates the proxy bottleneck. Additionally, the disclosed technology allows the proxy to handle only metadata thereby scaling much higher number of transaction rates when compared to the traditional proxies. Furthermore, the disclosed technology is more efficient than traditional proxy-based approaches, because it performs the necessary transformations to scale out the communication steam on the packet level, utilizing software-defined network switches and controllers to transform client network packets in the network.
- Having thus described the basic concept of the technology, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the technology. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the technology is limited only by the following claims and equivalents thereto.
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/659,930 US10798159B2 (en) | 2017-07-26 | 2017-07-26 | Methods for managing workload throughput in a storage system and devices thereof |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/659,930 US10798159B2 (en) | 2017-07-26 | 2017-07-26 | Methods for managing workload throughput in a storage system and devices thereof |
Publications (2)
Publication Number | Publication Date |
---|---|
US20190037013A1 true US20190037013A1 (en) | 2019-01-31 |
US10798159B2 US10798159B2 (en) | 2020-10-06 |
Family
ID=65038387
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/659,930 Active 2037-10-22 US10798159B2 (en) | 2017-07-26 | 2017-07-26 | Methods for managing workload throughput in a storage system and devices thereof |
Country Status (1)
Country | Link |
---|---|
US (1) | US10798159B2 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11792284B1 (en) * | 2017-11-27 | 2023-10-17 | Lacework, Inc. | Using data transformations for monitoring a cloud compute environment |
US11050653B2 (en) * | 2019-06-11 | 2021-06-29 | Burlywood, Inc. | Telemetry capture system for storage systems |
Citations (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6157955A (en) * | 1998-06-15 | 2000-12-05 | Intel Corporation | Packet processing system including a policy engine having a classification unit |
US20020078174A1 (en) * | 2000-10-26 | 2002-06-20 | Sim Siew Yong | Method and apparatus for automatically adapting a node in a network |
US20020143955A1 (en) * | 2001-03-27 | 2002-10-03 | Fujitsu Limited | Packet relay processing apparatus |
US20030046394A1 (en) * | 2000-11-03 | 2003-03-06 | Steve Goddard | System and method for an application space server cluster |
US6549516B1 (en) * | 1999-07-02 | 2003-04-15 | Cisco Technology, Inc. | Sending instructions from a service manager to forwarding agents on a need to know basis |
US20030108052A1 (en) * | 2001-12-06 | 2003-06-12 | Rumiko Inoue | Server load sharing system |
US20030149755A1 (en) * | 2002-02-06 | 2003-08-07 | Emek Sadot | Client-controlled load balancer |
US20030148755A1 (en) * | 2002-02-05 | 2003-08-07 | Antonio Bovo | Multi-protocol call trace on GPRS Gb-Gr |
US20040093425A1 (en) * | 2002-11-07 | 2004-05-13 | Thomas David Andrew | Method and system for managing fragmented information packets in a computer network |
US20050005006A1 (en) * | 2003-07-01 | 2005-01-06 | International Business Machines Corporation | System and method for accessing clusters of servers from the internet network |
US6856991B1 (en) * | 2002-03-19 | 2005-02-15 | Cisco Technology, Inc. | Method and apparatus for routing data to a load balanced server using MPLS packet labels |
US20050055435A1 (en) * | 2003-06-30 | 2005-03-10 | Abolade Gbadegesin | Network load balancing with connection manipulation |
US20060050722A1 (en) * | 2004-09-03 | 2006-03-09 | James Bury | Interface circuitry for a receive ring buffer of an as fabric end node device |
US20070192593A1 (en) * | 2005-12-29 | 2007-08-16 | Boisjolie Darren R | Method and system for transparent bridging and bi-directional management of network data |
US20080013534A1 (en) * | 2006-07-14 | 2008-01-17 | Akihito Tsuzuki | Packet transfer device and communication system |
US7519062B1 (en) * | 1997-10-14 | 2009-04-14 | Cisco Technology, Inc. | Method and apparatus for implementing forwarding decision shortcuts at a network switch |
US20090151680A1 (en) * | 2007-12-14 | 2009-06-18 | Bong Sang Lee | Oil gallery for variable valve timing apparatus of a cylinder head |
US20090161680A1 (en) * | 2007-12-21 | 2009-06-25 | Nec Corporation | Gateway apparatus, packet forwarding method, and program |
US7584262B1 (en) * | 2002-02-11 | 2009-09-01 | Extreme Networks | Method of and system for allocating resources to resource requests based on application of persistence policies |
US7711819B2 (en) * | 2001-10-31 | 2010-05-04 | Fujitsu Limited | Load balancer |
US20100287227A1 (en) * | 2009-05-05 | 2010-11-11 | Deepak Goel | Systems and methods for identifying a processor from a plurality of processors to provide symmetrical request and response processing |
US20100312902A1 (en) * | 2007-11-28 | 2010-12-09 | Damaka, Inc. | System and method for endpoint handoff in a hybrid peer-to-peer networking environment |
US7877490B1 (en) * | 2007-12-28 | 2011-01-25 | Violin Memory, Inc. | Method and apparatus for efficient TCP connection handoff |
US20130080575A1 (en) * | 2011-09-27 | 2013-03-28 | Matthew Browning Prince | Distributing transmission of requests across multiple ip addresses of a proxy server in a cloud-based proxy service |
US20130287031A1 (en) * | 2010-12-31 | 2013-10-31 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for forwarding data in communications system |
US20130332584A1 (en) * | 2011-02-28 | 2013-12-12 | Hangzhou H3C Technologies, Co., Ltd. | Load balancing methods and devices |
US20150180963A1 (en) * | 2012-08-19 | 2015-06-25 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US20160277355A1 (en) * | 2015-03-18 | 2016-09-22 | Cisco Technology, Inc. | Inter-pod traffic redirection and handling in a multi-pod network environment |
US20160285648A1 (en) * | 2013-12-04 | 2016-09-29 | Huawei Technologies Co., Ltd. | Data processing method and apparatus, storage controller, and cabinet |
US9461881B2 (en) * | 2011-09-30 | 2016-10-04 | Commvault Systems, Inc. | Migration of existing computing systems to cloud computing sites or virtual machines |
US20180241809A1 (en) * | 2017-02-21 | 2018-08-23 | Microsoft Technology Licensing, Llc | Load balancing in distributed computing systems |
US20190004701A1 (en) * | 2017-07-03 | 2019-01-03 | Intel Corporation | Tier-Aware Read and Write |
US20190241809A1 (en) * | 2018-02-05 | 2019-08-08 | Merck Patent Gmbh | Compounds for the homeotropic alignment of liquid-crystalline media |
US20200112514A1 (en) * | 2016-08-23 | 2020-04-09 | Netduma Software, LTD. | Congestion control |
-
2017
- 2017-07-26 US US15/659,930 patent/US10798159B2/en active Active
Patent Citations (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7519062B1 (en) * | 1997-10-14 | 2009-04-14 | Cisco Technology, Inc. | Method and apparatus for implementing forwarding decision shortcuts at a network switch |
US6157955A (en) * | 1998-06-15 | 2000-12-05 | Intel Corporation | Packet processing system including a policy engine having a classification unit |
US6549516B1 (en) * | 1999-07-02 | 2003-04-15 | Cisco Technology, Inc. | Sending instructions from a service manager to forwarding agents on a need to know basis |
US20020078174A1 (en) * | 2000-10-26 | 2002-06-20 | Sim Siew Yong | Method and apparatus for automatically adapting a node in a network |
US20030046394A1 (en) * | 2000-11-03 | 2003-03-06 | Steve Goddard | System and method for an application space server cluster |
US20020143955A1 (en) * | 2001-03-27 | 2002-10-03 | Fujitsu Limited | Packet relay processing apparatus |
US7711819B2 (en) * | 2001-10-31 | 2010-05-04 | Fujitsu Limited | Load balancer |
US20030108052A1 (en) * | 2001-12-06 | 2003-06-12 | Rumiko Inoue | Server load sharing system |
US20030148755A1 (en) * | 2002-02-05 | 2003-08-07 | Antonio Bovo | Multi-protocol call trace on GPRS Gb-Gr |
US20030149755A1 (en) * | 2002-02-06 | 2003-08-07 | Emek Sadot | Client-controlled load balancer |
US7584262B1 (en) * | 2002-02-11 | 2009-09-01 | Extreme Networks | Method of and system for allocating resources to resource requests based on application of persistence policies |
US6856991B1 (en) * | 2002-03-19 | 2005-02-15 | Cisco Technology, Inc. | Method and apparatus for routing data to a load balanced server using MPLS packet labels |
US20040093425A1 (en) * | 2002-11-07 | 2004-05-13 | Thomas David Andrew | Method and system for managing fragmented information packets in a computer network |
US20050055435A1 (en) * | 2003-06-30 | 2005-03-10 | Abolade Gbadegesin | Network load balancing with connection manipulation |
US20050005006A1 (en) * | 2003-07-01 | 2005-01-06 | International Business Machines Corporation | System and method for accessing clusters of servers from the internet network |
US20060050722A1 (en) * | 2004-09-03 | 2006-03-09 | James Bury | Interface circuitry for a receive ring buffer of an as fabric end node device |
US20070192593A1 (en) * | 2005-12-29 | 2007-08-16 | Boisjolie Darren R | Method and system for transparent bridging and bi-directional management of network data |
US20080013534A1 (en) * | 2006-07-14 | 2008-01-17 | Akihito Tsuzuki | Packet transfer device and communication system |
US20100312902A1 (en) * | 2007-11-28 | 2010-12-09 | Damaka, Inc. | System and method for endpoint handoff in a hybrid peer-to-peer networking environment |
US20090151680A1 (en) * | 2007-12-14 | 2009-06-18 | Bong Sang Lee | Oil gallery for variable valve timing apparatus of a cylinder head |
US20090161680A1 (en) * | 2007-12-21 | 2009-06-25 | Nec Corporation | Gateway apparatus, packet forwarding method, and program |
US7877490B1 (en) * | 2007-12-28 | 2011-01-25 | Violin Memory, Inc. | Method and apparatus for efficient TCP connection handoff |
US20100287227A1 (en) * | 2009-05-05 | 2010-11-11 | Deepak Goel | Systems and methods for identifying a processor from a plurality of processors to provide symmetrical request and response processing |
US20130287031A1 (en) * | 2010-12-31 | 2013-10-31 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for forwarding data in communications system |
US20130332584A1 (en) * | 2011-02-28 | 2013-12-12 | Hangzhou H3C Technologies, Co., Ltd. | Load balancing methods and devices |
US20130080575A1 (en) * | 2011-09-27 | 2013-03-28 | Matthew Browning Prince | Distributing transmission of requests across multiple ip addresses of a proxy server in a cloud-based proxy service |
US9461881B2 (en) * | 2011-09-30 | 2016-10-04 | Commvault Systems, Inc. | Migration of existing computing systems to cloud computing sites or virtual machines |
US20150180963A1 (en) * | 2012-08-19 | 2015-06-25 | Box, Inc. | Enhancement of upload and/or download performance based on client and/or server feedback information |
US20160285648A1 (en) * | 2013-12-04 | 2016-09-29 | Huawei Technologies Co., Ltd. | Data processing method and apparatus, storage controller, and cabinet |
US20160277355A1 (en) * | 2015-03-18 | 2016-09-22 | Cisco Technology, Inc. | Inter-pod traffic redirection and handling in a multi-pod network environment |
US20200112514A1 (en) * | 2016-08-23 | 2020-04-09 | Netduma Software, LTD. | Congestion control |
US20180241809A1 (en) * | 2017-02-21 | 2018-08-23 | Microsoft Technology Licensing, Llc | Load balancing in distributed computing systems |
US20190004701A1 (en) * | 2017-07-03 | 2019-01-03 | Intel Corporation | Tier-Aware Read and Write |
US20190241809A1 (en) * | 2018-02-05 | 2019-08-08 | Merck Patent Gmbh | Compounds for the homeotropic alignment of liquid-crystalline media |
Also Published As
Publication number | Publication date |
---|---|
US10798159B2 (en) | 2020-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11249857B2 (en) | Methods for managing clusters of a storage system using a cloud resident orchestrator and devices thereof | |
EP2659375B1 (en) | Non-disruptive failover of rdma connection | |
JP5026283B2 (en) | Collaborative shared storage architecture | |
US8090908B1 (en) | Single nodename cluster system for fibre channel | |
US11921597B2 (en) | Cross-platform replication | |
EP3380922B1 (en) | Synchronous replication for file access protocol storage | |
JP2005267327A (en) | Storage system | |
US10855556B2 (en) | Methods for facilitating adaptive quality of service in storage networks and devices thereof | |
US10872036B1 (en) | Methods for facilitating efficient storage operations using host-managed solid-state disks and devices thereof | |
US11005894B2 (en) | Methods for demultiplexing services over ports and devices thereof | |
US10782889B2 (en) | Fibre channel scale-out with physical path discovery and volume move | |
US10798159B2 (en) | Methods for managing workload throughput in a storage system and devices thereof | |
US11249671B2 (en) | Methods for improved data replication across hybrid cloud volumes using data tagging and devices thereof | |
US20210334025A1 (en) | Methods for handling storage devices with different zone sizes and devices thereof | |
US10768834B2 (en) | Methods for managing group objects with different service level objectives for an application and devices thereof | |
US10938938B2 (en) | Methods for selectively compressing data and devices thereof | |
US11258877B2 (en) | Methods for managing workloads in a storage system and devices thereof | |
US11709957B2 (en) | Methods for securing files within a storage device using artificial intelligence and devices thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NETAPP, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EGGERT, LARS;SANTRY, DOUGLAS;SIGNING DATES FROM 20170630 TO 20170726;REEL/FRAME:043112/0925 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |