It was used for testing pump xlator functionality. When replace-brick is done on a distribute volume, it would lead to pump xlator migrating data to the destination brick from source. I guess we can delete this test. I don't think we support pump xlator anymore.
On Fri, Sep 8, 2017 at 10:02 AM, Atin Mukherjee <[email protected]> wrote: > Pranith, > > I see you're the author of the test in $Subj. Now while I was working on a > patch https://review.gluster.org/#/c/18226/ to disallow replace brick > operations on dist only volumes the patch failed the regression on this > test as the test actually uses replace brick on a distribute only volume > which IMO is wrong as then this would always end up in to data loss > situation. I'd need some context here to understand the expectation of this > test before doing any modifications. > > ~Atin > -- Pranith
_______________________________________________ Gluster-devel mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-devel
