I'm glad to see that this bug was addressed in the latest 5.6 release. Do you know if the fix will be backported to 5.5? I see this bug is filed under the future-5.5 milestone, but I don't know if that means it will necessarily be addressed.
FWIW, we would very much appreciate it being backported as I don't foresee us upgrading to 5.6 in the near future, and we're hitting this bug again when removing nodes from a recently scaled cluster.
Hey all,
I'm glad to see that this bug was addressed in the latest 5.6 release. Do you know if the fix will be backported to 5.5? I see this bug is filed under the future-5.5 milestone, but I don't know if that means it will necessarily be addressed.
FWIW, we would very much appreciate it being backported as I don't foresee us upgrading to 5.6 in the near future, and we're hitting this bug again when removing nodes from a recently scaled cluster.