Currently, in TiFlash we already support using multiple paths to store data. It is necessary for many cases, for example, users tend to use many slower and cheaper disks for TiFlash in a single machine. And due to the CPU and RAM resources limitation, deploying each TiFlash node for one disk is not practical. So the preferred deploying mode is one TiFlash instance with many disks. With multiple disks supported, we can utilize the IOPS and bandwidth of all disks.
While TiFlash using TiKV as the raft front end, to receive raft logs, we need raft-engine to also support multiple disks.
Currently, in TiFlash we already support using multiple paths to store data. It is necessary for many cases, for example, users tend to use many slower and cheaper disks for TiFlash in a single machine. And due to the CPU and RAM resources limitation, deploying each TiFlash node for one disk is not practical. So the preferred deploying mode is one TiFlash instance with many disks. With multiple disks supported, we can utilize the IOPS and bandwidth of all disks.
While TiFlash using TiKV as the raft front end, to receive raft logs, we need raft-engine to also support multiple disks.