<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Synchronous cache & consistency
</h3>
<span style="margin-bottom: 10px;">
created by <a href="http://community.jboss.org/people/afitzms">Adam Fitzgerald</a> in <i>JBoss Cache</i> - <a href="http://community.jboss.org/message/604796#604796">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>Hi,</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I have some questions about the behavior of a clustered (sync replicated), configured with a sync singleton store CacheLoader.  The cache would be used transactionally and we want to ensure as high a degree of consistency as possible, both between cache instances within the cluster and the persistent store.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The modifications to the cache are replicated upon commit, are changes replicated to the other instances in the cluster sequentially or concurrently? Is the commit failed if the replication fails to some instances?  Are the changes to the successfully replicated instances rolled back?</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>With the CacheLoader configured as a singleton store with sync writes (and sync replication), if the cache instance elected to do the writing fails what happens to transactions that try to commit during the failover/election period (do they fail)? After the election, with pushStateWhenCoordinator=true, are transactions blocked during the writing of in memory state to the persistent store?  If not why is there a timeout?</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Thanks in advance!</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Adam</p><div class="mcePaste" id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;">Hi,<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>I have some questions about the behavior of a clustered (sync replicated), configured with a sync singleton store<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>CacheLoader.  The cache would be used transactionally and we want to ensure as high a degree of consistency as possible, both<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>between cache instances within the cluster and the persistent store.<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>The modifications to the cache are replicated upon commit, are changes replicated to the other instances in the cluster<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>sequentially or concurrently? Is the commit failed if the replication fails to some instances?  Are the changes to the<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>successfully replicated instances rolled back?<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>With the CacheLoader configured as a singleton store with sync writes (and sync replication), if the cache instance elected<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>to do the writing fails what happens to transactions that try to commit during the failover/election period (do they fail)?<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>After the election, with pushStateWhenCoordinator=true, are transactions blocked during the writing of in memory state to the<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>persistent store?  If not why is there a timeout?<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>Thanks in advance!<p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p>Adam</div></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/604796#604796">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss Cache at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2052">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>