On 02/28/2016 11:06 PM, ML mail wrote:
> Thanks for explaining why the ping-timeout option has been disabled. Now in
> my case of a small replicate volume of 2 physical nodes with one brick per
> node, does it mean that if one node goes down the FUSE client mount will not
> respond at all? In
Thanks for explaining why the ping-timeout option has been disabled. Now in my
case of a small replicate volume of 2 physical nodes with one brick per node,
does it mean that if one node goes down the FUSE client mount will not respond
at all? In the past it would simply block for 42 seconds and
On 02/28/2016 04:48 PM, ML mail wrote:
> Hi,
>
> I just upgraded from 3.7.6 to 3.7.8 and noticed the following 2 points:
>
> 1) As others on the mailing list I am also affected by a massive performance
> drop on my FUSE mount. I used to have around 10 MB/s transfer, which is
> already quite s
Hi,
I just upgraded from 3.7.6 to 3.7.8 and noticed the following 2 points:
1) As others on the mailing list I am also affected by a massive performance
drop on my FUSE mount. I used to have around 10 MB/s transfer, which is already
quite slow, but now since the upgrade I am at around 2 MB/s as