[Bugs] [Bug 1156003] New: write speed degradation after replica brick is down

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1156003

            Bug ID: 1156003
           Summary: write speed degradation after replica brick is down
           Product: GlusterFS
           Version: 3.5.2
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: gojkok at mail.ru
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
We have created gluster replicated volume on two servers:
gluster volume create VolumeName transport tcp replica 2 Server1:/brick
Server2:/brick
On gluster client machine we have mounted volume using glusterfs.
Read/Write speed at glusterfs mount on gluster client machine are around
120MBytes/sec at regular state.
If one of servers(brick) goes down or gets offline from network read speed
remains same as in regular state, but write speed degrades to 3Mbytes/sec.


Version-Release number of selected component (if applicable):
3.5.2

How reproducible:


Steps to Reproduce:
1. create replicated volume on two nodes (servers)
2. mount volume on client machine using glusterfs
3. test write speed on glusterfs mount
4. make one of replica volume nodes offline
5. retest write speed on glusterfs mount


Actual results:
3MBytes/s

Expected results:
120MBytes/s

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.