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 wrote:
>
> Strahil, y
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
mai
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 manua
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 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 hea
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.
Eithe
On Fri, Aug 9, 2019 at 3:41 PM Martin Perina wrote:
>
>
> On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola
> wrote:
>
>>
>>
>> Il giorno mar 6 ago 2019 alle ore 23:17 Jayme ha
>> scritto:
>>
>>> I’m aware of the heal process but it’s unclear to me if the update
>>> continues to run while the vo
I'd be happy to take a look at the process from a UX perspective. Would
anyone be able to document a series of screenshots or a video of the end to
end experience of it?
On Fri, Aug 9, 2019 at 6:11 AM Martin Perina wrote:
>
>
> On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola
> wrote:
>
>>
>>
>
On Thu, Aug 8, 2019 at 10:25 AM Sandro Bonazzola
wrote:
>
>
> Il giorno mar 6 ago 2019 alle ore 23:17 Jayme 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 see
Il giorno mar 6 ago 2019 alle ore 23:17 Jayme 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 @Ma
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)
On Tue, Aug 6, 2019 at 6:06 PM Robert O'Kane wrote:
> Hello,
>
> Often(?), upd
Hello,
Often(?), updates to a hypervisor that also has (provides) a Gluster
brick takes the hypervisor offline (updates often require a reboot).
This reboot then makes the brick "out of sync" and it has to be resync'd.
I find it a "feature" than another host that is also part of a gluster
do
Hi Jayme,
I can't recall such a healing time.
Can you please retry and attach the engine & vdsm logs so we'll be smarter?
*Regards,*
*Shani Leviim*
On Tue, Aug 6, 2019 at 5:24 PM Jayme wrote:
> I've yet to have cluster upgrade finish updating my three host HCI
> cluster. The most recent try
12 matches
Mail list logo
