Electronic storage system
AssigneeWeka. IO Ltd.
InventorsMaor Ben Dayan, Liran Zvibel, Omri Palmon
Life of this patent
Estimating the term…
Abstract
Methods and systems for electronic storage are provided. A storage system comprises a plurality of storage system front ends, a plurality of storage system back ends, and a plurality of solid state drive (SSD) agents. Each storage system front end resides on a server of a plurality of servers. Each server of the plurality of servers comprises one or more storage system back ends of the plurality of storage system back ends. Each storage system front end is able to receive I/O requests and relay information associated with the I/O requests to a relevant storage system back end. The relevant storage system back end communicates metadata associated with the I/O request to an SSD via an SSD agent.
Claims21
1-20. (canceled)
A method, comprising:
- configuring each of a plurality of servers with one or more storage system back ends of a plurality of storage system back ends;
- organizing the plurality of storage system back ends into a plurality of erasure-coded stripes, wherein each erasure-coded stripe spans more than one failure domain;
- relaying information associated with an I/O request to a particular storage system back end of the plurality of storage system back ends;
- communicating metadata associated with the I/O request, via an solid state drive (SSD) agent of a plurality of SSD agents, between the particular storage system back end and a first SSD of a plurality of SSDs;
- writing the information associated with the I/O request to the first SSD, wherein the I/O request is a write operation;
- and
- migrating the information associated with the I/O request from the first SSD to an object store as a background asynchronous process.
A storage system comprising:
- a plurality of storage system back ends organized into a plurality of erasure-coded stripes, wherein each erasure-coded stripe spans more than one failure domain;
- a plurality of servers, wherein each of the servers is associated with one or more storage system back ends of the plurality of storage system back ends;
- a plurality of solid state drives (SSDs);
- and
- a plurality of SSD agents, wherein when information associated with an I/O request is relayed to a particular storage system back end of the plurality of storage system back ends:
- metadata associated with the I/O request is communicated, via an SSD agent of a plurality of SSD agents, between the particular storage system back end and a first solid state drive (SSD) of the plurality of SSDs;
- the information associated with the I/O request is written to the first SSD;
- and
- the information associated with the I/O request is migrated from the first SSD to an object store as a background asynchronous process.
A method caused to be performed by a machine that is executing code stored on a non-transitory machine-readable storage, the method comprising:
- configuring each of a plurality of servers with one or more storage system back ends of a plurality of storage system back ends;
- organizing the plurality of storage system back ends into a plurality of erasure-coded stripes, wherein each erasure-coded stripe spans more than one failure domain;
- relaying information associated with an I/O request to a particular storage system back end of the plurality of storage system back ends;
- communicating metadata associated with the I/O request, via an solid state drive (SSD) agent of a plurality of SSD agents, between the particular storage system back end and a first SSD of a plurality of SSDs;
- writing the information associated with the I/O request to the first SSD;
- and
- migrating the information associated with the I/O request from the first SSD to an object store as a background asynchronous process.
Dependencies are inferred from the claim text.