On 2/10/2016 12:48 AM, Lindsay Mathieson wrote:
This was raised earlier but I don't believe it was ever resolved and
it is becoming a serious issue for me.
I'm doing rolling upgrades on our three node cluster (Replica 3,
Sharded, VM Workload).
I update one node, reboot it, wait for
On Sun, Oct 2, 2016 at 5:49 AM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On 2/10/2016 12:48 AM, Lindsay Mathieson wrote:
>
>> Only the heal count does not change, it just does not seem to start. It
>> can take hours before it shifts, but once it does, its quite rapid. Node 1
>>
On 2/10/2016 12:48 AM, Lindsay Mathieson wrote:
Only the heal count does not change, it just does not seem to start.
It can take hours before it shifts, but once it does, its quite rapid.
Node 1 has restarted and the heal count has been static at 511 shards
for 45 minutes now. Nodes 1 & 2 have
On 2/10/2016 12:48 AM, Lindsay Mathieson wrote:
511 shards for 45 minutes
At (roughly) the one hour mark it started ticking over, heal completed
at 1.5 hours.
--
Lindsay Mathieson
___
Gluster-users mailing list
Gluster-users@gluster.org
Any errors/warnings in the glustershd logs?
-Krutika
On Sat, Oct 1, 2016 at 8:18 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> This was raised earlier but I don't believe it was ever resolved and it is
> becoming a serious issue for me.
>
>
> I'm doing rolling upgrades on our
This was raised earlier but I don't believe it was ever resolved and it
is becoming a serious issue for me.
I'm doing rolling upgrades on our three node cluster (Replica 3,
Sharded, VM Workload).
I update one node, reboot it, wait for healing to complete, do the next one.
Only the heal
