Patent Application
20230108184
Not applicable.
Not applicable.
This invention relates generally to computer networks and more particularly to dispersing error encoded data.
Computing devices are known to communicate data, process data, and/or store data. Such computing devices range from wireless smart phones, laptops, tablets, personal computers (PC), work stations, and video game devices, to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing device includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.
As is further known, a computer may effectively extend its CPU by using “cloud computing” to perform one or more computing functions (e.g., a service, an application, an algorithm, an arithmetic logic function, etc.) on behalf of the computer. Further, for large services, applications, and/or functions, cloud computing may be performed by multiple cloud computing resources in a distributed manner to improve the response time for completion of the service, application, and/or function. For example, Hadoop is an open source software framework that supports distributed applications enabling application execution by thousands of computers.
In addition to cloud computing, a computer may use “cloud storage” as part of its memory system. As is known, cloud storage enables a user, via its computer, to store files, applications, etc. on an Internet storage system. The Internet storage system may include a RAID (redundant array of independent disks) system and/or a dispersed storage system that uses an error correction scheme to encode data for storage.
The DSN memory 22 includes a plurality of storage units 36 that may be located at geographically different sites (e.g., one in Chicago, one in Milwaukee, etc.), at a common site, or a combination thereof. For example, if the DSN memory 22 includes eight storage units 36, each storage unit is located at a different site. As another example, if the DSN memory 22 includes eight storage units 36, all eight storage units are located at the same site. As yet another example, if the DSN memory 22 includes eight storage units 36, a first pair of storage units are at a first common site, a second pair of storage units are at a second common site, a third pair of storage units are at a third common site, and a fourth pair of storage units are at a fourth common site. Note that a DSN memory 22 may include more or less than eight storage units 36. Further note that each storage unit 36 includes a computing core (as shown in
Each of the computing devices 12-16, the managing unit 18, and the integrity processing unit 20 include a computing core 26, which includes network interfaces 30-33. Computing devices 12-16 may each be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment. Note that each of the managing unit 18 and the integrity processing unit 20 may be separate computing devices, may be a common computing device, and/or may be integrated into one or more of the computing devices 12-16 and/or into one or more of the storage units 36.
Each interface 30, 32, and 33 includes software and hardware to support one or more communication links via the network 24 indirectly and/or directly. For example, interface 30 supports a communication link (e.g., wired, wireless, direct, via a LAN, via the network 24, etc.) between computing devices 14 and 16. As another example, interface 32 supports communication links (e.g., a wired connection, a wireless connection, a LAN connection, and/or any other type of connection to/from the network 24) between computing devices 12 & 16 and the DSN memory 22. As yet another example, interface 33 supports a communication link for each of the managing unit 18 and the integrity processing unit 20 to the network 24.
Computing devices 12 and 16 include a dispersed storage (DS) client module 34, which enables the computing device to dispersed storage error encode and decode data as subsequently described with reference to one or more of
In operation, the managing unit 18 performs DS management services. For example, the managing unit 18 establishes distributed data storage parameters (e.g., vault creation, distributed storage parameters, security parameters, billing information, user profile information, etc.) for computing devices 12-14 individually or as part of a group of user devices. As a specific example, the managing unit 18 coordinates creation of a vault (e.g., a virtual memory block associated with a portion of an overall namespace of the DSN) within the DSTN memory 22 for a user device, a group of devices, or for public access and establishes per vault dispersed storage (DS) error encoding parameters for a vault. The managing unit 18 facilitates storage of DS error encoding parameters for each vault by updating registry information of the DSN 10, where the registry information may be stored in the DSN memory 22, a computing device 12-16, the managing unit 18, and/or the integrity processing unit 20.
The DSN managing unit 18 creates and stores user profile information (e.g., an access control list (ACL)) in local memory and/or within memory of the DSN memory 22. The user profile information includes authentication information, permissions, and/or the security parameters. The security parameters may include encryption/decryption scheme, one or more encryption keys, key generation scheme, and/or data encoding/decoding scheme.
The DSN managing unit 18 creates billing information for a particular user, a user group, a vault access, public vault access, etc. For instance, the DSTN managing unit 18 tracks the number of times a user accesses a non-public vault and/or public vaults, which can be used to generate a per-access billing information. In another instance, the DSTN managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate a per-data-amount billing information.
As another example, the managing unit 18 performs network operations, network administration, and/or network maintenance. Network operations includes authenticating user data allocation requests (e.g., read and/or write requests), managing creation of vaults, establishing authentication credentials for user devices, adding/deleting components (e.g., user devices, storage units, and/or computing devices with a DS client module 34) to/from the DSN 10, and/or establishing authentication credentials for the storage units 36. Network administration includes monitoring devices and/or units for failures, maintaining vault information, determining device and/or unit activation status, determining device and/or unit loading, and/or determining any other system level operation that affects the performance level of the DSN 10. Network maintenance includes facilitating replacing, upgrading, repairing, and/or expanding a device and/or unit of the DSN 10.
The integrity processing unit 20 performs rebuilding of ‘bad’ or missing encoded data slices. At a high level, the integrity processing unit 20 performs rebuilding by periodically attempting to retrieve/list encoded data slices, and/or slice names of the encoded data slices, from the DSN memory 22. For retrieved encoded slices, they are checked for errors due to data corruption, outdated version, etc. If a slice includes an error, it is flagged as a ‘bad’ slice. For encoded data slices that were not received and/or not listed, they are flagged as missing slices. Bad and/or missing slices are subsequently rebuilt using other retrieved encoded data slices that are deemed to be good slices to produce rebuilt slices. The rebuilt slices are stored in the DSTN memory 22.
The DSN interface module 76 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.). The DSN interface module 76 and/or the network interface module 70 may function as one or more of the interface 30-33 of
In the present example, Cauchy Reed-Solomon has been selected as the encoding function (a generic example is shown in
The computing device 12 or 16 then disperse storage error encodes a data segment using the selected encoding function (e.g., Cauchy Reed-Solomon) to produce a set of encoded data slices.
Returning to the discussion of
As a result of encoding, the computing device 12 or 16 produces a plurality of sets of encoded data slices, which are provided with their respective slice names to the storage units for storage. As shown, the first set of encoded data slices includes EDS 1_1 through EDS 5_1 and the first set of slice names includes SN 1_1 through SN 5_1 and the last set of encoded data slices includes EDS 1_Y through EDS 5_Y and the last set of slice names includes SN 1_Y through SN 5_Y.
To recover a data segment from a decode threshold number of encoded data slices, the computing device uses a decoding function as shown in
The system functions to modify storage of data in a first DST unit set 82 of the at least two DST unit sets 82 by utilizing a distributed computing storage modification process. The computing device 96 issues slice access requests 90 to the first DST unit set 82 and receives slice access responses 92. The computing device 96 identifies a data object stored as a plurality of sets of encoded data slices for the storage modification process based on the received slice access responses 92. For example, the computing device determines a measured reliability level based on the received slice access responses 92 and initiates the storage modification process to improve reliability when the measured reliability level compares unfavorably to a reliability level goal.
The computing device 96 determines one or more tasks of the storage modification process (e.g., retrieve slices, decode slices, re-encode slices, store slices). The determining may be based on one or more of a lookup, receiving a task list, generating the task list based on the received slice access responses. The computing device 96 partitions each of the one or more tasks to produce one or more storage modification partial tasks 94. The computing device 96 assigns each of the one or more storage modification partial tasks 94 to one or more DST units 88 of another DST unit set 82 of the two or more DST unit sets 82. Alternatively, the first DST unit set 82 includes at least one of the assigned one or more DST units 88. The computing device 96 outputs the storage modification partial tasks 94 to the assigned one or more DST units 88.
The assigned one or more DST units 88 execute the storage modification partial tasks 94 to produce storage modification partial results 98. The storage modification partial results 98 include one or more of a slice name of a slice to be generated, the retrieved slice, a newly generated slice, an error indicator, a set of modified slices, a set of newly generated slices, a data segment, and an indicator that the modified slices have been stored to retire the storage modification process. The assigned one or more DST units 88 may issue slice access requests 90 to the first DST unit set 82 and receive slice access responses 92 from the first DST unit set 82. The computing device 96 facilitates completion of the one or more tasks of the storage modification process utilizing the storage modification partial results 98. For example, the computing device 96 stores newly generated slices. As another example, the computing device 96 updates a storage location list.
The method continues at step 104 where the processing module identifies distributed storage and task (DST) execution units to support the one or more tasks of the storage modification process. The identifying may be based on one or more of DST execution unit availability, an error message, and a DST execution unit encoding capability level. The method continues with steps 106 and 108, where for each task of the one or more tasks, the processing module partitions the task to produce one or more partial tasks and for each identified DST execution unit, the processing module assigns one or more partial tasks.
The method continues at step 110 where the processing module receives one or more storage modification partial results. The method continues at step 112 where the processing module facilitates completion of the one or more tasks of the storage modification process utilizing the one or more storage modification partial results. For example, the processing module stores new slices. As another example, the processing module updates a storage location table. As yet another example, the processing module issues a command to a DST execution unit to store a newly generated slice.
The determining the encoding modification may be based on determination factors, which include one or more of greater reliability, modifying a storage location, responding to new hardware, and changing a storage tier. For example, the determination factors may include changing storage of a set of encoded data slices from a cache (tier 1) to a hard drive (tier 2). As another example, determination factors may include changing storage from a magnetic tape (tier 3) to double-parity RAID (tier 1). As yet another example, the determination factors may include changing a physical address of an encoded data slice(s). As yet still a further example, the determination factors may include a new hard drive being added to a storage unit and a storage unit being added to the set of storage units.
The method continues with step 122, where the computing device determines a plurality of tasks for executing the encoding modification. As one example, when the encoding modification is to add an encoded data slice a first task may be obtaining a data matrix and a second task may be updating revision levels for the set of encoded data slices. The plurality of tasks may also include a plurality of intermediate tasks (e.g., between a start of execution of the first task and an end of execution of the second task). In this example, the first intermediate task is creating a new row of an encoding matrix, a second intermediate task is performing a matrix multiplication of the new row by the data matrix to produce the encoded data slice and a third intermediate task is storing the encoded data slice.
As another example of the plurality of intermediate tasks, when the encoding modification is to delete an encoded data slice, a first task may be identifying the encoded data slice and a second task may be updating slice names for the set of encoded data slices. In this example, a first intermediate task may be sending a delete command to a storage unit of the set of storage units that is storing the identified encoded data slice.
As yet another example of the plurality of intermediate tasks, when the encoding modification is to change an encoding matrix (e.g., changing due to a decode threshold change, changing due to different encoding function, etc.), the first task may be obtaining a data matrix and a second task may be updating revision levels for the set of encoded data slices. In this example, a first intermediate task may be creating a new encoding matrix, a second intermediate task may be performing a matrix multiplication of the new encoding matrix by the data matrix to produce a coded matrix, a third intermediate task may be transforming the coded matrix to produce the modified set of encoded data slices and a fourth intermediate task may be storing the modified set of encoded data slices. Each of the intermediate tasks may also include a plurality of partial intermediate tasks.
As an example of the plurality of partial intermediate tasks, the first intermediate task includes a plurality of partial first intermediate tasks. A first partial first intermediate task may be obtaining a first row of the new encoding matrix, a second partial first intermediate task may be obtaining a second row of the new encoding matrix and a third partial first intermediate task may be obtaining a third row of the new encoding matrix. As another example, the second intermediate task includes a plurality of partial second intermediate tasks. A first partial second intermediate task may be multiplying the first row of the new encoding matrix with the data matrix to produce a first new encoded data slice of the modified set of encoded data slices and a second partial second intermediate task may be multiplying the second row of the new encoding matrix with the data matrix to produce a second new encoded data slice of the modified set of encoded data slices.
The method continues with step 124, where the computing device divides a first task of the plurality of tasks into one or more partial tasks based on the first task. For example, when the first task is obtaining a data matrix, a first partial first task may be obtaining a first portion of a data matrix and a second partial first task may be obtaining a second portion of the data matrix.
The method continues with step 126, where the computing device assigns a first partial task of the one or more partial tasks to a first storage unit. The method continues with step 128, where the computing device divides a second task of the plurality of tasks into a plurality of partial tasks based on the second task. For example, a first partial second task may be updating a first slice name of a set of slice names and a second partial second task may be updating a second slice name of the set of slice names.
The method continues with step 130, where the computing device assigns the plurality of partial tasks to a set of storage units. For example, the first partial second task may be assigned to a first storage unit of the set of storage units and the second partial second task may be assigned to a second storage unit of the set of storage units.
The method continues with step 132, where the first storage unit and at least some storage units of the set of storage units execute the first partial task and the plurality of partial tasks, respectively, to produce a modified set of encoded data slices.
The respective storage units may then store or send to another storage unit for storage, an encoded data slice(s) of the modified set of encoded data slices.
It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc. any of which may generally be referred to as ‘data’).
As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.
As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.
As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.
One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.
To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.
In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.
The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.
Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.
The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.
As may further be used herein, a computer readable memory includes one or more memory elements. A memory element may be a separate memory device, multiple memory devices, or a set of memory locations within a memory device. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The memory device may be in a form a solid state memory, a hard drive memory, cloud memory, thumb drive, server memory, computing device memory, and/or other physical medium for storing digital information.
While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations.
The present U.S. Utility patent application claims priority pursuant to 35 U.S.C. § 120 as a continuation of U.S. Utility application Ser. No. 17/248,707, entitled “MODIFYING STORAGE OF ENCODED DATA SLICES BASED ON CHANGING STORAGE PARAMETERS”, filed Feb. 3, 2021, which is a continuation of U.S. Utility application Ser. No. 16/159,469, entitled “USING DISPERSED COMPUTATION TO CHANGE DISPERSAL CHARACTERISTICS”, filed Oct. 12, 2018, issued as U.S. Pat. No. 10,936,448 on Mar. 2, 2021, which is a continuation of U.S. Utility application Ser. No. 15/823,811, entitled “USING DISPERSED COMPUTATION TO CHANGE DISPERSAL CHARACTERISTICS”, filed Nov. 28, 2017, issued as U.S. Pat. No. 10,268,554 on Apr. 23, 2019, which is a continuation-in-part of U.S. Utility application Ser. No. 14/102,987, entitled “UPDATING SHARED GROUP INFORMATION IN A DISPERSED STORAGE NETWORK”, filed Dec. 11, 2013, issued as U.S. Pat. No. 10,055,441 on Aug. 21, 2018, which claims priority pursuant to 35 U.S.C. § 119(e) to the following U.S. Provisional Patent Application No. 61/760,962, entitled “MANAGING A DISPERSED STORAGE NETWORK POWER CONSUMPTION”, filed Feb. 5, 2013, expired, all of which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility patent application for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 61760962 | Feb 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17248707 | Feb 2021 | US |
| Child | 18063583 | US | |
| Parent | 16159469 | Oct 2018 | US |
| Child | 17248707 | US | |
| Parent | 15823811 | Nov 2017 | US |
| Child | 16159469 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14102987 | Dec 2013 | US |
| Child | 15823811 | US |
