Dmitriy, On Sun, Apr 19, 2015 at 12:57 AM, Dmitriy Setrakyan <[email protected]> wrote:
> On Sat, Apr 18, 2015 at 1:27 PM, Ognen Duzlevski < > [email protected]> > wrote: > > >> Hello, > >> > >> I have noticed that with 1.0.0-incubating there is somewhat of a delay > with > >> "joining" an ignite cluster. I have 6 EC2 instances - I start ignite.sh > >> examples/configs/example-ignite.sh & and then move on the next instance. > >> The same command on the next instance takes about 5-10 seconds before it > >> returns and each additional instance seems to take even longer. Anyone > else > >> notice this? > > > > > > You should not be getting such pauses. What OS are you running on? > > Linux (the Amazon AMI on EC2). Can you also tell me which ports (tcp and/or udp) need to be open on the instances to make it all work? So far I have deduced a few from running "netstat -lp" on the machines running ignite.sh but I did not have the time to figure out which ones are actually necessary. >> I get this when I run ingnite.sh (1.0.0-incubating): > >> [15:22:31] Topology snapshot [ver=3, nodes=3, CPUs=24, heap=3.0GB] > >> [15:22:32] New version is available at ignite.incubator.apache.org: > 1.0.2 > >> > >> Where is 1.0.2 available for downloads? All I see is 1.0.0-incubating. > >> > > > >You can download it here: http://www.gridgain.com/download/editions/ Ah, OK. The ignite.sh script spits out the apache URL, not the gridgain one. Thanks!
