Hi!
Did you mean the option rpc-auth-allow-insecure on setting?
Yes, exactly. I've also applied the volume set server.allow-insecure on
command, but I doubt that this is helped or is active at all, since I've
never restarted the volume itself, just single nodes.
-- Andreas
On Fri, Aug 28,
Did you mean the option rpc-auth-allow-insecure on setting? I just did a
rolling upgrade from 3.6 to 3.7 without issue, however, I had enabled
insecure connections because I had some clients running 3.7.
-Alastair
On 27 August 2015 at 10:04, Andreas Mather andr...@allaboutapps.at wrote:
Hi
Hi Humble!
Thanks for the reply. The docs do not mention anything related to 3.6-3.7
upgrade that applies to my case.
I could resolve the issue in the meantime by doing the steps mentioned in
the 3.7.1 release notes (
https://gluster.readthedocs.org/en/latest/release-notes/3.7.1/).
Thanks,
Hi Andreas,
Is it even possible to perform a rolling upgrade?
The GlusterFS upgrade process is documented @
https://gluster.readthedocs.org/en/latest/Upgrade-Guide/README/
--Humble
On Thu, Aug 27, 2015 at 4:57 PM, Andreas Mather andr...@allaboutapps.at
wrote:
Hi All!
I wanted to do
Hi All!
I wanted to do a rolling upgrade of gluster from 3.6.3 to 3.7.3, but after
the upgrade, the updated node won't connect.
The cluster has 4 nodes (vhost[1-4]) and 4 volumes (vol[1-4]) with 2
replicas each:
vol1: vhost1/brick1, vhost2/brick2
vol2: vhost2/brick1, vhost1/brick2
vol3:
