Following up on this, my test/dev cluster is now completely upgraded to ovirt 4.3.2-1 and gluster5.5 and I’ve bumped the op-version on the gluster volumes. It’s behaving normally and gluster is happy, no excessive healing or crashing bricks.
I did encounter https://bugzilla.redhat.com/show_bug.cgi?id=1677160 <https://bugzilla.redhat.com/show_bug.cgi?id=1677160> on my production cluster (with gluster 5.5 clients and 3.12.15 servers) and am proceeding to upgrade my gluster servers to 5.5 now that I’m happy with it on my dev cluster. A little quicker that I’d like, but it seems to be behaving and I was also in the middle of adding disk to my servers, and have to restart them (or at least gluster), so I’m going for it. After I finish this, I’ll test gluster 6 out. -Darrell > On Mar 25, 2019, at 11:04 AM, Darrell Budic <bu...@onholyground.com> wrote: > > I’m not quite done with my test upgrade to ovirt 4.3.x with gluster 5.5, but > so far it’s looking good. I have NOT encountered the upgrade bugs listed as > resolved in the 5.5 release notes. Strahil, I didn’t encounter the brick > death issue and don’t have a bug ID handy for it, but so far I haven’t had > any bricks die. I’m moving the last node of my hyperconverged test > environment over today, and will followup again tomorrow on it. > > Separately, I upgraded my production nodes from ovirt 4.3.1 to 4.3.2 (they > have a separate gluster server cluster which is still on 3.12.15), which > seems to have moved to the gluster 5.3.2 release. While 5.3.0 clients were > not having any trouble talking to my 3.12.15 servers, 5.3.2 hit > https://bugzilla.redhat.com/show_bug.cgi?id=1651246 > <https://bugzilla.redhat.com/show_bug.cgi?id=1651246>, causing disconnects to > one of my servers (but only one, oddly enough), raising the load on my other > two servers and causing a lot of continuous healing. This lead to some > stability issues with my hosted engine and general sluggishness of the ovirt > UI. I also experienced problems migrating from 4.3.1 nodes, but that seems to > have been related to the underlying gluster issues, as it seems to have > cleared up onceI resolved the gluster problems. Since I was testing gluster > 5.5 already, I moved my nodes to gluster 5.5 (instead of rolling them back) > as the bug above was resolved in that version. That did the trick, and my > cluster is back to normal and behaving properly again. > > So my gluster 5.5 experience has been positive so far, and it looks like 5.3 > is a version for laying down and avoiding. I’ll update again tomorrow, and > then flag the centos maintainers about 5.5 stability so it gets out of the > -testing repo if all continues to go well. > > -Darrell > > >> On Mar 21, 2019, at 3:39 PM, Strahil <hunter86...@yahoo.com >> <mailto:hunter86...@yahoo.com>> wrote: >> >> Hi Darrel, >> >> Will it fix the cluster brick sudden death issue ? >> >> Best Regards, >> Strahil Nikolov >> >> On Mar 21, 2019 21:56, Darrell Budic <bu...@onholyground.com >> <mailto:bu...@onholyground.com>> wrote: >> This release of Gluster 5.5 appears to fix the gluster 3.12->5.3 migration >> problems many ovirt users have encountered. >> >> I’ll try and test it out this weekend and report back. If anyone else gets a >> chance to check it out, let us know how it goes! >> >> -Darrell >> >> Begin forwarded message: >> >> From: Shyam Ranganathan <srang...@redhat.com <mailto:srang...@redhat.com>> >> Subject: [Gluster-users] Announcing Gluster release 5.5 >> Date: March 21, 2019 at 6:06:33 AM CDT >> To: annou...@gluster.org <mailto:annou...@gluster.org>, gluster-users >> Discussion List <gluster-us...@gluster.org >> <mailto:gluster-us...@gluster.org>> >> Cc: GlusterFS Maintainers <maintain...@gluster.org >> <mailto:maintain...@gluster.org>> >> >> The Gluster community is pleased to announce the release of Gluster >> 5.5 (packages available at [1]). >> >> Release notes for the release can be found at [3]. >> >> Major changes, features and limitations addressed in this release: >> >> - Release 5.4 introduced an incompatible change that prevented rolling >> upgrades, and hence was never announced to the lists. As a result we are >> jumping a release version and going to 5.5 from 5.3, that does not have >> the problem. >> >> Thanks, >> Gluster community >> >> [1] Packages for 5.5: >> https://download.gluster.org/pub/gluster/glusterfs/5/5.5/ >> <https://download.gluster.org/pub/gluster/glusterfs/5/5.5/> >> >> [2] Release notes for 5.5: >> https://docs.gluster.org/en/latest/release-notes/5.5 >> <https://docs.gluster.org/en/latest/release-notes/5.5>/ >> _______________________________________________ >> Gluster-users mailing list >> gluster-us...@gluster.org <mailto:gluster-us...@gluster.org> >> https://lists.gluster.org/mailman/listinfo/gluster-users >> <https://lists.gluster.org/mailman/listinfo/gluster-users> >> > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/5SS24L27QNSR2MZEQEGKCLWAIW5DVTYX/
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EGFPX4MWW2KAZRSGCFBOIWJCKOUUOGPE/
