On Thu, Jul 21, 2016 at 5:21 AM, David Gossage <dgossage@xxxxxxxxxxxxxxxxxx> wrote:
In the case of rolling upgrades across a cluster if I have my storage and vm hosts on separate machines what order would I want to update?Clients first or storage nodes first?
Version setup info which I should have included probably
Centos 7 servers across board
storage over 2xGB ports LACP bonded
ZFS backed bricks
oVirt 3.6.6
Gluster 3.7.11 currently
Type: Replicate
Volume ID: 167b8e57-28c3-447a-95cc-8410cbdf3f7f
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: ccgl1.gl.local:/gluster1/BRICK1/1
Brick2: ccgl2.gl.local:/gluster1/BRICK1/1
Brick3: ccgl4.gl.local:/gluster1/BRICK1/1
Options Reconfigured:
nfs.enable-ino32: off
nfs.addr-namelookup: off
nfs.disable: on
performance.strict-write-ordering: off
cluster.background-self-heal-count: 16
cluster.self-heal-window-size: 1024
server.allow-insecure: on
cluster.server-quorum-type: server
cluster.quorum-type: auto
network.remote-dio: enable
cluster.eager-lock: enable
performance.stat-prefetch: on
performance.io-cache: off
performance.read-ahead: off
performance.quick-read: off
storage.owner-gid: 36
storage.owner-uid: 36
performance.readdir-ahead: on
features.shard: on
features.shard-block-size: 64MB
diagnostics.brick-log-level: WARNING
David Gossage
Carousel Checks Inc. | System Administrator
Office 708.613.2284
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
