Hit there...
I have set up two server as replica, like this:
gluster vol create Vol01 server1:/data/storage server2:/data/storage
Then I create a config file in client, like this:
volume remote1
type protocol/client
option transport-type tcp
option remote-host server1
option remote-subvolume /data/storage
end-volume
volume remote2
type protocol/client
option transport-type tcp
option remote-host server2
option remote-subvolume /data/storage
end-volume
volume replicate
type cluster/replicate
subvolumes remote1 remote2
end-volume
volume writebehind
type performance/write-behind
option window-size 1MB
subvolumes replicate
end-volume
volume cache
type performance/io-cache
option cache-size 512MB
subvolumes writebehind
end-volume
And add this line in /etc/fstab
/etc/glusterfs/datastore.vol /mnt glusterfs defaults,_netdev 0 0
After mount /mnt, I can access the servers. So far so good!
But when I make server1 crash, I was unable to access /mnt or even use
gluster vol status
on server2
Everything hangon!
I have tried with replicated, distributed and replicated-distributed too.
I am using Debian Stretch, with gluster package installed via apt, provided by Standard Debian Repo, glusterfs-server 3.8.8-1
I am sorry if this is a newbie question, but glusterfs share it's not suppose to keep online if one server goes down?
Any adviced will be welcome
Best
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
