Hey folks,
The network timeout setting (45 secs), which allows a node to determine if another has failed...Is this also invoked when a node is gracefully shutdown/rebooted? I had initially thought it was to deal with a hard failure, however, even rebooting a node for maintenance causes the other node to loose its mounted volume for 45 seconds. I would have hoped the service on the rebooting node would have made the other node aware. Volume Name: store0 Type: Replicate Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: store01:/mnt/brick0 Brick2: store02:/mnt/brick0 Cheers, ALUN JAMES Senior Systems Engineer Tibus T: +44 (0)28 9033 1122 E: [email protected] W: www.tibus.com Follow us on Twitter @tibus Tibus is a trading name of The Internet Business Ltd, a company limited by share capital and registered in Northern Ireland, NI31325. It is part of UTV Media Plc. This email and any attachment may contain confidential information for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorised to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
