Description of problem: The logs indicating the switching of workers to Active/Passive was redundant. Status API too logs and locking function as well. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Setup geo-rep with master volume with replica and observe logs Actual results: The Active/Passive switching logs are redundant Expected results: Single instance of log is good enough Additional info:
REVIEW: https://review.gluster.org/20856 (geo-rep: Cleanup unwanted code) posted (#1) for review on master by Kotresh HR
COMMIT: https://review.gluster.org/20856 committed in master by "Aravinda VK" <avishwan> with a commit message- geo-rep: Cleanup unwanted code Cleanup the Active/Passive logging code which is redundant. With new status infra implmented, this is redundant as every status switch is logged by status infra. fixes: bz#1619027 Change-Id: I0a6644cb998f3520e62a5189f21e4d66acc0e7c5 Signed-off-by: Kotresh HR <khiremat>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report. glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/