On Mon, May 9, 2011 at 7:33 PM, Vikas Gorur <vikas at gluster.com> wrote: > > On May 9, 2011, at 5:21 AM, Whit Blauvelt wrote: > > On Mon, May 09, 2011 at 02:09:30PM +0530, Vijay Bellur wrote: > > On Saturday 07 May 2011 04:49 AM, Anthony J. Biacco wrote: > > Ok, then i wouldnt understand why shutting down the daemon via the init > script would also kill the clients? Since its possible for the > > clients to be able to access a redundant server. > > > What are the symptoms that you observe on the clients upon a daemon > > shutdown on the server? > > I think the question is why there's a single init.d script that starts or > shuts down both daemon and client at once. > > The init.d/glusterd script has nothing whatsoever to do with the client. It > only controls starting/stopping the server. The client is an independent > process that is started by mounting and stopped by unmounting. > Shutting down the servers will cause the clients to see "Transport endpoint > not connected" errors. It will not "kill" the clients. Is this true for all versions? Now I am slightly confused. Also from the discussion and the documentation I get the impression that there are major differences between 3.0 and 3.1 / 3.2. My personal expectation would have been that without a change in the major version number there would be no such dramatic changes - or at least an automated migration / conversion of *.vol files. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/
