<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On 30 May 2017, at 19:58, Raghavendra Gowdappa &lt;<a href="mailto:rgowdapp@redhat.com" class="">rgowdapp@redhat.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><br style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">----- Original Message -----</span><br style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">From: "Zhang Huan" &lt;<a href="mailto:zhanghuan@open-fs.com" class="">zhanghuan@open-fs.com</a>&gt;<br class="">To: "Raghavendra G" &lt;<a href="mailto:raghavendra@gluster.com" class="">raghavendra@gluster.com</a>&gt;<br class="">Cc: "GlusterFS Maintainers" &lt;<a href="mailto:maintainers@gluster.org" class="">maintainers@gluster.org</a>&gt;, "Gluster Devel" &lt;<a href="mailto:gluster-devel@gluster.org" class="">gluster-devel@gluster.org</a>&gt;, "Kaushal Madappa"<br class="">&lt;<a href="mailto:kmadappa@redhat.com" class="">kmadappa@redhat.com</a>&gt;<br class="">Sent: Tuesday, May 30, 2017 3:33:09 PM<br class="">Subject: Re: [Gluster-Maintainers] [Gluster-devel] Backport for "Add back socket for polling of events<br class="">immediately..."<br class=""><br class=""><br class=""><br class=""><br class="">On 29 May 2017, at 11:16, Raghavendra G &lt; <a href="mailto:raghavendra@gluster.com" class="">raghavendra@gluster.com</a> &gt; wrote:<br class=""><br class="">Replying to all queries here:<br class=""><br class="">* Is it a bug or performance enhancement?<br class="">Its a performance enhancement. No functionality is broken if this patch is<br class="">not taken in.<br class=""><br class="">* Are there performance numbers to validate the claim?<br class=""><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1358606#c9" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1358606#c9</a><br class=""><br class="">* Are there any existing users who need this enhancement?<br class="">https://bugzilla.redhat.com/show_bug.cgi?id=1358606#c27<br class=""><br class="">Though not sure what branch Zhang Huan is on. @Zhang your inputs are needed<br class="">here.<br class=""><br class="">We are currently on 3.8. Thus the performance number is based on 3.8.<br class="">If you need more details, please let me know.<br class=""></blockquote><br style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Thanks Zhang. The question was more on the lines whether you need backport of the fix to 3.8. </span></div></blockquote><div><div><br class=""></div><div>Actually, we really need this backported to 3.8. I have seen the backport of it to 3.8.</div><div><a href="https://review.gluster.org/#/c/15046/" class="">https://review.gluster.org/#/c/15046/</a></div><div class="">Once it gets merged, we will rebase to it and test it as a whole.</div></div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Can you upgrade to recent releases (say 3.11.x or 3.10.x)?</span><br style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote><div><br class=""></div><div>Sorry, I am afraid not. Gusterfs is one of the key components in our product. An upgrade alone would break the whole thing.&nbsp;</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><br style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Monaco; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class=""><br class=""><br class=""><br class=""><br class="">* Do I think this patch _should_ go into any of the released branches?<br class="">Personally, I don't feel strongly either way. I am fine with this patch not<br class="">making into any of released branches. But, I do think there are users who<br class="">are affected with this (Especially EC/Disperse configurations). If they want<br class="">to stick to the released branches, pulling into released branches will help<br class="">them. @Pranith/Xavi, what are your opinions on this?<br class=""><br class="">regards,<br class="">Raghavendra<br class=""><br class="">On Sun, May 28, 2017 at 6:58 PM, Shyam &lt; <a href="mailto:srangana@redhat.com" class="">srangana@redhat.com</a> &gt; wrote:<br class=""><br class=""><br class="">On 05/28/2017 09:24 AM, Atin Mukherjee wrote:<br class=""><br class=""><br class=""><br class=""><br class="">On Sun, May 28, 2017 at 1:48 PM, Niels de Vos &lt; <a href="mailto:ndevos@redhat.com" class="">ndevos@redhat.com</a><br class="">&lt;mailto: <a href="mailto:ndevos@redhat.com" class="">ndevos@redhat.com</a> &gt;&gt; wrote:<br class=""><br class="">On Fri, May 26, 2017 at 12:25:42PM -0400, Shyam wrote:<br class=""><blockquote type="cite" class="">Or this one: <a href="https://review.gluster.org/15036" class="">https://review.gluster.org/15036</a> &lt;<br class=""><a href="https://review.gluster.org/15036" class="">https://review.gluster.org/15036</a> &gt;<br class=""><br class="">This is backported to 3.8/10 and 3.11 and considering the size and impact<br class="">of<br class="">the change, I wanted to be sure that we are going to accept this across all<br class="">3 releases?<br class=""><br class="">@Du, would like your thoughts on this.<br class=""><br class="">@niels, @kaushal, @talur, as release owners, could you weigh in as well<br class="">please.<br class=""><br class="">I am thinking that we get this into 3.11.1 if there is agreement, and not<br class="">in<br class="">3.11.0 as we are finalizing the release in 3 days, and this change looks<br class="">big, to get in at this time.<br class=""></blockquote><br class=""><br class="">Given 3.11 is going to be a new release, I'd recommend to get this fix<br class="">in (if we have time). <a href="https://review.gluster.org/#/c/17402/" class="">https://review.gluster.org/#/c/17402/</a> is dependent<br class="">on this one.<br class=""><br class="">It is not a fix Atin, it is a more fundamental change to request processing,<br class="">with 2 days to the release, you want me to merge this?<br class=""><br class="">Is there a *bug* that will surface without this change or is it a performance<br class="">enhancement?<br class=""><br class=""><br class=""><br class=""><br class=""><blockquote type="cite" class=""><br class="">Further the change is actually an enhancement, and provides performance<br class="">benefits, so it is valid as a change itself, but I feel it is too late to<br class="">add to the current 3.11 release.<br class=""></blockquote><br class="">Indeed, and mostly we do not merge enhancements that are non-trivial to<br class="">stable branches. Each change that we backport introduces the chance on<br class="">regressions for users with their unknown (and possibly awkward)<br class="">workloads.<br class=""><br class="">The patch itself looks ok, but it is difficult to predict how the change<br class="">affects current deployments. I prefer to be conservative and not have<br class="">this merged in 3.8, at least for now. Are there any statistics in how<br class="">performance is affected with this change? Having features like this only<br class="">in newer versions might also convince users to upgrade sooner, 3.8 will<br class="">only be supported until 3.12 (or 4.0) gets released, which is approx. 3<br class="">months from now according to our schedule.<br class=""><br class="">Niels<br class=""><br class="">_______________________________________________<br class="">maintainers mailing list<br class=""><a href="mailto:maintainers@gluster.org" class="">maintainers@gluster.org</a> &lt;mailto: <a href="mailto:maintainers@gluster.org" class="">maintainers@gluster.org</a> &gt;<br class=""><a href="http://lists.gluster.org/mailman/listinfo/maintainers" class="">http://lists.gluster.org/mailman/listinfo/maintainers</a><br class="">&lt; http://lists.gluster.org/mailman/listinfo/maintainers &gt;<br class=""><br class=""><br class="">_______________________________________________<br class="">Gluster-devel mailing list<br class="">Gluster-devel@gluster.org<br class="">http://lists.gluster.org/mailman/listinfo/gluster-devel<br class=""><br class=""><br class=""><br class="">--<br class="">Raghavendra G<br class="">_______________________________________________<br class="">Gluster-devel mailing list<br class="">Gluster-devel@gluster.org<br class="">http://lists.gluster.org/mailman/listinfo/gluster-devel<br class=""><br class=""><br class="">_______________________________________________<br class="">maintainers mailing list<br class=""><a href="mailto:maintainers@gluster.org" class="">maintainers@gluster.org</a><br class=""><a href="http://lists.gluster.org/mailman/listinfo/maintainers" class="">http://lists.gluster.org/mailman/listinfo/maintainers</a></blockquote></div></blockquote></div><br class=""></body></html>