Are you observing high cpu usage on client side or server side? If it is on client side, can you remove all performance translators and observe whether you still face the same problem? If removing performance translators solves the problem of high cpu usage, is it possible to zero in on particular translator (write-behind, io-cache, read-ahead etc) by adding and removing them from configuration? I am suspecting io-cache to be the culprit.
Definitely worth looking into more deeply. CPU usage was on the client side. The end configuration I was using is what I posted -- writeback and io-cache. I'll see about eliminating them to further test behavior.
John -- John Madden Sr UNIX Systems Engineer Ivy Tech Community College of Indiana [email protected] _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
