I have not quite had such a bad experience with upgrades (was able to
do all upgrades of the 3.5 and 3.6 series without downtime, except for
the 3.6. to 3.7 upgrade where regardless of adding the
rpc-allow-insecure option would not let the 3.7 node talk to the 3.6).
However, had to recently
In a recent audit of the overall Gluster.org infrastructure, we discovered
an intrusion into a little-used server. As a result, we are notifying the
community of the intrusion which we do not believe has compromised any of
the GlusterFS code or packages offered to the community. However, in an
Pls see below
From: Vijaikumar Mallikarjuna [mailto:vmall...@redhat.com]
Sent: Wednesday, 21 October 2015 6:37 PM
To: Sincock, John [FLCPTY]
Cc: gluster-devel@gluster.org
Subject: Re: [Gluster-devel] Need advice re some major issues with glusterfind
On Wed, Oct 21, 2015 at 5:53 AM, Sincock,
I came across the following BZs which are still open in mainline. But they are
fixed and made available in a upstream release. Planning to close them this
week, unless there are any objections.
On Wed, Oct 21, 2015 at 5:53 AM, Sincock, John [FLCPTY] wrote:
> Hi Everybody,
>
> We have recently upgraded our 220 TB gluster to 3.7.4, and we've been
> trying to use the new glusterfind feature but have been having some serious
> problems with it. Overall the glusterfind