[Gluster-devel] Cascading different translator doesn't work as expectation

[Krishna Srinivas]

Alfred,

Can you check client logs for any error messages?
You are using ALU, it might be creating the files on the disk with max
space (which being your storage nodes 3, 4)
You can check with RR scheduler to see if all the nodes are participating.

How much memory do the servers and client use?

Krishna

On Sun, Jan 4, 2009 at 6:48 PM, yaomin @ gmail <yangyaomin at gmail.com> wrote:
> Hey,
>
>     I try to use the following cascading mode to enhance the throughput
> performance, but the result is bad.
>     There are four storage nodes and each exports 2 directories.
>
>          (on client)                          unify(alu) translator
>                                                   /
>                     \
>
>  /                                  \
>
> /                                      \
>
>  /                                          \
>
> /                                             \
> (translator on client)        stripe
> stripe
>                                       /
>  \                                     /     \
>                                      /
> \                                   /        \
>                                     /
> \                                 /           \
> (translator on client)   AFR        AFR                          AFR
>  AFR
>                                   /    \           /
>  \                        /     \          /      \
>                                  /      \         /
>  \                    /        \        /        \
>                             #1-1  #2-1  #3-1   #4-4         #1-2   #2-2
> #3-2    #4-2
>    When I use iozone to test with 10 concurrent processes, I only find the
> #3 and #4 storages working,  and the other 2 nodes doesn't work. As my
> expectation, the 4 storage nodes should simultaneously work at any time, but
> it is out of my mind. what's wrong with it?
>   Another issue is that the memory is exhausted on storage nodes when
> writing and on client server when reading, and it is not what I want. Is
> there any method to limit the usage of memory?
>
>
> Best Wishes.
> Alfred
>