<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>Bug of write-behind client side</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
<BR>
client.vol is<BR>
<BR>
volume unify-brick<BR>
type cluster/unify<BR>
option scheduler rr # round robin<BR>
option namespace muskie-ns<BR>
# subvolumes muskie-brick pike1-brick pike2-brick pike3-brick<BR>
subvolumes muskie-brick pike1-brick pike3-brick<BR>
end-volume<BR>
<BR>
volume wb<BR>
type performance/write-behind<BR>
option aggregate-size 1MB<BR>
option flush-behind on<BR>
subvolume<BR>
client.vol is<BR>
<BR>
volume unify-brick<BR>
type cluster/unify<BR>
option scheduler rr # round robin<BR>
option namespace muskie-ns<BR>
# subvolumes muskie-brick pike1-brick pike2-brick pike3-brick<BR>
subvolumes muskie-brick pike1-brick pike3-brick<BR>
end-volume<BR>
<BR>
volume wb<BR>
type performance/write-behind<BR>
option aggregate-size 1MB<BR>
option flush-behind on<BR>
subvolumes unify-brick<BR>
end-volume<BR>
<BR>
<BR>
yes abcdefghijklmn | while read l; do echo $l; done > a<BR>
<BR>
would cause glusterfs process 100% busy and files system hang when the output size is around the aggregate-size.<BR>
<BR>
<BR>
removing write-behind translator would get rid of this problem.<BR>
<BR>
<BR>
s unify-brick<BR>
end-volume<BR>
<BR>
<BR>
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.<BR>
<BR>
<BR>
<BR>
<BR>
Best,<BR>
Manhong</FONT>
</P>
</BODY>
</HTML>