I have repeatedly explained this multiple times the way to hit this problem is *extremely rare* and until and unless you prove us wrong and explain why do you think you can get into this situation often. I still see that information is not being made available to us to think through why this fix is critical. Also as I mentioned earlier, this piece of change touches upon the core store utils code path which need to be thought out really well with all the corner cases before pushing the commit.
On Wed, Jan 31, 2018 at 5:32 PM, ABHISHEK PALIWAL <abhishpaliwal@xxxxxxxxx> wrote:
Hi Team,I am facing one issue which is exactly same as mentioned on the below linkAlso there are some patches available to fix the issue but seems those are not approved and still discussion is going onCurrently the status is "Abandoned".Could you please let me know what is our plan to release this patch? Please respond as it is important for us.RegardsAbhishek Paliwal
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
