<div dir="ltr">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.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 8, 2017 at 10:02 AM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Pranith,<br><br></div>I see you're the author of the test in $Subj. Now while I was working on a patch <a href="https://review.gluster.org/#/c/18226/" target="_blank">https://review.gluster.org/#/<wbr>c/18226/</a> 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.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div></div><div>~Atin<br></div></font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div>