[Gluster-users] RIO scope in release 4.0 (Was: Request for Comments: Upgrades from 3.x to 4.0+)

Shyam Ranganathan srangana at redhat.com
Thu Nov 2 14:28:59 UTC 2017

On 11/02/2017 08:10 AM, Kotresh Hiremath Ravishankar wrote:
> Hi Amudhan,
> Please go through the following that would clarify up-gradation concerns 
> from DHT to RIO in 4.0
>  1. RIO would not deprecate DHT. Both DHT and RIO would co-exist.
>  2. DHT volumes would not be migrated to RIO. DHT volumes would still be
>     using DHT code.
>  3. The new volume creation should specifically opt for RIO volume once
>     RIO is in place.
>  4. RIO should be perceived as another volume type which is chosed
>     during volume creation
>     just like replicate, EC which would avoid most of the confusions.
    5. RIO will be alpha quality (in terms of features and 
functionality) when it releases with 4.0, it is a tech preview to get 
feedback from the community.
    6. RIO is not a blocker for releasing 4.0, so if said alpha tasks 
are not met, it may not be part of 4.0 as well

Hope this clarifies volume compatibility concerns from a distribute 
layer perspective in 4.0.


More information about the Gluster-users mailing list