[Gluster-users] Problem no. 1

[artur.k]

>> During this time, most likely, gluster is auto-healing the server 
>> that was down.
>> Unfortunately, it seems, the process for it doing so has changed in 2.0.
>> I guess it's more robust, but it's also more time consuming.

>> Previously, files were only healed when you accessed that file.  now, 
>> it seems files are healed when you access a directory.

>> So---- when lighthttp accesses a file x in directory Y,
>> gluster not only auto-heals file x, but also ALL the other files in Y.
>> It blocks the IO request until it's healed the entire directory.
>> This is the safest thing, but what it should do is heal the file we 
>>  need, return back to the application, then continue auto-healing the 
>> rest of the files.

>> I've no idea if they're going to change this or not (or if it's too 
>> difficult), but it is kind of a pain having processes sit waiting 
>> while unrelated files are being dealt with.


>www-xx-1:/var/storage# du -hs glusterfs
>1.5G    glusterfs

>www-xx-1:/var/storage/glusterfs# find . -type f| wc -l
>38187

>www-xx-1:/var/storage/glusterfs# find . -type d| wc -l
>218


You will optimize it for the next versions? I ask because I do not know if I have to wait or look for another solution