uses RAFT as a consistency protocol. The figure above is from the RAFT paper(https://raft.github.io/raft.pdf). CurveBS uses BRaft to implement the consistency protocol. For CurveBS 1. A CopySet considerations 1. CurveBS uses raft as a consistency protocol which requires majority replicas to be successful. Compare with strong consistency protocol which needs all replicas successful, it provides

availability and reliability ● Cluster topology ● CopySet pre-allocation algorithm ● Raft Consistency protocol High performance ● pre-created file pool ● data strip like RAID ● Zero data copy ● RDMA Cloud COPYSET belong to different failure domainsCURVE IO data flowOther performance optimizations RAFT protocol Zero data copy pre-created file poolCURVE file system File service middleware Upper-layer applications availability/reliability ● Easy to operation and maintenance ● Cloud Native CURVE solution ● RAFT protocol; Copyset allocation algorithm with topology-based failure domain to provide high availability/reliability

include/fuse_kernel.h // This is the first request sent by the kernel to the daemon. It is used to negotiate the protocol version and other filesystem parameters. struct fuse_init_in { uint32_t major; uint32_t minor; want; struct fuse_conn_info { /** * Major version of the protocol (read-only) */ unsigned proto_major; /** * Minor version of the protocol (read-only) */ unsigned proto_minor; /** * Maximum

Estimation of availability and reliability in CurveBS CurveBS uses the RAFT protocol to maintain consistency of stored data. It generally takes the form of 3 replicas of data. If one replica fails

tuning, abnormal detection and schedule tuningStorage Engine Comparison (vs. Ceph) DATA CONSISTENT PROTOCOL CURVE (RAFT) CEPH WRITE SUCCESS majority write successful all write successful READ Leader of