Yes that is correct. I don't know if the upgrade to 4.3.1 itself caused
issues or simply related somehow to rebooting all hosts again to apply node
updates started causing brick issues for me again. I started having similar
brick issues after upgrading to 4.3 originally that seemed to have
stabilized, prior to 4.3 I never had a single glusterFS issue or brick
offline on 4.2
On Fri, Mar 15, 2019 at 9:48 AM Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Il giorno ven 15 mar 2019 alle ore 13:38 Jayme <jaymef(a)gmail.com> ha
scritto:
> I along with others had GlusterFS issues after 4.3 upgrades, the failed
> to dispatch handler issue with bricks going down intermittently. After
> some time it seemed to have corrected itself (at least in my enviornment)
> and I hadn't had any brick problems in a while. I upgraded my three node
> HCI cluster to 4.3.1 yesterday and again I'm running in to brick issues.
> They will all be up running fine then all of a sudden a brick will randomly
> drop and I have to force start the volume to get it back up.
>
Just to clarify, you already where on oVirt 4.3.0 + Glusterfs 5.3-1 and
upgraded to oVirt 4.3.1 + Glusterfs 5.3-2 right?
>
> Have any of these Gluster issues been addressed in 4.3.2 or any other
> releases/patches that may be available to help the problem at this time?
>
> Thanks!
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/746CU33TP22...
>
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <
https://www.redhat.com/>
sbonazzo(a)redhat.com
<
https://red.ht/sig>