On 08/21/2018 09:33 AM, mabi wrote:
> Hello,
>
> I just upgraded from 4.0.2 to 4.1.2 using the official documentation:
>
> https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
>
> I noticed that this documentation might be missing the following two
> additional steps:
>
> 1)
Funny I also use stretch but from 4.0.2 to 4.1.2 the glustereventsd did not get
restarted automatically so I restarted it manually after having finished the
upgrade.
‐‐‐ Original Message ‐‐‐
On August 21, 2018 4:20 PM, Hu Bert wrote:
> today i tested an upgrade 3.12.12 -> 4.1.2, and
today i tested an upgrade 3.12.12 -> 4.1.2, and the glustereventsd
service was restarted. We use debian stretch; maybe it depends on the
operating system?
2018-08-21 16:17 GMT+02:00 mabi :
> Oops missed that part at the bottom, thanks Hu Bert!
>
> Now the only thing missing from the upgrade guide
I think point 2 is already covered by the guide; see: "Upgrade
procedure for clients"
Following are the steps to upgrade clients to the 4.1.x version,
NOTE: x is the minor release number for the release
>>> Unmount all glusterfs mount points on the client
Stop all applications that access the
Oops missed that part at the bottom, thanks Hu Bert!
Now the only thing missing from the upgrade guide is what to do about the
glustereventsd service during the upgrade.
‐‐‐ Original Message ‐‐‐
On August 21, 2018 4:11 PM, Hu Bert wrote:
> I think point 2 is already covered by the
I couldn't find any disconnections yet. We analyzed the port's traffic
to see if there was too much data going through, but that was OK. I also
cannot see any other disconnections so for now we will continue to check
the network because I might have missed something.
Thanks for all the help!
Hi all,I want to construct a storage system using gluster, and I want to know what is the most stable version of gluster? Any suggestion for me? Thank you very much.
Hello,
I just upgraded from 4.0.2 to 4.1.2 using the official documentation:
https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
I noticed that this documentation might be missing the following two additional
steps:
1) restart the glustereventsd service
2) umount and mount again
Hello there,
i just installed a replicate setup to test if the upgrade 3.12 -> 4.1
runs smoothly. Well, it did :-) though there is no real usage/load on
the test installation, just some test files. I upgraded from 3.12.12-1
to 4.1.2-1 on a debian stretch. Besides some warnings and errors
Hi,
I seem to have gotten my geo-replication back to working again, but if I
compare the outputs of 'find -type f' from the georep master and the
slave there are numerous differences.
This is 400G of data (and a 4 megabit WAN link) so I can't just pull
over the data again, so:
How do I
Hi Amar,
Unfortunately I do not have the GlusterFS brick logs anymore - however I do
have a hint:
I have 2 gluster (4.1.1) glusterfs volumes where I saw the issue - each has
about 10-12 VMs active.
I also have 2 addl. gluster (4.1.1) glusterfs volumes, but with only 3-4
VMs, where I did not see
On Tue, Aug 21, 2018 at 11:40 AM Hu Bert wrote:
> Good morning :-)
>
> gluster11:
> ls -l /gluster/bricksdd1/shared/.glusterfs/indices/xattrop/
> total 0
> -- 1 root root 0 Aug 14 06:14
> xattrop-006b65d8-9e81-4886-b380-89168ea079bd
>
> gluster12:
> ls -l
Good morning :-)
gluster11:
ls -l /gluster/bricksdd1/shared/.glusterfs/indices/xattrop/
total 0
-- 1 root root 0 Aug 14 06:14
xattrop-006b65d8-9e81-4886-b380-89168ea079bd
gluster12:
ls -l /gluster/bricksdd1_new/shared/.glusterfs/indices/xattrop/
total 0
-- 1 root root 0 Jul 17
13 matches
Mail list logo
