Description of problem: ec needs to issue locks for reads, so it uses the same management functions used for writes. This means that reads are sent one by one in sequence. Since reads do not touch any state of the file, there could be multiple read requests running at the same time, improving read performance. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/11742 (cluster/ec: Allow read fops to be processed in parallel) posted (#1) for review on master by Xavier Hernandez (xhernandez)
REVIEW: http://review.gluster.org/11742 (cluster/ec: Allow read fops to be processed in parallel) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11742 (cluster/ec: Allow read fops to be processed in parallel) posted (#3) for review on master by Xavier Hernandez (xhernandez)
REVIEW: http://review.gluster.org/11742 (cluster/ec: Allow read fops to be processed in parallel) posted (#4) for review on master by Xavier Hernandez (xhernandez)
REVIEW: http://review.gluster.org/11742 (cluster/ec: Allow read fops to be processed in parallel) posted (#5) for review on master by Xavier Hernandez (xhernandez)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user