<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Bela, Manik,<BR>
<BR>
Thanks for responding. Will ISPN-83 be included in 4.2.1.FINAL? Yes, a large cluster jgroups config would be great. At this point we have taken the UDP config distributed with 4.2.0 and increased all the timeouts. It took about 30 minutes to get to 150 nodes. The cluster appears stable once its up, the problem is in the startup. Based on what I am seeing and have read in the documentation, every time a node wants to join a FLUSH is sent across the entire system and then a new view is created. We are seeing nodes wait minutes to get the new view. It has been mentioned before that Infinispan was tested at 1000 nodes and there may be a couple of places where Infinispan is in use at the several hundred node size. Can we get a copy of the configuration files for these systems?<BR>
<BR>
Dave Marion<BR> <BR>
<HR id=stopSpelling>
From: manik@jboss.org<BR>Date: Fri, 18 Mar 2011 10:22:05 +0000<BR>To: infinispan-dev@lists.jboss.org<BR>Subject: Re: [infinispan-dev] Infinispan Large Scale support<BR><BR>
<META content="Microsoft SafeHTML" name=Generator><BR>
<DIV>
<DIV>On 18 Mar 2011, at 07:12, Bela Ban wrote:</DIV>
<BLOCKQUOTE>
<DIV><FONT class=ecxApple-style-span color=#000000><BR></FONT>
<BLOCKQUOTE>Initially we were seeing lots of little clusters form, increasing the number of initial members in the PING section of the jgroups-udp.xml file and increasing the<BR></BLOCKQUOTE>
<BLOCKQUOTE>timeouts seems to have made things better but not great. Even at 20 <BR></BLOCKQUOTE>nodes, we are seeing messages where the coordinator is failing to flush.<BR><BR>I do *not* recommend FLUSH in clusters bigger than 10-15 nodes ! FLUSH <BR>will definitely kill you if you have clusters of 100s of nodes.<BR><BR>IIRC, Infinispan requires FLUSH, but I think this was removed in <BR>4.2.1.FINAL. Maybe Manik or Vladimir can comment ?<BR></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>4.2.1.FINAL isn't out yet, but it should be soon.</DIV>
<DIV><BR></DIV>
<DIV>The strategy I'm taking is that FLUSH will still be enabled and required to maintain the same behaviour as 4.2.0, but you will be able to switch this check off with a system property flag, and provide a JGroups config that excludes FLUSH.</DIV><BR>
<BLOCKQUOTE>
<DIV>
<BLOCKQUOTE>It does not appear that the default configuration scales to a large size.<BR></BLOCKQUOTE><BR><BR>Correct. The default config is geared toward a 4-16 node cluster.<BR></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Yes, you will need to tune your JGroups config for larger clusters. Maybe it makes sense to ship a "jgroups-large-cluster.xml" config as well, to help ease the complexity of this in future.</DIV></DIV>
<DIV><BR></DIV>
<DIV>Cheers</DIV>
<DIV>Manik</DIV><BR>
<DIV><SPAN class=ecxApple-style-span style="WORD-SPACING: 0px; FONT: medium Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
<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" target=_blank>twitter.com/maniksurtani</A></DIV>
<DIV><BR></DIV>
<DIV>Lead, Infinispan</DIV>
<DIV><A href="http://www.infinispan.org/" target=_blank>http://www.infinispan.org</A></DIV>
<DIV><BR></DIV></DIV></SPAN><BR class=ecxApple-interchange-newline></DIV><BR><BR>_______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev </body>
</html>