Vis a vis IP addresses, the command 'ec2-describe-instances ' will show you the hostnames of the instances you have running.
The terracotta server doesn't need to know the IP address of a connecting JVM. Each JVM that connects to the terracotta server needs to know the IP address of the server, but not the other way around. When I've set up terracotta clusters on EC2, I assume that the server is long lived. I haven't really thought about how to make an entire cluster just start up without some configuration, but I'm sure there's some clever way to do it. Vis a vis what happens if the terracotta server goes down: you can run them in pairs (or, really, any number) so that if the primary server goes down, a secondary will automatically take over. The servers can be synchronized using a shared disk (e.g., NFS) or over a network. Running tomcat clustered with terracotta on EC2 is really no different than running tomcat clustered on any other multi-node environment. What information, specifically, are you looking for? --Orion hank williams wrote: > > Steven, > > could you tell me, just conceptually, how you handle the IP address issues > with EC2? How do you access the cluster when you dont know the IP address, > and how does the main terracotta server know where the other instances are > given that every time they come up, they come up at a different name and > IP > address? > > Finally, given that everything is dependent on the main terracotta server > not going down, what happens if it does? Under ec2 you loose all of the > data > stored on that drive, so even if it knew where the other servers were, > once > it goes down and a new instance comes back up it will forget unless that > has > been baked into the system. > > I have read that the terracotta guys have also been working on tomcat > under > ec2 but detailed info is scarce. Any additional info greatly appreciated. > > Thanks > Hank > > On 9/6/07, Steven Gong <[EMAIL PROTECTED]> wrote: >> >> Hank, >> I am working on Standalone version clustering currently and thinking that >> migrating to WAR version should not be a big deal. If you are interested, >> you can take a look at the clustering branch on SVN. >> >> On 9/7/07, hank williams <[EMAIL PROTECTED]> wrote: >> >> > Is there any kind of precise roadmap (or better yet AMI) for getting a >> > tomcat cluster up and running with terracotta. >> > >> > I have heard people talk about this but specifics are thin. >> Particularly >> > as it relates to the IP address not being static and how to handle >> that, >> > particularly in a clustered environment. >> > >> > Regards >> > Hank >> > >> > _______________________________________________ >> > Red5 mailing list >> > Red5@osflash.org >> > http://osflash.org/mailman/listinfo/red5_osflash.org >> > >> > >> >> >> -- >> Best Regards >> Steven Gong >> >> InfraRed5 Red5 Consultant: http://www.infrared5.com , >> [EMAIL PROTECTED] >> >> Red5 Developer: http://osflash.org/red5, >> http://jira.red5.org/confluence/display/~steven/Home >> <http://jira.red5.org/confluence/display/%7Esteven/Home> >> >> Modesty is an overrated quality in men of no great accomplishment. -- >> Ricky Jay >> _______________________________________________ >> Red5 mailing list >> Red5@osflash.org >> http://osflash.org/mailman/listinfo/red5_osflash.org >> >> > > _______________________________________________ > Red5 mailing list > Red5@osflash.org > http://osflash.org/mailman/listinfo/red5_osflash.org > > -- View this message in context: http://www.nabble.com/terracotta---ec2-tf4395743.html#a12556420 Sent from the Red5 - English mailing list archive at Nabble.com. _______________________________________________ Red5 mailing list Red5@osflash.org http://osflash.org/mailman/listinfo/red5_osflash.org
