<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 1 Feb 2012, at 14:39, Dan Berindei wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><blockquote type="cite"><blockquote type="cite"><br class="Apple-interchange-newline">The getCache() timeout should not be increased at all. Instead I would<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">propose that getCache() returns a functional cache immediately, even<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">if the cache didn't receive any data, and it works solely as an L1<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">cache until the administrator allows it to join. I'd even make it<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">possible to designate a cache as an L1-only cache, so it's never an<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">owner for any key.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I agree that would be very nice, but makes it much more complex to<br></blockquote><blockquote type="cite">implement in 5.2 as well: functional L1 means that the other nodes<br></blockquote><blockquote type="cite">must accept this node as part of the grid, including for L1<br></blockquote><blockquote type="cite">invalidation purposes.<br></blockquote><br>I don't think L1 would be a problem, the L1 code doesn't assume that<br>the requestor is in the CH. That would basically be the only<br>difference between a "normal" node and a "L1-only" node.</div></span></blockquote><br></div><div>No, but the Address does need to be in the View. But I suppose this depends on your decoupling of the 2PC view installation from state transfer and consistent hash installation. :)</div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><div>--</div><div>Manik Surtani</div><div><a href="mailto:manik@jboss.org">manik@jboss.org</a></div><div><a href="http://twitter.com/maniksurtani">twitter.com/maniksurtani</a></div><div><br></div><div>Lead, Infinispan</div><div><a href="http://www.infinispan.org">http://www.infinispan.org</a></div><div><br></div></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>