Fully loaded Simple two nodes Unify

From GlusterDocumentation

Server Volume Specification

# file: /etc/glusterfs/glusterfs-server.vol
volume posix
  type storage/posix
  option directory /data/export
end-volume

volume plocks
  type features/posix-locks
  subvolumes posix
end-volume

volume brick
  type performance/io-threads
  option thread-count 4
  subvolumes plocks
end-volume

volume brick-ns
  type storage/posix
  option directory /data/export-ns
end-volume

volume server
  type protocol/server
  option transport-type tcp/server
  option auth.ip.brick.allow *
  option auth.ip.brick-ns.allow *
  subvolumes brick brick-ns
end-volume

Client Volume Specification

# file: /etc/glusterfs/glusterfs-client.vol
volume remote1
  type protocol/client
  option transport-type tcp/client
  option remote-host storage1.example.com
  option remote-subvolume brick
end-volume

volume remote2
  type protocol/client
  option transport-type tcp/client
  option remote-host storage2.example.com
  option remote-subvolume brick
end-volume
 
volume remote-ns
  type protocol/client
  option transport-type tcp/client
  option remote-host storage1.example.com
  option remote-subvolume brick-ns
end-volume

volume unify0
  type cluster/unify
  option scheduler rr # round robin
  option namespace remote-ns
  subvolumes remote1 remote2
end-volume

volume iot
  type performance/io-threads
  options thread-count 2
  subvolumes unify0
end-volume

volume wb
  type performance/write-behind
  subvolumes iot
end-volume

volume ioc
  type performance/io-cache
  option cache-size 512MB # Choose this according to how much memory you want to dedicate
  subvolumes wb
end-volume

FYI

• io-cache translator may not work as expected if AFR or stripe translators are loaded below it.