<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Bela,<BR>
<BR>
Agreed, increasing the timeouts is probably not the way to go. However I am at the mercy of whatever Infinispan is doing. As for the notion of Infinispan being tested at 1000 nodes:<BR>
<BR>
Manik was quoted here: <A href="http://itmanagement.earthweb.com/netsys/article.php/3864436/Red-Hat-Ramps-Up-Open-Source-Cloud-Projects.htm">http://itmanagement.earthweb.com/netsys/article.php/3864436/Red-Hat-Ramps-Up-Open-Source-Cloud-Projects.htm</A><BR>
It was never denied here: <A href="http://community.jboss.org/thread/156494?tstart=0">http://community.jboss.org/thread/156494?tstart=0</A><BR>
and I'll have to wait until I get home to dig up an email that I think I have.<BR>
<BR>
However, I'm not assigning blame, I was under the impression that it had been tested at 1000 nodes. I just had it up at 430 nodes, but I can't reliably get it to that size when I restart it. I think the answer is that Infinispan will have to use what will scale in JGroups (remove what does not scale). Until then I will have to scale it down to a size that I can start in a reliable fashion. <BR>
<BR>
Still no answer on whether ISPN-83 will be in 4.2.1.....<BR>
<BR>
<BR>
<BR>
Dave Marion<BR> <BR>
> Date: Fri, 18 Mar 2011 16:30:46 +0100<BR>> From: bban@redhat.com<BR>> To: infinispan-dev@lists.jboss.org<BR>> Subject: Re: [infinispan-dev] Infinispan Large Scale support<BR>> <BR>> <BR>> <BR>> On 3/18/11 2:19 PM, david marion wrote:<BR>> ><BR>> > 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.<BR>> <BR>> That's certainly not the way to do it ! If you post your config over on <BR>> the JGroups mailing list [1], I'll take a look and suggest <BR>> modifications. If we work on this a bit to get your cluster going, this <BR>> config could serve as the basis of a large cluster sample config, <BR>> shipped with JGroups and posted on a wiki.<BR>> <BR>> <BR>> > 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<BR>> >documentation, every time a node wants to join a FLUSH is sent across <BR>> the entire system and then a new view is created.<BR>> <BR>> <BR>> FLUSH can not be part of a large cluster configuration; virtual <BR>> synchrony was never meant to scale to more than 20 or so nodes !<BR>> <BR>> <BR>> > We are seeing nodes wait minutes to get the new view. It has been mentioned before that Infinispan was tested at 1000 nodes<BR>> <BR>> <BR>> Where was this mentioned ? I personally have never see such a large <BR>> cluster... The largest cluster I know of is ca 400 nodes...<BR>> <BR>> <BR>> <BR>> [1] https://lists.sourceforge.net/mailman/listinfo/javagroups-users<BR>> <BR>> -- <BR>> Bela Ban<BR>> Lead JGroups / Clustering Team<BR>> JBoss<BR>> _______________________________________________<BR>> infinispan-dev mailing list<BR>> infinispan-dev@lists.jboss.org<BR>> https://lists.jboss.org/mailman/listinfo/infinispan-dev<BR> </body>
</html>