Title of Invention: Data Rebuild on Feedback from a Queue in a Non-Volatile Solid-State Storage Abstract: A storage cluster is provided. The storage cluster includes a plurality of storage nodes, each of the plurality of storage nodes having nonvolatile solid-state memory and a plurality of operations queues coupled to the solid-state memory. The plurality of storage nodes is configured to distribute the user data and metadata throughout the plurality of storage nodes such that the plurality of storage nodes can access the user data with a failure of two of the plurality of storage nodes. Each of the plurality of storage nodes is configured to determine whether a read of 1 or more bits in the solid-state memory via a first path is within a latency budget. The plurality of storage nodes is configured to perform a read of user data or metadata via a second path, responsive to a determination that the read of the bit via the first path is not within the latency budget. Detailed Description: BACKGROUND Solid-state memory, such as flash, is currently in use in solid-state drives (SSD) to augment or replace conventional hard disk drives (HDD), writable CD (compact disk) or writable DVD (digital versatile disk) drives, collectively known as spinning media, and tape drives, for storage of large amounts of data. Flash and other solid-state memories have characteristics that differ from spinning media, which may lead to scheduling conflicts in solid-state storage. Variations in delays from reading bits in a solid-state storage may make it difficult to guarantee performance. Yet, many solid-state drives are designed to conform to hard disk drive standards for compatibility reasons, which makes it difficult to provide enhanced features or take advantage of unique aspects of flash and other solid-state memory. It is within this context that the embodiments arise. SUMMARY In some embodiments, a storage cluster is provided. The storage cluster includes a plurality of storage nodes, each of the plurality of storage nodes having nonvolatile solid-state memory for storage of user data and each of the plurality of storage nodes having a plurality of operations queues coupled to the non-volatile solid-state memory. The plurality of storage nodes is configured to distribute the user data and metadata associated with the user data throughout the plurality of storage nodes such that the plurality of storage nodes can access the user data, via erasure coding, with a failure of two of the plurality of storage nodes. Each of the plurality of storage nodes is configured to determine whether a read of a bit in the non-volatile solid-state memory via a first path is within a latency budget, based on feedback from the plurality of operations queues. The plurality of storage nodes is configured to perform a read of the user data or the metadata via a second path, responsive to a determination that the read of the bit via the first path is not within the latency budget. Other aspects and advantages of the embodiments will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the described embodiments. BRIEF DESCRIPTION OF THE DRAWINGS The described embodiments and the advantages thereof may best be understood by reference to the following description taken in conjunction with the accompanying drawings. These drawings in no way limit any changes in form and detail that may be made to the described embodiments by one skilled in the art without departing from the spirit and scope of the described embodiments. FIG. 1 is a perspective view of a storage cluster with multiple storage nodes and internal storage coupled to each storage node to provide network attached storage, in accordance with some embodiments. FIG. 2 is a system diagram of an enterprise computing system, which can use one or more of the storage clusters of FIG. 1 as a storage resource in some embodiments. FIG. 3 is a multiple level block diagram, showing contents of a storage node and contents of one of the non-volatile solid-state storage units in accordance with some embodiments. FIG. 4 is a block diagram of a controller with operations queues coupled to flash memory in an embodiment of a non-volatile solid-state storage, operating according to scheduling policies. FIG. 5 is a block diagram showing the operations queues of FIG. 4 and various paths for reading bits in flash dies in accordance with some embodiments. FIG. 6 is a block diagram showing the operations queues of FIG. 4 and further paths for reading bits in flash dies in accordance with some embodiments. FIG. 7 is a flow diagram of a method for accessing data in a storage cluster in accordance with some embodiments. FIG. 8 is an illustration showing an exemplary computing device which may implement the embodiments described herein. DETAILED DESCRIPTION The embodiments below describe a storage cluster that stores user data, such as user data originating from one or more user or client systems or other sources external to the storage cluster. The storage cluster distributes user data across storage nodes housed within a chassis, using erasure coding and redundant copies of metadata. Erasure coding refers to a method of data protection in which data is broken into fragments, expanded and encoded with redundant data pieces and stored across a set of different locations, such as disks, storage nodes or geographic locations. Flash memory is one type of solid-state memory that may be integrated with the embodiments, although the embodiments may be extended to other types of solid-state memory or other storage medium, including non-solid-state memory. Control of storage locations and workloads are distributed across the storage locations in a clustered peer-to-peer system. Tasks such as mediating communications between the various storage nodes, detecting when a storage node has become unavailable, and balancing I/Os (inputs and outputs) across the various storage nodes, are all handled on a distributed basis. Data is laid out or distributed across multiple storage nodes in data fragments or stripes that support data recovery in some embodiments. Ownership of data can be reassigned within a cluster, independent of input and output patterns. This architecture described in more detail below allows a storage node in the cluster to fail, with the system remaining operational, since the data can be reconstructed from other storage nodes and thus remain available for input and output operations. In various embodiments, a storage node may be referred to as a cluster node, a blade, or a server. The storage cluster is contained within a chassis, i.e., an enclosure housing one or more storage nodes. A mechanism to provide power to each storage node, such as a power distribution bus, and a communication mechanism, such as a communication bus that enables communication between the storage nodes are included within the chassis. The storage cluster can run as an independent system in one location according to some embodiments. In one embodiment, a chassis contains at least two instances of both the power distribution and the communication bus which may be enabled or disabled independently. The internal communication bus may be an Ethernet bus, however, other technologies such as Peripheral Component Interconnect (PCI) Express, InfiniBand, and others, are equally suitable. The chassis provides a port for an external communication bus for enabling communication between multiple chassis, directly or through a switch, and with client systems. The external communication may use a technology such as Ethernet, InfiniBand, Fibre Channel, etc. In some embodiments, the external communication bus uses different communication bus technologies for inter-chassis and client communication. If a switch is deployed within or between chassis, the switch may act as a translation between multiple protocols or technologies. When multiple chassis are connected to define a storage cluster, the storage cluster may be accessed by a client using either proprietary interfaces or standard interfaces such as network file system (NFS), common internet file system (CIFS), small computer system interface (SCSI) or hypertext transfer protocol (HTTP). Translation from the client protocol may occur at the switch, chassis external communication bus or within each storage node. Each storage node may be one or more storage servers and each storage server is connected to one or more non-volatile solid-state memory units, which may be referred to as non-volatile solid-state storage units. One embodiment includes a single storage server in each storage node and between one to eight non-volatile solid-state memory units, however this one example is not meant to be limiting. The storage server may include a processor, dynamic random access memory (DRAM) and interfaces for the internal communication bus and power distribution for each of the power buses. Inside the storage node, the interfaces and non-volatile solid-state storage share a communication bus, e.g., PCI Express, in some embodiments. The non-volatile solid-state memory units may directly access the internal communication bus interface through a storage node communication bus, or request the storage node to access the bus interface. The non-volatile solid-state memory unit contains an embedded central processing unit (CPU), solid-state storage controller, and a quantity of solid-state mass storage, e.g., between 2-32 terabytes (TB) in some embodiments. An embedded volatile storage medium, such as DRAM, and an energy reserve apparatus are included in the non-volatile solid-state memory unit. In some embodiments, the energy reserve apparatus is a capacitor, super-capacitor, or battery that enables transferring a subset of DRAM contents to a stable storage medium in the case of power loss. In some embodiments, the non-volatile solid-state memory unit is constructed with a storage class memory, such as phase change or magnetoresistive random access memory (MRAM) that substitutes for DRAM and enables a reduced power hold-up apparatus. Various aspects of storage clusters, storage nodes, and non-volatile solid-state storage units are discussed with reference to FIGS. 1-3. Embodiments of a non-volatile solid-state storage with multiple operations queues, scheduling policies, and various paths for reading bits are discussed with reference to FIGS. 4-7. The operations queues provide feedback that is used to evaluate whether a read of a particular bit in a solid-state memory, e.g., flash memory, can be accomplished within a latency or delay budget. When such a read is predicted to be too slow, the storage cluster uses an alternate path, such as reading a redundant copy of a bit, or applying erasure coding to rebuild a data segment. FIG. 1 is a perspective view of a storage cluster 160, with multiple storage nodes 150 and internal solid-state memory coupled to each storage node to provide network attached storage or storage area network, in accordance with some embodiments. A network attached storage, storage area network, or a storage cluster, or other storage memory, could include one or more storage clusters 160, each having one or more storage nodes 150, in a flexible and reconfigurable arrangement of both the physical components and the amount of storage memory provided thereby. The storage cluster 160 is designed to fit in a rack, and one or more racks can be set up and populated as desired for the storage memory. The storage cluster 160 has a chassis 138 having multiple slots 142. It should be appreciated that chassis 138 may be referred to as a housing, enclosure, or rack unit. In one embodiment, the chassis 138 has fourteen slots 142, although other numbers of slots are readily devised. For example, some embodiments have four slots, eight slots, sixteen slots, thirty-two slots, or other suitable number of slots. Each slot 142 can accommodate one storage node 150 in some embodiments. Chassis 138 includes flaps 148 that can be utilized to mount the chassis 138 on a rack. Fans 144 provide air circulation for cooling of the storage nodes 150 and components thereof, although other cooling components could be used, or an embodiment could be devised without cooling components. A switch fabric 146 couples storage nodes 150 within chassis 138 together and to a network for communication to the memory. In an embodiment depicted in FIG. 1, the slots 142 to the left of the switch fabric 146 and fans 144 are shown occupied by storage nodes 150, while the slots 142 to the right of the switch fabric 146 and fans 144 are empty and available for insertion of storage node 150 for illustrative purposes. This configuration is one example, and one or more storage nodes 150 could occupy the slots 142 in various further arrangements. The storage node arrangements need not be sequential or adjacent in some embodiments. Storage nodes 150 are hot pluggable, meaning that a storage node 150 can be inserted into a slot 142 in the chassis 138, or removed from a slot 142, without stopping or powering down the system. Upon insertion or removal of storage node 150 from slot 142, the system automatically reconfigures in order to recognize and adapt to the change. Reconfiguration, in some embodiments, includes restoring redundancy and/or rebalancing data or load. Each storage node 150 can have multiple components. In the embodiment shown here, the storage node 150 includes a printed circuit board 158 populated by a CPU 156, i.e., processor, a memory 154 coupled to the CPU 156, and a non-volatile solid-state storage unit 152 coupled to the CPU 156, although other mountings and/or components could be used in further embodiments. The memory 154 has instructions which are executed by the CPU 156 and/or data operated on by the CPU 156. As further explained below, the non-volatile solid-state storage unit 152 includes flash or, in further embodiments, other types of solid-state memory. FIG. 2 is a system diagram of an enterprise computing system 102, which can use one or more of the storage nodes, storage clusters and/or non-volatile solid-state storage of FIG. 1 as a storage resource 108. For example, flash storage 128 of FIG. 2 may integrate the storage nodes, storage clusters and/or non-volatile solid-state storage of FIG. 1 in some embodiments. The enterprise computing system 102 has processing resources 104, networking resources 106 and storage resources 108, including flash storage 128. A flash controller 130 and flash memory 132 are included in the flash storage 128. In various embodiments, the flash storage 128 could include one or more storage nodes or storage clusters, with the flash controller 130 including the CPUs, and the flash memory 132 including the non-volatile solid-state storage of the storage nodes. In some embodiments flash memory 132 may include different types of flash memory or the same type of flash memory. The enterprise computing system 102 illustrates an environment suitable for deployment of the flash storage 128, although the flash storage 128 could be used in other computing systems or devices, larger or smaller, or in variations of the enterprise computing system 102, with fewer or additional resources. The enterprise computing system 102 can be coupled to a network 140, such as the Internet, in order to provide or make use of services. For example, the enterprise computing system 102 could provide cloud services, physical computing resources, or virtual computing services. In the enterprise computing system 102, various resources are arranged and managed by various controllers. A processing controller 110 manages the processing resources 104, which include processors 116 and random-access memory (RAM) 118. Networking controller 112 manages the networking resources 106, which include routers 120, switches 122, and servers 124. A storage controller 114 manages storage resources 108, which include hard drives 126 and flash storage 128. Other types of processing resources, networking resources, and storage resources could be included with the embodiments. In some embodiments, the flash storage 128 completely replaces the hard drives 126. The enterprise computing system 102 can provide or allocate the various resources as physical computing resources, or in variations, as virtual computing resources supported by physical computing resources. For example, the various resources could be implemented using one or more servers executing software. Files or data objects, or other forms of data, are stored in the storage resources 108. In various embodiments, an enterprise computing system 102 could include multiple racks populated by storage clusters, and these could be located in a single physical location such as in a cluster or a server farm. In other embodiments the multiple racks could be located at multiple physical locations such as in various cities, states or countries, connected by a network. Each of the racks, each of the storage clusters, each of the storage nodes, and each of the non-volatile solid-state storage could be individually configured with a respective amount of storage space, which is then reconfigurable independently of the others. Storage capacity can thus be flexibly added, upgraded, subtracted, recovered and/or reconfigured at each of the non-volatile solid-state storage units. As mentioned previously, each storage node could implement one or more servers in some embodiments. FIG. 3 is a multiple level block diagram, showing contents of a storage node 150 and contents of a non-volatile solid-state storage unit 152 of the storage node 150. Data is communicated to and from the storage node 150 by a network interface controller (NIC) 202 in some embodiments. Each storage node 150 has a CPU 156, and one or more non-volatile solid-state storage 152, as discussed above. Moving down one level in FIG. 3, each non-volatile solid-state storage unit 152 has a relatively fast non-volatile solid-state memory, such as non-volatile random access memory (NVRAM) 204, and flash memory 206. In some embodiments, NVRAM 204 supports an abundance of program erase cycles. Moving down another level in FIG. 3, the NVRAM 204 is implemented in one embodiment as high speed volatile memory, such as dynamic random access memory (DRAM) 216, backed up by energy reserve 218. Energy reserve 218 provides sufficient electrical power to keep the DRAM 216 powered long enough for contents to be transferred to the flash memory 206 in the event of power failure. In some embodiments, energy reserve 218 is a capacitor, super-capacitor, battery, or other device, that supplies a suitable supply of energy sufficient to enable the transfer of the contents of DRAM 216 to a stable storage medium in the case of power loss. The flash memory 206 is implemented as multiple flash dies 222, which may be referred to as packages of flash dies 222 or an array of flash dies 222. It should be appreciated that the flash dies 222 could be packaged in any number of ways, with a single die per package, multiple dies per package (i.e. multichip packages), in hybrid packages, as dies on a printed circuit board or other substrate. In some embodiments, the hybrid package may include a combination of memory types, such as NVRAM, random access memory (RAM), CPU, field programmable gate array (FPGA), or different sized flash memory in the same package. In the embodiment shown, the non-volatile solid-state storage unit 152 has a controller 212 or other processor, and an input output (I/O) port 210 coupled to the controller 212. I/O port 210 is coupled to the CPU 156 and/or the network interface controller 202 of the flash storage node 150. Flash input output (I/O) port 220 is coupled to the flash dies 222, and a direct memory access unit (DMA) 214 is coupled to the controller 212, the DRAM 216 and the flash dies 222. In the embodiment shown, the I/O port 210, controller 212, DMA unit 214 and flash I/O port 220 are implemented on a programmable logic device (PLD) 208, e.g., a field programmable gate array (FPGA). In this embodiment, each flash die 222 has pages, organized as sixteen kB (kilobyte) pages 224, and a register 226 through which data can be written to or read from the flash die 222. In further embodiments, other types of solid-state memory are used in place of, or in addition to flash memory illustrated within flash die 222. In NVRAM 204, redundancy is not organized by segments but instead by messages, where each message (128 bytes to 128 kB) establishes its own data stripe, in some embodiments. NVRAM is maintained at the same redundancy as segment storage and operates within the same storage node groups in some embodiments. Because messages are stored individually the stripe width is determined both by message size and the storage cluster configuration. Larger messages may be more efficiently stored as wider strips. With reference to FIGS. 1-3, two of the many tasks of the CPU 156 on a storage node 150 are to break up write data, and reassemble read data. When the system has determined that data is to be written, an authority for that data is located in one of the non-volatile solid-state storage units 152. The authority may be embodied as metadata, including one or more lists such as lists of data segments which the non-volatile solid-state storage unit 152 manages. When a segment ID for data is already determined the request to write is forwarded to the non-volatile solid-state storage unit 152 currently determined to be the host of the authority determined from the segment. The host CPU 156 of the storage node 150, on which the non-volatile solid-state storage unit 152 and corresponding authority reside, then breaks up or shards the data and transmits the data out to various non-volatile solid-state storage 152. The transmitted data is written as a data stripe in accordance with an erasure coding scheme. In some embodiments, data is requested to be pulled, and in other embodiments, data is pushed. In reverse, when data is read, the authority for the segment ID containing the data is located as described above. The host CPU 156 of the storage node 150 on which the non-volatile solid-state storage unit 152 and corresponding authority reside requests the data from the non-volatile solid-state storage and corresponding storage nodes pointed to by the authority. In some embodiments the data is read from flash storage as a data stripe. The host CPU 156 of storage node 150 then reassembles the read data, correcting any errors (if present) according to the appropriate erasure coding scheme, and forwards the reassembled data to the network. In further embodiments, some or all of these tasks can be handled in the non-volatile solid-state storage 152. In some embodiments, the segment host requests the data be sent to storage node 150 by requesting pages from storage and then sending the data to the storage node making the original request. In some systems, for example in UNIX-style file systems, data is handled with an index node or inode, which specifies a data structure that represents an object in a file system. The object could be a file or a directory, for example. Metadata may accompany the object, as attributes such as permission data and a creation timestamp, among other attributes. A segment number could be assigned to all or a portion of such an object in a file system. In other systems, data segments are handled with a segment number assigned elsewhere. For purposes of discussion, the unit of distribution is an entity, and an entity can be a file, a directory or a segment. That is, entities are units of data or metadata stored by a storage system. Entities are grouped into sets called authorities. Each authority has an authority owner, which is a storage node that has the exclusive right to update the entities in the authority. In other words, a storage node contains the authority, and that the authority, in turn, contains entities. A segment is a logical container of data in accordance with some embodiments. A segment is an address space between medium address space and physical flash locations, i.e., the data segment number, are in this address space. Each data segment is protected, e.g., from memory and other failures, by breaking the segment into a number of data and parity shards, where applicable. The data and parity shards are distributed, i.e., striped, across non-volatile solid-state storage units 152 coupled to the host CPUs 156 (See FIG. 3) in accordance with an erasure coding scheme. Usage of the term segments refers to the container and its place in the address space of segments in some embodiments. Usage of the term stripe refers to the same set of shards as a segment and includes how the shards are distributed along with redundancy or parity information in accordance with some embodiments. A series of address-space transformations takes place across an entire storage system. At the top, there is the inode address space, which the filesystem uses to translate file paths to inode IDs (Identifications). Modes point into medium address space, where data is logically stored. Medium addresses are mapped into segment address space. Segment addresses are then translated into physical flash locations. Physical flash locations have an address range bounded by the amount of flash in the system in accordance with some embodiments. Medium addresses and segment addresses are logical containers, and in some embodiments use a 128 bit or larger identifier so as to be practically infinite, with a likelihood of reuse calculated as longer than the expected life of the system. Addresses from logical containers are allocated in a hierarchical fashion in some embodiments. Initially, each non-volatile solid-state storage unit 152 may be assigned a range of address space. Within this assigned range, the non-volatile solid-state storage unit 152 is able to allocate addresses without synchronization with other non-volatile solid-state storage 152. Data and metadata are stored by a set of underlying storage layouts that are optimized for varying workload patterns and storage devices. These layouts incorporate multiple redundancy schemes, compression formats and index algorithms. Some of these layouts store information about authorities and authority masters, while others store file metadata and file data. The redundancy schemes include error correction codes that tolerate corrupted bits within a single storage device (such as a NAND flash chip), erasure codes that tolerate the failure of multiple storage nodes, and replication schemes that tolerate data center or regional failures. In some embodiments, low density parity check (LDPC) code is used within a single non-volatile solid-state storage. Data is not further replicated within a storage cluster, as it is assumed a storage cluster may fail. Reed-Solomon encoding is used within a storage cluster, and mirroring is used within a storage grid in some embodiments. Metadata may be stored using an ordered log structured index (such as a Log Structured Merge Tree), and large data may be stored in an unordered log structured layout (similar to log structured file systems). FIG. 4 is a block diagram of a controller 212 with operations queues 510 coupled to flash memory 206 in an embodiment of a non-volatile solid-state storage 152, operating according to scheduling policies 514. The scheduling policies 514 are employed by the controller 212 to prioritize operations in the operations queues 510. As described above with reference to FIG. 3, the flash memory 206 has multiple flash dies 222, shown here organized into channels as illustrated by channel 1 and channel n. Each channel has a channel bus 512, which is eight bits wide in the embodiment shown, but could have other widths in further embodiments. Each channel, and channel bus 512, is associated with multiple operations queues 510. Each channel bus 512 thus couples multiple operations queues 510 to 1 or more flash dies 222. The operations queues 510 include read queues, write queues, and erase queues, and may include further queues organized according to traffic classes. These traffic classes could include read operations and write operations relating to user data, metadata, address tables and further system data and operations. In various embodiments, the operations queues 510 are implemented in hardware, firmware, software and memory, or various combinations thereof. The controller 212 of FIG. 4 receives requests for operations, and places (i.e., deposits or writes) the operations into the operations queues 510. The operations may be sorted according to operations classes, or channels, or both. For example, the controller 212 could receive these requests for operations as messages passed down from the CPU 156 of the storage node 152 to the non-volatile solid-state storage 152. Operations typically include reading data, writing data, or erasing (e.g., a block of flash), although further operations at higher or lower level could be performed. Operations are overlapped for high throughput to and from the flash memory 206 in some embodiments. In order to increase efficiency and prevent conflicts, scheduling policies 514 are adopted. These scheduling policies 514 can be held in a memory in or coupled to the controller 212, and can have various formats as readily devised. In some embodiments, versions of flash memory 206 allow interruptible writes or interruptible erases, which may allow a different set of scheduling policies 514. Still referring to FIG. 4, the controller 212 evaluates the benefits to the system of operations waiting in the operations queues 510. That is, the controller 212 determines a relative benefit for each of the operations in accordance with the scheduling policies 514. In one embodiment, the controller 212 weights the operations, i.e., assigns a weighting value to each of the operations in the operations queues 510 based on the operation and the scheduling policies 514. In some embodiments, the scheduling, the policies, and/or the weighting can change dynamically each evaluation period or some other time frame. The operations queues 510 may be set up with sufficient memory to have these weights written adjacent to the operations awaiting in the queues 510. Weighting scales with increasing or decreasing values to represent greater benefit, ranges of weighting values, and further mechanisms for evaluating, weighting, or associating weights and operations are readily devised. For each of the channels, i.e., for each of the channel busses 512, the controller 212 selects or determines an operation from the operations queues 510 that has a greater benefit than others of the operations in the operations queues 510. It may be preferable to pick an operation with a maximum benefit, but there also may be operations with equal or approximately equal benefits, and some tie-breaking algorithm could be employed in some embodiments. It may also be expedient to pick an operation with a locally maximum benefit, without examining all of the operations in all of the queues 510, or without finding a globally maximum benefit. In various embodiments, the controller 212 selects the next operation from the operations queues 510 for each of the channels in various ways. In one embodiment, the controller 212 selects an operation from among operations at the heads of the operations queues 510. In one embodiment, the controller 212 selects an operation from anywhere in the operations queues coupled to each channel. That is, the controller 212 can select operations out of sequence relative to the queues 510. One example policy is a policy to perform the quickest operation or shortest job first, i.e., execute first the operation that consumes the least amount of time. This may be based on expected execution time. For example, a write operation could take from 1 to 3 ms, depending on whether the write is to a fast or a slow page in the flash memory 206. It should be appreciated that various flash memory types, e.g., triple level cell flash (TLC) and quad level cell flash (QLC), can have multiple levels of speed for association with different pages. As a further example, read operations could vary between 100 μs and 500 μs, which may be page dependent. Block erases of flash memory 206 typically take a longer amount of time ID than either the reads or the writes. An interruptible write, or interruptible erase, could be paused in order to perform a more beneficial write, or a read with a greater benefit value. An erase, even if the erase takes a long time, should be performed at high priority if failing to do so results in running out of storage capacity, i.e., having insufficient storage capacity for new writes. An aging mechanism is employed in some embodiments, in order to prevent operations from stagnating in the queues 510. For example, without an aging mechanism, an operation having a low system benefit could remain for an undesirably long amount of time in a queue 510. In these embodiments, an aging parameter could be employed that increases in value, i.e., indicates a greater benefit, the longer an operation remains in a queue 510. Each location in each queue 510 could have an aging parameter, such as a timestamp or a value that increments with each evaluation cycle, associated with the operation at that location. The weighting could take the aging parameter into account. In some embodiments, this aging is accounted for in the scheduling policies 514. The data may be explicitly tagged, for example, tags could indicate that an inode number or identifier is being accessed, or a medium address is being accessed. Tags indicating priority could be attached by a file system based on analytics performed in the inode or medium layer. Tags may indicate levels of priority assigned elsewhere in the system in some embodiments. A tag may indicate a client critical path, which should be given a high priority and high relative benefit. In embodiments with such tags, the scheduling policies 514 relate at least in part to the tags. In some embodiments, some or all operations may not be explicitly tagged. In such cases, a determination of relative benefit to the system could be according to the address and/or the content of data associated with the operation. For example, garbage collection may involve read and write operations to move data out of an area so that a block can be reclaimed in flash memory 206. These operations could be given lower weighting than reads or writes of user data requested by a client and in some embodiments the determination of the lower weighting could be based on tags or addresses. FIG. 5 is a block diagram showing the operations queues 510 of FIG. 4 and various paths for reading bits in flash dies 222. The operations queues 510 provide feedback to the controller 212 of the non-volatile solid-state storage 152. The controller 212 can then use this feedback to manage the operations queues 510 according to the policies as described above (see FIG. 4), and the controller 212 can pass some or all of this feedback, or calculations or analysis based on this feedback, to the CPU 156 of the storage node 150 (see FIG. 3). Feedback from the operations queues 510 could include information regarding remaining capacity or fullness of each of the operations queues 510, weighting of operations presently in the operations queues 510, priorities of operations presently in the operations queues 510, quantities of operations presently in the operations queues 510, or the contents of the operations queues 510. Further types of feedback, and formats or representations of the feedback, are readily devised in accordance with the teachings herein. The CPU 156 of the storage node 150 can use the information from the operations queues 510 to make decisions as to whether or not to do a rebuild of data in some embodiments. This could be based on a performance target for data reads, e.g., a targeted read latency, which can be expressed as a latency budget. If, for a read of a particular bit 540 in a flash die 222, the latency budget is exceeded, i.e., it would take too long a time to perform that read, the CPU 156 can decide to rebuild the data. The read operation may be for a single bit, more than one bit, a byte, a word , a page, a block, etc., in some embodiments. Every component along a particular path adds some delay, and the total of these delays impacts the performance budget. The CPU 156 can perform analysis of various paths, and determine which path to apply in order to meet a latency budget in some embodiments. The path of information flow from the operations queues 510 up to the CPU 156 enables this path analysis. In the scenario depicted in FIG. 5, the CPU 156 is attempting to read, via the controller 212, a particular bit 540 in a flash die 222. This could be in order to obtain a read bit 520 which is part of a data segment, or the read bit 520 could be part of some metadata. In this scenario, a redundant copy 538 of the particular bit 540 exists in another flash die 222. This could be the case when erasure coding is applying redundancy to user data, or when redundancy is applied to metadata. Generally, a first path 550 to a particular bit 540 on a flash die 222 includes a particular channel bus 512, and a particular subset of the operations queues 510. Other paths generally include different channel busses 512, different subsets of the operations queues 510, and different flash dies 222. Controller 212 or the CPU 156 determines, from the feedback from the operations queues 510, that reading the particular bit 540 from the flash die 222 along the first path 550 will take longer than a specified latency budget which may be expressed in microseconds or milliseconds in some embodiments. The latency may be due to the operations queues 510 have too many high priority operations (or operations with high weight) present in the operations queues 510 associated with the particular channel bus 512 along the first path 550. Too many operations could be scheduled ahead of a requested operation under consideration. A write queue could be in danger of overflowing and need service or a block erase could be scheduled at high priority, to avoid loss of write capacity, and so on. In such cases, it will take too much time until the read of the particular bit 540 in the flash die 222 can be performed. Such a situation is depicted as an “X” along the first path 550, indicating that the first path 550 will not satisfy the latency budget. The CPU 156 determines to obtain a duplicate read bit 522 via a second path 552, which leads to a redundant copy of the particular bit 538. In some embodiments the parity bit can be used to rebuild the page to lead to the redundant copy. The second path 552 bypasses the first path 550, and thus avoids the delays indicated by the feedback from the operations queues 510 along the first path 550. In making such a determination, the CPU 156 compares estimated delays along the first path 550 and the second path 552, and chooses the faster path. Determining whether a read of a bit in the non-volatile solid-state memory is likely to be within a latency budget can be a task of the controller 212, the CPU 156, or both as a shared task. Once the decision is made, the read is performed along the preferred path. A storage cluster 160 can thus perform a read of user data or metadata via the second path 552, as a result of determining that reading the particular bit 540 via the first path 550 is not likely to be within the latency budget. FIG. 6 is a block diagram showing the operations queues 510 of FIG. 4 and further paths for reading bits in flash dies 222. In one scenario applicable to FIG. 6, the CPU 156 of a storage node 150 is attempting to read user data, specifically a data segment. For this, the CPU 156 is attempting to gather the data shards 524, 526, 528, 530, 532 from respective solid-state storages 152. Similarly to the scenario depicted in FIG. 5, the controller 212 and/or the CPU 156 determines that reading the particular bit 540 in the flash die 222 via the first path 550 is likely to exceed the latency budget. This is again depicted as the “X” along the first path 550. So, in this scenario, the data shard 526 will not be available within the latency budget. The CPU 156 determines to apply erasure coding 534 to the remaining data shards 524, 528, 530, 532, without waiting for the data shard 526. Applying the erasure coding 534 to the remaining data shards 524, 528, 530, 532 produces the corrected data segment 542 without incurring the latency penalty that would have applied from the wait for the data shard 526. This constitutes a differing version of a second path, which bypasses the first path 550, and results in a rebuild of the user data. A storage cluster 160 can thus perform a read of user data via this second path, as a result of determining that reading the particular bit 540 via the first path 550 is not likely to be within the latency budget. In some cases, this rebuilding of the user data, e.g., producing a corrected data segment 542, reconstructs the missing or overly delayed data shard 526. This could occur when the data shard 526 represents a specified bit in the corrected data segment 542, which is reconstructed using the erasure coding 534. However, in other cases, the rebuilding of the user data produces the corrected data segment 542 from data shards 524, 528, 530, 532 which represent error correction code bits and specified bits in the corrected data segment 542, with the missing or overly delayed data shard 526 representing one of the error correction code bits. The missing or overly delayed data shard 526 is not necessarily directly reconstructed, and the erasure coding scheme has sufficient coverage to rebuild the corrected data segment 542 despite lacking one of the error correction code bits. It should be appreciated that the above scenarios and operations described relative to operations queues 510 and various paths can be applied to other types of non-volatile solid-state storage. Differing paths, various versions of feedback from the operations queues 510, various types of erasure coding, levels of redundancy, and calculations or determinations performed by a controller 212 and/or a CPU 156 at various levels in a storage cluster 160 are applicable to the various embodiments. FIG. 7 is a flow diagram of a method for accessing data in a storage cluster, which can be practiced on or by various storage clusters, storage nodes and/or non-volatile solid-state storage units in accordance with some embodiments. In an action 702, user data is written into storage nodes of a storage cluster, with erasure coding. The erasure coding could include redundant copies of user data and/or error correction code applied to the user data. In various embodiments, the storage nodes include non-volatile solid-state storage units with non-volatile solid-state memory. Some embodiments include flash memory. The erasure coding is such that the user data is accessible via the erasure coding, even when two of the storage nodes are determined to be unreachable. In an action 704, metadata is written into the storage nodes. In various embodiments, metadata is written into non-volatile random-access memory, solid-state memory and/or flash memory. One or more redundant copies of metadata may be written into the memory. In a decision action 706, it is determined if the storage cluster should read a bit in a non-volatile solid-state memory. This could be based on a received request, such as a request to read user data, or a request to read metadata. The request directs, at least in part, to read the bit in the non-volatile solid-state memory. This could be as part of a process of reading data shards to assemble a data segment, or part of reading a subset of the metadata. If the answer is no, flow branches back to one of the actions 702, 704, 706, in order to write more user data or metadata into the storage nodes, or determine whether there should be a read of a bit. If the answer is yes, flow continues to the action 708, to evaluate the read path. In the action 708, feedback is obtained from operations queues. As described above, operations queues are coupled to the channel bus along a path of interest to a particular read bit in solid-state memory. The read path to the bit in the non-volatile solid-state memory is evaluated based on the feedback from the operations queues, in an action 710. In a decision action 712, it is determined if the reading of the bit via the path meets the latency budget. The latency budget may be predefined based on performance goals for the system. If the answer is yes, reading the bit via the path meets the latency budget, flow continues back to one of the actions 702, 704, 706, to write more user data or metadata, or determine whether there should be a read of a bit. If the answer is no, the latency budget is not met, flow continues to the action 714. In action 714, an alternate path is determined. For example, a controller or a processor could determine that an alternate path to a redundant copy of a data bit or metadata bit is available, or erasure coding could be applied to produce a corrected data segment. In an action 716, a read is performed via the alternate path. For example, the redundant copy of the data bit or the redundant copy of the metadata bit could be read by the alternate path. In some embodiments, a read of data shards could be performed via the alternate path, followed by erasure coding application, to produce a corrected data segment. Following this read, flow branches back to one of the actions 702, 704, 706, to write more user data or metadata, or determine whether there should be a read of a bit. It should be appreciated that the methods described herein may be performed with a digital processing system, such as a conventional, general-purpose computer system. Special purpose computers, which are designed or programmed to perform only one function may be used in the alternative. FIG. 8 is an illustration showing an exemplary computing device which may implement the embodiments described herein. The computing device of FIG. 8 may be used to perform embodiments of the functionality for a storage node or a non-volatile solid-state storage in accordance with some embodiments. The computing device includes a central processing unit (CPU) 801, which is coupled through a bus 805 to a memory 803, and mass storage device 807. Mass storage device 807 represents a persistent data storage device such as a disc drive, which may be local or remote in some embodiments. The mass storage device 807 could implement a backup storage, in some embodiments. Memory 803 may include read only memory, random access memory, etc. Applications resident on the computing device may be stored on or accessed via a computer readable medium such as memory 803 or mass storage device 807 in some embodiments. Applications may also be in the form of modulated electronic signals modulated accessed via a network modem or other network interface of the computing device. It should be appreciated that CPU 801 may be embodied in a general-purpose processor, a special purpose processor, or a specially programmed logic device in some embodiments. Display 811 is in communication with CPU 801, memory 803, and mass storage device 807, through bus 805. Display 811 is configured to display any visualization tools or reports associated with the system described herein. Input/output device 809 is coupled to bus 805 in order to communicate information in command selections to CPU 801. It should be appreciated that data to and from external devices may be communicated through the input/output device 809. CPU 801 can be defined to execute the functionality described herein to enable the functionality described with reference to FIGS. 1-7. The code embodying this functionality may be stored within memory 803 or mass storage device 807 for execution by a processor such as CPU 801 in some embodiments. The operating system on the computing device may be MS-WINDOWS™, UNIX™, LINUX™, iOS™, CentOS™, Android™, Redhat Linux™, z/OS™, or other known operating systems. It should be appreciated that the embodiments described herein may be integrated with virtualized computing system also. Detailed illustrative embodiments are disclosed herein. However, specific functional details disclosed herein are merely representative for purposes of describing embodiments. Embodiments may, however, be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein. It should be understood that although the terms first, second, etc. may be used herein to describe various steps or calculations, these steps or calculations should not be limited by these terms. These terms are only used to distinguish one step or calculation from another. For example, a first calculation could be termed a second calculation, and, similarly, a second step could be termed a first step, without departing from the scope of this disclosure. As used herein, the term “and/or” and the “/” symbol includes any and all combinations of one or more of the associated listed items. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “includes”, and/or “including”, when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups
{'application_number': '<application-reference appl-type="utility">\n<document-id>\n<country>US</country>\n<doc-number>14454503</doc-number>\n<date>20140807</date>\n</document-id>\n</application-reference>', 'publication_number': '<publication-reference>\n<document-id>\n<country>US</country>\n<doc-number>20160041868</doc-number>\n<kind>A1</kind>\n<date>20160211</date>\n</document-id>\n</publication-reference>', 'source_file': './application/2016/ipa160211.xml', 'source_data': 'USPTO-Application'}