I recently upgraded our 20x2 distributed-replicate volume from 3.2.6 to
3.3.1. Since then, every server's glusterd logs have been getting
spammed with "[socket.c:1798:socket_event_handler] 0-transport:
disconnecting now" exactly every 3 seconds.
gluster volume info:
Volume Name: myvol
Type: Distributed-Replicate
Volume ID: 56498956-7b4b-4ee3-9d2b-4c8cfce26051
Status: Started
Number of Bricks: 20 x 2 = 40
Transport-type: tcp
Bricks:
Brick1: node43:/mnt/localb
Brick2: node44:/mnt/localb
Brick3: node43:/mnt/localc
Brick4: node44:/mnt/localc
Brick5: node45:/mnt/localb
Brick6: node46:/mnt/localb
Brick7: node45:/mnt/localc
Brick8: node46:/mnt/localc
Brick9: node47:/mnt/localb
Brick10: node48:/mnt/localb
Brick11: node47:/mnt/localc
Brick12: node48:/mnt/localc
Brick13: node45:/mnt/locald
Brick14: node46:/mnt/locald
Brick15: node47:/mnt/locald
Brick16: node48:/mnt/locald
Brick17: node51:/mnt/localb
Brick18: node52:/mnt/localb
Brick19: node51:/mnt/localc
Brick20: node52:/mnt/localc
Brick21: node51:/mnt/locald
Brick22: node52:/mnt/locald
Brick23: node53:/mnt/locald
Brick24: node54:/mnt/locald
Brick25: node53:/mnt/localc
Brick26: node54:/mnt/localc
Brick27: node53:/mnt/localb
Brick28: node54:/mnt/localb
Brick29: node55:/mnt/localb
Brick30: node29:/mnt/localb
Brick31: node55:/mnt/localc
Brick32: node29:/mnt/localc
Brick33: node30:/mnt/localc
Brick34: node31:/mnt/localc
Brick35: node30:/mnt/localb
Brick36: node31:/mnt/localb
Brick37: node40:/mnt/localb
Brick38: node41:/mnt/localb
Brick39: node40:/mnt/localc
Brick40: node41:/mnt/localc
Options Reconfigured:
nfs.register-with-portmap: OFF
nfs.disable: on
performance.quick-read: off
Any ideas what might be causing this, and how to get rid of it?
Thank you,
Pierre
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
