Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner

• US 8,984,223 B2
• Filed: 07/01/2013
• Issued: 03/17/2015
• Est. Priority Date: 12/24/1997
• Status: Expired due to Fees

• Current Assignee: Avid Technology Incorporated
• Original Assignee: Avid Technology Incorporated
• Inventors: Peters, Eric C., Rabinowitz, Stanley, Jacobs, Herbert R., Fasciano, Peter J.
• Primary Examiner(s): BATAILLE, PIERRE MICHE
• Application Number:
  US13/932,225
• Publication Number:
  US 20130325895A1
• Time in Patent Office: 624 Days
• Field of Search: 711/112, 711/114, 711/162, 711/13, 711/165, 711/170, 711/111, 711/202, 711/E12.001
• US Class Current: 711/114
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/184 implemented as replicated file system
• CPC Class Codes: G06F 16/1844 Management specifically adapted to replicated file systems
• CPC Class Codes: G06F 16/70 of video data
• CPC Class Codes: G06F 2211/1028 Distributed, i.e. distributed RAID systems with parity
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1097 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]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04N 21/2182 involving memory arrays, e.g. RAID disk arrays RAID arrays per se G06F3/0689; use of parity to protect data in RAID systems G06F11/1008
• CPC Class Codes: H04N 21/23103 using load balancing strategies, e.g. by placing or distributing content on different disks, different memories or different servers storage management G06F3/0604; allocation of resources considering the load in multiprogramming arrangements G06F9/505; techniques for rebalancing the load in a distributed system G06F9/5083; access to distributed or replicated servers, e.g. load balancing, in data networks H04L67/1001
• CPC Class Codes: H04N 21/23116 involving data replication, e.g. over plural servers synchronization of replicated data G06F11/1658; error detection or correction by means of data replication G06F11/2053; replication in distributed file systems G06F16/10; replication in distributed file systems G06F16/27; replication or mirroring of data in data networks H04L67/1095
• CPC Class Codes: H04N 21/2312 Data placement on disk arrays data placement in general G06F3/0604
• CPC Class Codes: H04N 21/2315 using interleaving
• CPC Class Codes: H04N 21/232 : Content retrieval operation locally within server, e.g. reading video streams from disk arrays storage management G06F3/0604; details of querying and searching of video data from a database G06F16/739
• CPC Class Codes: H04N 21/2393 : involving handling client requests scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04N 21/2396 : characterized by admission policies admission control, resource allocation in open networks H04L12/5692; arrangements for network security using user profiles for access control H04L63/102; access security in wireless networks H04W12/08
• CPC Class Codes: H04N 21/2405 : Monitoring of the internal components or processes of the server, e.g. server load allocation of resources in multiprogramming arrangements G06F9/50; performance measurement of computer activity G06F11/34
• CPC Class Codes: H04N 21/241 : Operating system [OS] processes, e.g. server setup
• CPC Class Codes: H04N 21/262 : Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists scheduling strategies for dispatcher in multiprogramming arrangements G06F9/4881; arrangements for scheduling broadcast services or broadcast-related services H04H60/06; flow control in packet networks H04L47/10; establishing a time schedule or organising the servicing of application requests H04L67/62
• CPC Class Codes: H04N 21/44004 : involving video buffer management, e.g. video decoder buffer or video display buffer
• CPC Class Codes: H04N 21/442 : Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk arrangements for monitoring broadcast services or broadcast-related services H04H60/29; arrangements for identifying or recognising characteristics with a direct linkage to broadcast information H04H60/35; monitoring of user activities for profile generation for accessing a video database G06F16/739; monitoring in wireless networks H04W24/00
• CPC Class Codes: H04N 21/47202 : for requesting content on demand, e.g. video on demand
• CPC Class Codes: H04N 21/8456 : by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04N 7/17336 : Handling of requests in head-ends
• CPC Class Codes: Y10S 707/99953 : Recoverability
• CPC Class Codes: Y10S 707/99956 : File allocation

Abstract

Multiple applications request data from multiple storage units over a computer network. The data is divided into segments and each segment is distributed randomly on one of several storage units, independent of the storage units on which other segments of the media data are stored. At least one additional copy of each segment also is distributed randomly over the storage units, such that each segment is stored on at least two storage units. This random distribution of multiple copies of segments of data improves both scalability and reliability. When an application requests a selected segment of data, the request is processed by the storage unit with the shortest queue of requests. Random fluctuations in the load applied by multiple applications on multiple storage units are balanced nearly equally over all of the storage units. This combination of techniques results in a system which can transfer multiple, independent high-bandwidth streams of data in a scalable manner in both directions between multiple applications and multiple storage units.

Claims

1. In a distributed data storage system comprising a plurality of storage units for storing data and interconnected by a computer network, wherein stored data from a file is divided into segments that are distributed among the plurality of storage units, wherein each segment has an identifier, and wherein two or more copies of each segment are distributed among the plurality of storage units, such that each segment is stored on at least two of the storage units, and wherein the segments of data are distributed nonsequentially among the plurality of storage units, a method for allowing one or more client systems to access segments of data from a file, comprising:

each client system;

accessing a catalog manager that associates, for each segment of a file, the identifier of the segment with an indication of each of the storage units on which a copy of the segment is stored;

for each segment to be read, selecting one of the at least two storage units storing the segment;

sending over the network a request for the segment directly to the selected storage unit, wherein the request includes the identifier of the requested segment; and

each storage unit;

maintaining data defining information that associates, for each segment stored on the storage unit, the identifier of the segment with the location of the segment in storage;

receiving a request over the computer network from one of the client systems for a segment, wherein the received request includes the identifier of the requested segment;

determining the location of the segment in the storage using the information that associates the identifier of the requested segment with the location of the segment in the storage;

retrieving the requested segment from the storage; and

sending the retrieved segment over the computer network to the client system that requested the segment.

2. The method of claim 1, wherein, if a storage unit is unavailable, segments stored on the unavailable storage unit are copied from other storage units that store the segments to other available storage units.

3. The method of claim 1, wherein the catalog manager tracks storage locations of the segments of data by updating information indicating the storage units on which the segments of files are stored when one or more segments of data are written to storage.

4. A data storage system, comprising:

a plurality of client systems, each client system having a file system through which applications executed on the client system access data;

a plurality of storage servers coupled to the plurality of client systems via a computer network, each storage server storing data from files of the file system;

wherein the stored data from each of the files is divided into segments that are stored across the plurality of storage servers, with two or more copies of each segment being distributed among the plurality of storage servers, such that each segment is stored on at least two of the storage servers and wherein the segments of data are distributed nonsequentially among the plurality of storage servers; and

a catalog manager having storage in that stores information indicating the storage servers on which the segments of files are stored;

at least one of the client systems being configured to;

access, before reading data from a file, the catalog manager to obtain the information indicating the storage servers on which the segments of the file are stored, and

communicate directly with the storage servers to request the segments of the file using the accessed information; and

each storage server being configured to;

maintain data defining information that associates, for each segment stored on the storage server, the identifier of the segment with the location of the segment in storage;

in response to a request from one of the client systems for a segment, wherein the received request includes the identifier of the requested segment, determine the location of the segment in the storage using the information that associates the identifier of the requested segment with the location of the segment in the storage;

retrieve the requested segment from the storage; and

send the retrieved segment over the computer network to the client system that requested the segment.

5. The data storage system of claim 4, wherein the plurality of storage servers are configured to respond to requests received from client systems by accessing the requested segments of the file and sending the requested segments of the file directly to the requesting client system.

6. The data storage system of claim 4, wherein the catalog manager includes a central database accessible by each of the plurality of client systems.

7. A data storage system, comprising:

a client system having a file system through which applications executed on the client system access data;

a plurality of storage servers coupled to the client system via a computer network, each storage server storing data from files of the file system,

wherein the stored data from each of the files is divided into segments that are stored across the plurality of storage servers, with two or more copies of each segment being distributed among the plurality of storage servers, such that each segment is stored on at least two of the storage servers and wherein the segments of data are distributed nonsequentially among the plurality of storage servers; and

a catalog manager configured to maintain information indicating the storage servers on which the segments of files are stored;

the client system being configured to;

access, before reading data from a file, the catalog manager to obtain the information indicating the storage servers on which the segments of the file are stored, and

communicate directly with the storage servers to request the segments of the file using the accessed information; and

each storage server being configured to;

maintain data defining information that associates, for each segment stored on the storage server, the identifier of the segment with the location of the segment in storage;

in response to a request over the computer network from the client system for a segment, wherein the received request includes the identifier of the requested segment, determine the location of the segment in the storage using the information that associates the identifier of the requested segment with the location of the segment in the storage;

retrieve the requested segment from the storage; and

send the retrieved segment over the computer network to the client system.

8. The data storage system of claim 7, wherein the catalog manager includes a central database accessible by the client system.