Abstract
When running a scale-out cluster it is sometimes needed to run various tasks (like an upgrade) on nodes which, in effect, require rebooting them. That could potentially be disruptive for client connections and many times the answer to "when can we do that?" question is "not any time soon". Some measures do exist in the protocol stacks these days. However, when it comes to the older stacks they do not, simply because when they had been developed, the clustered storage wasn't so common. Therefore, we need to resort to all sorts of tricks exploiting the clients' behaviour in order to get as close to the "seamless" experience as we possibly can. The talk describes both the preferred methods and the necessary tricks played to help avoiding the problems. Both may be helpful for smb client implementers to enhance their clients' flexibility.
Learning Objectives
Active management of smb client connections to the cluster,Differences in various smb clients' reactions to disruption,Possible ways of improving the smb clients durability,Methods not worth pursuing further