On Thursday 21 October 2010 wrote Daniel Goolsby: > I seem to have some kind of caching issue. I have a process that will > create hundreds of directories, then immediately spawn a parallel process > across multiple nodes. The job ends of failing because some of the nodes > cannot see the directories that the first process created. If I wait a few > minutes then start the parallel process, it will succeed, which makes me > believe some of the nodes just don't see the directories yet. > > Is there a way to disable caching (or if someone knows of something else I > could check, I'd appreciate)? > > I saw there was an "option cache-timeout" but didn't get any better > results setting that to 0. > > Thoughts?
You forgot to mention your version. We had similar problems with 3.0.5 and had to take quickread out of the module stack in client config to see the changes immediately. Amon Ott -- Dr. Amon Ott - m-privacy GmbH Am Köllnischen Park 1, 10179 Berlin Tel: +49 30 24342334 Fax: +49 30 24342336 Web: http://www.m-privacy.de Handelsregister: Amtsgericht Charlottenburg HRB 84946 Geschäftsführer: Dipl.-Kfm. Holger Maczkowsky, Roman Maczkowsky GnuPG-Key-ID: EA898571 _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
