> > AFR ( STRIPE (server1, server2), server3) >> > >> > Let afr serve over the stripe for high performance by default, and >> server3 >> > be a backup. This works well for read-heavy workloads. >> >> How will afr over stripe help for read-heavy work loads? >> > Kris, this is because, you can say 'read-subvolume' as stripe volume, > through which you can read faster (because read calls can be sent parallally > to two nodes, and hence faster). > > >> >> I suggested stripe over afrs keeping in mind AFR's currently bad selfheal >> logic >> for big files. Selfheal will be very optimal in stripe over afrs. >> > For the very reason AFR over STRIPE makes sense. because in this case, afr > doesn't see any files with holes, where as in stripe over afr, you see files > with holes below afr. > Also because, unstriped copy of a file is safer as a backup (though slower, which can be worked around for read-heavy ops) than copied striped chunks. avati
