<html><head><meta http-equiv="content-type" content="text/html; charset=GB2312"><style>body { line-height: 1.5; }body { font-size: 10.5pt; font-family: ËÎÌå; color: rgb(0, 0, 0); line-height: 1.5; }</style></head><body>
<div><span></span>hi :</div><div><br></div><div>who have more detail info about outcast, eg. design document. can send to me £¿thank you</div><div><br></div><div><h1><br></h1><h1>Features/outcast</h1>
                        
                        <div id="contentSub"><span class="subpages">< <a href="http://www.gluster.org/community/documentation/index.php/Features" title="Features">Features</a></span></div>
                                                                        
                        <div id="mw-content-text" dir="ltr" class="mw-content-ltr" lang="en">
<h2> <span class="mw-headline" id="Feature"> Feature </span></h2>
<p>This feature provides a way of preventing split-brains in time.
</p>
<h2> <span class="mw-headline" id="Summary"> Summary </span></h2>
<p>At the moment there is no way of marking a brick as stale copy,
because of this if a file is modified when the source brick is down the
file goes into split-brain. This feature should give the functionality
where a file can be marked as outcast. Modifications on the file are
considered to be successful only if it succeeds on at least one good
copy. If the operation succeeds only on outcast files then the operation
is treated as failure.
</p><p>Note: Split-brains due to network-partition can still happen. </p></div></div>
<div><br></div><hr style="WIDTH: 210px; HEIGHT: 1px" color="#b5c4df" size="1" align="left">
<div><span><div style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt"><div>hwh@sangfor.com</div></div></span></div>
</body></html>