[Gluster-users] Bug of write-behind client side

[Dai, Manhong]

Hi,

client.vol is

volume unify-brick
  type cluster/unify
  option scheduler rr # round robin
  option namespace muskie-ns
#  subvolumes muskie-brick pike1-brick pike2-brick pike3-brick
  subvolumes muskie-brick pike1-brick pike3-brick
end-volume

volume wb
  type performance/write-behind
  option aggregate-size 1MB
  option flush-behind on
  subvolume
client.vol is

volume unify-brick
  type cluster/unify
  option scheduler rr # round robin
  option namespace muskie-ns
#  subvolumes muskie-brick pike1-brick pike2-brick pike3-brick
  subvolumes muskie-brick pike1-brick pike3-brick
end-volume

volume wb
  type performance/write-behind
  option aggregate-size 1MB
  option flush-behind on
  subvolumes unify-brick
end-volume


yes abcdefghijklmn | while read l; do echo $l; done > a

would cause glusterfs process 100% busy and files system hang when the output size is around the aggregate-size.


removing write-behind translator would get rid of this problem.


s unify-brick
end-volume


command "yes abcdefghijklmn | while read l; do echo $l; done > a" would cause glusterfs process 100% busy and files system hang when the output size is around the aggregate-size. removing write-behind translator would get rid of this problem.




Best,
Manhong
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20080827/1e01fd05/attachment.html>