<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 19, 2018 at 6:19 AM, Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/18/2018 07:34 PM, Ravishankar N wrote:<br>
><br>
><br>
> On 01/18/2018 11:53 PM, Shyam Ranganathan wrote:<br>
>> On 01/02/2018 11:08 AM, Shyam Ranganathan wrote:<br>
>>> Hi,<br>
>>><br>
>>> As release 3.13.1 is announced, here is are the needed details for<br>
>>> 3.13.2<br>
>>><br>
>>> Release date: 19th Jan, 2018 (20th is a Saturday)<br>
>> Heads up, this is tomorrow.<br>
>><br>
>>> Tracker bug for blockers:<br>
>>> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.13.2" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=glusterfs-3.<wbr>13.2</a><br>
>> The one blocker bug has had its patch merged, so I am assuming there are<br>
>> no more that should block this release.<br>
>><br>
>> As usual, shout out in case something needs attention.<br>
><br>
> Hi Shyam,<br>
><br>
> 1. There is one patch <a href="https://review.gluster.org/#/c/19218/" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>c/19218/</a> which<br>
> introduces full locks for afr writevs. We're introducing this as a<br>
> GD_OP_VERSION_3_13_2 option. Please wait for it to be merged on 3.13<br>
> branch today. Karthik, please back port the patch.<br>
<br>
</span>Do we need this behind an option, if existing behavior causes split<br>
brains? Or is the option being added for workloads that do not have<br>
multiple clients or clients writing to non-overlapping regions (and thus<br>
need not suffer a penalty in performance maybe? But they should not<br>
anyway as a single client and AFR eager locks should ensure this is done<br>
only once for the lifetime of the file being accesses, right?)<br>
<br>
Basically I would like to keep options out it possible in backports, as<br>
that changes the gluster op-version and involves other upgrade steps to<br>
be sure users can use this option etc. Which means more reading and<br>
execution of upgrade steps for our users. Hence the concern!<br>
<span class=""><br>
><br>
> 2. I'm also backporting <a href="https://review.gluster.org/#/c/18571/" rel="noreferrer" target="_blank">https://review.gluster.org/#/<wbr>c/18571/</a>. Please<br>
> consider merging it too today if it is ready.<br></span></blockquote><div><br></div><div>Let's take this one in 3.13.3, I think we need to test a few more cases that I missed</div><div>at the time of review.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
</span>This should be fine.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> We will attach the relevant BZs to the tracker bug.<br>
><br>
> Thanks<br>
> Ravi<br>
>><br>
>>> Shyam<br>
>>> ______________________________<wbr>_________________<br>
>>> Gluster-devel mailing list<br>
>>> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
>>> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
>>><br>
>> ______________________________<wbr>_________________<br>
>> Gluster-devel mailing list<br>
>> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
>> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
><br>
</div></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></div>