9:31 a.m.
As far as I know,
The UI allows the administrator to override the gluster status, although I always use that
protection.
In my opinion gluster health (especially in my setup - replica2 arbiter1) is very
important.
Best Regards,
Strahil NikolovOn Sep 17, 2019 00:47, Jayme <jaymef(a)gmail.com> wrote:
Strahil, yes this is similar to the approach I have used to upgrade my hci cluster. This
thread is in regards to the ui cluster upgrade procedure. It fails to update after the
first host is rebooted because the gluster volume is still in a healing state and the
attempt to set the second host to maintenance fails because quorum is not met.
On Mon, Sep 16, 2019 at 1:41 PM Strahil <hunter86_bg(a)yahoo.com> wrote:
>
> I keep reading this chain and I still don't get what/who should wait for the
cluster to heal...
> Is there some kind of built-in autopatching feature?
>
> Here is my approach:
> 1. Set global maintenance
> 2. Power off the engine
> 3. Create a gluster snapshot of the engine's volume
> 4. Power on engine manually
> 5. Check engine status
> 6. Upgrade engine
> 7. Upgrade engine's OS
> 8. Reboot engine and check health
> 9. Remove global maintenance
> 10. Set a host into local maintenance (evacuate all VMs)
> 11. Use UI to patch the host (enable autoreboot)
> 12. When host is up - login and check gluster volumes' heal status
> 13. Remove maintenance for the host and repeate for the rest of the cluster.
>
> I realize that for large clusters this approach is tedious and an automatic approach
can be scripted.
>
> Best Regards,
> Strahil Nikolov
>
> On Sep 16, 2019 11:02, Kaustav Majumder <kmajumde(a)redhat.com> wrote:
>>
>> Hi Jayme,
>> It would be great if you could raise a bug regarding the same.
>>
>> On Wed, Sep 11, 2019 at 5:05 PM Jayme <jaymef(a)gmail.com> wrote:
>>>
>>> This sounds similar to the issue I hit with the cluster upgrade process in my
environment. I have large 2tb ssds and most of my vms are several hundred Gbs in size. The
heal process after host reboot can take 5-10 minutes to complete. I may be able to address
this with better gluster tuning.
>>>
>>> Either way the upgrade process should be aware of the heal status and wait
for it to complete before attempting to move on to the next host.
>>>
>>>
>>> On Wed, Sep 11, 2019 at 3:53 AM Sahina Bose <sabose(a)redhat.com> wrote:
>>>>
>>>>
>>>>
>>>> On Fri, Aug 9, 2019 at 3:41 PM Martin Perina <mperina(a)redhat.com>
wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola
<sbonazzo(a)redhat.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Il giorno mar 6 ago 2019 alle ore 23:17 Jayme
<jaymef(a)gmail.com> ha scritto:
>>>>>>>
>>>>>>> I’m aware of the heal process but it’s unclear to me if the
update continues to run while the volumes are healing and resumes when they are done.
There doesn’t seem to be any indication in the ui (unless I’m mistaken)
>>>>>>
>>>>>>
>>>>>> Adding @Martin Perina , @Sahina Bose and