Hows do GlusterFS behave in the following scenarios:
=================================
In a multi-brick cluster using AFR a node goes down and then later is
brought back online
ACTUAL BEHAVIOR:
DESIRED BEHAVIOR:
GlusterFS sees the node restart and then begins syncing it's bricks
from transaction log, once it is synced it is put back into the cluster.
=================================
Expand/Contract a GlusterFS cluster.
ACTUAL BEHAVIOR:
DESIRED BEHAVIOR:
GlusterFS allows cluster members to be dynamically
hot-added/hot-removed from a running cluster.
=================================
