We need the logs to figure out the exact problem. Please run the
glusterfs command while mounting through FUSE with the following command
line option:
glusterfs -f your-dht-volfile -L TRACE -l /tmp/dhtlog /mnt/gtest
Then perform the same operations and email us the dhtlog file, and we'll
see
On Wed, 5 May 2010 at 1:00am, Tejas N. Bhise wrote
We have recently made some code changes in an effort to improve small
file and 'ls' performance. The patches are -
selective readdirp - http://patches.gluster.com/patch/3203/
dht lookup revalidation optimization -
I am concerned about this patch:
updated write-behind default values - http://patches.gluster.com/patch/3223/
It changes the default value for performance/writebehind's flush-behind
option from off to on. My understanding is that when flush-behind is off,
all writes are done in the background
Barry,
Some clarifications below -
On Fri, Jun 4, 2010 at 9:17 PM, Barry Jaspan barry.jas...@acquia.com wrote:
I am concerned about this patch:
updated write-behind default values - http://patches.gluster.com/patch/3223/
It changes the default value for performance/writebehind's
