Cloning this bug to 3.3 as the same issue will be observed while upgrading from 3.2 to 3.3
upstream patch : https://review.gluster.org/17756