Thanks Vikas, Onbe more Q :) Regarding io-cache. Do I understand from here: http://www.gluster.org/docs/index.php/Translators_options#performance.2Fio-threads that files in the io-cache will be invalidated after 1 second (by default), and therefore if the access pattern for files is longer than this, then the cache won't offer any benefit? I intended to cache .pyc files to speed execution of python files from the Gluster mount, but the access pattern is more likely to be longer (perhaps minutes in some cases). Won't the cache simply be invalidated if a write occurs to the file, and otherwise it can persist in the cache rather then being re-loaded? D. On 16 Jun 2009, at 10:35, Vikas Gorur wrote: > > ----- "Daniel Jordan Bambach" <dan at lateral.net> wrote: > >> I have configured both servers with a config much like the below >> ('srv2' is replaced with 'srv1' on the other machine), and wondered >> if >> >> there might be any further insight from the group about improving >> performance and reliability in my rather simple set-up. > > Your configuration looks fine. > >> Also, is there any reason I can't use the existing (reasonably large) >> / >> home/export directories from GlsuterFS1.3.9 for a 2.0 install? > > There have been some changes in the way replicate stores extended > attributes on the backend from 1.3 to 2.0. To migrate, I recommend: > > 1) Stop GlusterFS 1.3 > 2) Run the script backend-xattr-sanitize.sh (found in the extras/ > directory of the source tarball) > on both your backend directories. > 3) Start GlusterFS 2.0 > > Vikas > -- > Engineer - Z Research > http://gluster.com/ >
